Career & People

Nobody Gave Me the Green Light

By Felix Maru · November 8, 2026 · 7 min read

There was a role I saw posted in early 2022. The title was IT Operations and Customer Support Engineer. The company was based in the US. I read the job description three times, thought "I don't quite have all of this," and almost closed the tab.

I had been an ICT Officer at a large international NGO for nearly four years. I understood infrastructure at scale, I had managed IT across multiple offices in multiple counties, and I had built enough internal tooling to know I could automate almost anything a support operation needed. But the job posting wanted someone with specific SaaS tooling experience I'd only read about, not used. And it wanted a faster, more self-directed style of work than a large bureaucratic organization typically produces.

I sent the application anyway. I got the role. That was over four years ago.

I am not telling this as a motivational story. I am telling it because the internal calculation I ran in that moment is one I have watched other people run badly, and I want to make it legible.

The Job Description Is a Wish List, Not a Contract

Job postings are written by people who want everything. They list the ideal candidate as if they expect to find one. Some requirements are genuinely load-bearing: if a role is 80% Salesforce administration and you have never opened Salesforce, that is a real gap. But most of the list is aspirational. The hiring manager's internal ranking of those bullets rarely matches their order on the page.

When I read that posting in 2022, I tried to separate the core from the periphery. The core was: someone who can manage a support operation, build workflows, debug weird infrastructure problems, and think without being told what to think. I had evidence for all of that, even if the specific tools named were ones I would have to learn. The periphery was tool familiarity that any motivated person picks up in the first few months.

The honest version of "I am not fully qualified" is usually "I have not yet used this specific tool." That is almost never the reason a hire does not work out.

The Gap Closes From the Inside

There is a version of readiness that is about credentials and certifications, things that can be measured before you are in the seat. And there is a version that is about judgment, pattern recognition, and adaptability, things that only show up once you are actually in the seat.

The second kind is the kind that matters most in support, IT, and automation work. What your manager will trust you with after six months depends almost entirely on the second kind.

The gap between what a job posting lists and what you have is almost always a first-kind gap. You will fill it faster once you are doing the work than you would by preparing to do the work. A person who learns Zendesk while answering real tickets in a real queue learns it in a week. A person who studies Zendesk documentation to prepare for an application is still studying in month three.

This is not an argument for ignoring the gap. If you apply for a role you are genuinely not prepared for and you get it, you will struggle, and struggling in a new role is not fun. The argument is about where the threshold is. For most roles, particularly in support and IT operations, that threshold is lower than the job description implies and lower than most applicants believe.

What Actually Signals Readiness

Before I sent that application in 2022, I took a quick inventory. Not of certifications. Of specific things I had done.

I had built a ticketing system for a team of 300 people spread across 31 counties and kept it running during a period where everyone had to work remotely overnight. I had automated onboarding for new hires in an organization that had no budget for dedicated tooling. I had talked a non-technical executive through an infrastructure decision at 10 PM on a Friday and been right. I had debugged things nobody had documented and written the documentation afterward.

None of that matched the job description bullet for bullet. All of it was evidence for the core of what the role required. That is what you are looking for when you assess your own readiness: not whether you have the listed items, but whether you have done the underlying thing those items are proxies for.

Certifications are proxies. Tool familiarity is a proxy. What the proxy is pointing at, the actual competence, is what the interviewer is trying to infer from the proxy. If you can offer the real thing directly, the proxy becomes less important.

Running the Actual Risk Calculation

People who wait for the green light often do so because they are afraid of rejection. That is understandable but it mis-frames the risk.

Rejection from an application costs almost nothing. A few hours of time, a small amount of hope. The worst realistic outcome is that you get to the final round and do not get the offer. You have still learned how that company evaluates talent, what their process looks like, and where your honest gaps are. That is useful information.

The cost of not applying is harder to see because it has no event attached to it. It is the role you did not get to try for, the feedback you did not receive, the confidence you did not build from going further than you expected. These costs are real but they are invisible.

The rational calculation is almost always: apply, because the downside of applying is small and known, and the downside of not applying is large and invisible.

What to Do in the First 90 Days If You Got the Role at 60%

Admit to yourself that you got the role at 60% and behave accordingly. That means doing the following, more or less in order.

Close the tool gaps first. Whatever specific software or system was on the posting that you did not fully know, make it your first month's project to know it properly. Not certificate-level knowledge. Working knowledge: what it does, how the team uses it, what goes wrong with it most often.

Find out what good looks like in this specific context. Every team has a different definition of "this is handled well." Your job in the first 30 days is to understand their definition, not to import your previous one.

Deliver something visible in the first few weeks. Not a large project. Something that was broken or slow or unclear and is now fixed or faster or documented because you were there. It does not have to be impressive. It has to be real.

Tell your manager what you are still learning. This is counterintuitive, but it matters. A manager who knows you are actively closing a gap is a manager who is watching for the moment you close it. A manager who does not know is a manager who is waiting for you to fail silently.

The People Who Wait for the Green Light

I have watched people wait. The person who wanted one more certification before applying to a role they were already doing informally. The person who had been building automations for two years but kept saying they were not ready to call themselves an automation engineer. The person who could have applied to a US company from Nairobi but assumed it would not work out before trying.

Some of them got there eventually. Some are still waiting.

The green light is usually not coming from outside. The signal you are waiting for, the moment someone tells you that you are ready, is almost never how careers in this industry actually advance. The signal is you, deciding that the evidence is sufficient and the application is worth sending.

It was for me. I think it probably is for you too. The worst they can say is no, and that is information, not a verdict.

If you want to talk through this, or anything else in this space, I am at felixmaru.com.

Share 𝕏 in

Comments