The search is in month three. You have talked to twenty people, made one offer that fell through, and the seat is still empty while the roadmap slips. A board member asks why it is taking so long. The temptation is to lower the bar and hire the next decent person. Sometimes that is right. Usually it is the wrong fix for the actual problem, and it is worth being honest about which situation you are in before you compromise on the most consequential hire you will make.
The two costs you are weighing
Every stalled search is a fight between two real costs. There is the cost of the empty seat: the features not shipped, the founder doing engineering work instead of selling, the momentum lost. And there is the cost of the wrong hire: the months of salary, the code you will have to unwind, the second search you run after you let them go, and the damage a weak first engineer does to everyone you try to hire after them.
For your first engineer, the second cost is almost always larger, and it is larger in a way founders underweight because it is invisible at the moment of hiring. An empty seat is a known, bounded pain you feel every day. A wrong hire is an unbounded pain you feel later, all at once. The whole premise of treating the first hire as a bet, which I wrote about in your first senior engineer is a bet, is that the downside is asymmetric. That asymmetry should make you slow to lower the bar, not fast.
Lowering the bar versus widening the search
Here is the distinction that resolves most of these situations. There is a difference between lowering the bar and widening the search, and founders confuse them constantly.
Lowering the bar means accepting someone who does not clear your judgment and quality threshold, because you are tired of looking. That is the dangerous move for hire one. Widening the search means keeping the bar and changing everything else: the sourcing channels, the pitch, the comp band, the location constraint, the seniority framing. Most stalled searches are not bar problems at all. They are pipeline problems wearing a bar problem's clothes.
Diagnose before you compromise
Before you lower anything, run the diagnosis honestly.
Look at the top of the funnel. If you have talked to only twenty people in three months, you do not have a bar problem, you have a volume problem. A real engineering search needs a genuinely full pipeline, and if yours is a trickle, the fix is more sourcing - a wider net, a recruiter, warm intros, remote candidates - not a lower standard. I wrote about where that pipeline actually comes from in where to actually find your first senior engineer.
Look at where candidates drop. If good people are getting to the final round and then saying no, the problem is your pitch, your comp, or your close, not your bar. If good people are not reaching the final round because you keep rejecting them, then ask whether your bar is actually calibrated or whether you are pattern-matching to a resume you have in your head. And if genuinely strong candidates are simply not entering the funnel at all, your role definition or your compensation is off-market.
Only after all of that comes back clean - full pipeline, competitive offer, sound close, calibrated bar - are you in the rare situation where the honest answer is that the market will not give you your ideal hire at your stage. And even then, the move is usually to reshape the role, not to lower the bar. Hire a strong generalist instead of the specialist you wanted. Bring in a fractional lead to hold the technical bar while you keep searching for the permanent hire. Split the role. Those keep quality intact while unblocking the roadmap. Lowering the bar on judgment, for the one hire whose judgment sets the standard for everyone after, is the last resort, not the first.
When lowering the bar is actually right
It is not never. If the role is genuinely junior - you need hands for well-defined work under your direction, not judgment - then holding out for a senior bar is the mistake, and a capable, cheaper, more available person is the right hire. And if the empty seat is about to sink the company because a specific deliverable has a hard external deadline, a good-enough hire now can beat a perfect hire in two months. The point is not that the bar is sacred. It is that lowering it should be a deliberate decision matched to the role, not a reflex triggered by search fatigue.
FAQ
How long should hiring a first engineer take?
A focused search with a full pipeline typically fills in six to twelve weeks. Past three months, something specific is usually broken - sourcing volume, the pitch, or the offer - and it is worth diagnosing which before you blame the bar or extend the timeline.
Is it ever right to lower the bar for a first engineer?
Yes, in two cases: when the role is genuinely junior and needs hands rather than judgment, or when a hard external deadline makes a good-enough hire now worth more than a perfect hire later. Outside those, a lowered bar on your first hire is usually a mistake you pay for over the next year.
How do I tell a bar problem from a pipeline problem?
Count the funnel. Few candidates in means a sourcing problem; many candidates rejected early means a possible calibration problem; good candidates saying no at the end means a pitch or comp problem. Only a calibrated, full funnel that still yields no one points at a genuine bar-versus-market tension.
What is the alternative to lowering the bar?
Widen the search and reshape the role. Add sourcing channels, open the location, improve the offer, hire a strong generalist instead of a specialist, or bring in a fractional lead to hold the bar while you keep looking. These unblock the roadmap without compromising the hire whose quality sets your standard.
If you are three months in and want an outside read on whether it is your bar or your pipeline, book a call.