The standard estimate for a bad engineering hire is 3x to 5x their annual salary. For a $180,000 senior engineer, that is $540,000 to $900,000 in real cost. Founders hear that number and assume it is inflated. It is not. It is usually low.
Here is what the math actually looks like across the startups we have worked with.
The direct costs
Recruiting cost to find them: $20,000 to $40,000 if you used a contingent recruiter, $5,000 to $15,000 if you sourced inbound. Plus internal time, usually 30 to 50 hours across interviews, take-homes, and debriefs.
Salary and benefits during their tenure: 6 to 12 months at $180,000 + 25% benefits = $112,500 to $225,000.
Severance and offboarding: 2 to 8 weeks of salary depending on jurisdiction and contract terms. Typical: $20,000 to $35,000.
Cost to find their replacement: same recruiting cost, plus 3 to 6 months of vacancy where the role is unfilled.
Direct costs alone: $200,000 to $400,000 before counting the productivity drag.
The indirect costs that dwarf the direct ones
Their output value, if it is negative. A bad senior engineer does not produce zero. They produce negative output. The code they shipped has to be rewritten. The decisions they made have to be reversed. The features they led got scoped wrong and need redo. This is the single largest cost and is genuinely hard to quantify until you live through it.
Team time spent compensating. Other engineers cover for them. Senior engineers spend their time reviewing and fixing instead of building. Tech leads spend their time managing performance instead of strategy. Pull that out of a five-person team and you have lost 30% of total team capacity for a quarter.
Morale and retention damage. Good engineers are the most sensitive to bad teammates. A persistent low performer who is not addressed is the most common reason we see top engineers quit. Lose one good engineer to morale damage and you have multiplied the original bad hire's cost by 2x.
Customer and revenue damage. A bug they introduced takes down production. A security gap they missed gets exploited. A customer integration they botched delays a launch by a quarter. These are tail risks, but they are real.
Why bad hires happen
The patterns are consistent.
Rushing the process. "We need someone now" leads to lowering the bar. The cost of waiting two more weeks for the right hire is always lower than the cost of bringing in the wrong one.
Anchoring on credentials. Strong resume, strong school, strong previous employer, weak signal on whether they will be effective in your specific context. Past success does not transfer automatically. Evaluate the work, not the brand.
Skipping reference checks. Three calls with people who actually worked with the candidate, asking specific questions about behavior under pressure, will surface 80% of red flags. Almost no one does it well.
Hiring for niceness over competence. Cultural fit matters. So does the ability to do the job. They are not substitutes.
What to do instead
Slow down the top of funnel. Be ruthless about who you bring in to interview. Each candidate consumes 15 to 25 hours of team time across the full loop.
Use work samples. A 4-hour take-home plus a 90-minute pairing session predicts success better than a 5-round behavioral interview, and respects everyone's time more.
Reference deeply. Two structured calls with former managers, with specific questions about strengths, gaps, and how they handled conflict.
Move fast when it is not working. The average startup waits three months too long to part ways with a bad hire. Every week of delay compounds the cost.
Need help hiring engineering leaders?
We help startups design technical interview loops, evaluate candidates, and structure roles. Especially valuable when the founder is non-technical.
Talk to us