I Am Not Hiring a Doer. I Am Hiring a Driver

Hiring for a fully remote senior role, 2026

I passed on two senior engineering candidates. Both were technically competent. Neither made it past me.

Here is the feedback I sent back to the firm sourcing for us, because I think it applies well beyond my open req. I am not looking for a doer. I am looking for a driver.

Executors versus owners

Both candidates presented as executors. They could describe what they built when handed a spec, and describe it well. Neither could point to a problem they owned end to end, made the calls on, and drove from ambiguity to shipped. When I asked for one, I got a list of features. When I asked who decided the features were the right ones, the answer was always somebody else.

That distinction is the entire role.

We are 100 percent remote. Nobody is looking over anyone's shoulder, and I do not want there to be. That model only works with people who take initiative by default, set their own direction inside a goal, and close the loop without being chased. A doer waits to be told the next step. A driver finds it. In an office you can paper over the difference with a standup and a walk to somebody's desk. Across three time zones, you cannot. The doer sits idle until the next sync, and the sync is tomorrow.

The why and the how, not the what

At the senior level I also need the why and the how, not the what. "I built the payments service" tells me nothing. Tell me the tradeoffs you weighed. Why you chose one approach over another. What you would do differently. How you reason about a system you have never seen before.

The what is on the resume already. Any competent engineer can recite it, and any competent recruiter can match it against a keyword list. The why and the how are the only signal I cannot get from a document, which is the whole reason a senior interview exists. If a candidate cannot reconstruct the decision, I have to assume they were not the one making it.

That is what separates a senior engineer from a mid-level engineer with a longer resume.

What the market is flooded with

Here is the uncomfortable part. Senior hiring right now is flooded with people who look strong on paper but have only operated inside well-scaffolded teams, where a lead broke the work down and they filled in the code. That was a perfectly good career for fifteen years. It is not a senior profile anymore.

With AI tooling absorbing more and more of the pure implementation work, that profile is worth less every quarter. The tickets that used to be handed to a strong implementer are now handed to an agent, with the strong implementer reviewing the result. The part that survives is the part the agent cannot do: deciding what the ticket should have said in the first place.

The scarce skill is judgment. Deciding what to build. Deciding how to architect it. Owning the outcome when it does not go to plan.

I would rather see two candidates who clearly clear that bar than ten who match the keyword list. The firm now knows that, and the next two candidates it sends me will be screened for ownership before they are screened for stack.