The cost of a bad hire in engineering runs 12 months and 7 lines. Salary is the smallest line.

Salary and overhead for the period. The hiring cost paid twice. Your strongest engineers’ time spent covering.

The work that did not happen, and what the team concludes about the bar.

Ask a hiring manager what a bad hire costs and you get the salary. Here is the rest of the bill.

What is a bad hire?

A bad hire is someone who cleared your bar and cannot do the work. The bill runs 12 months.

Months 1 to 3 look like normal ramp-up.

Months 3 to 6 the team covers quietly. Months 6 to 9 someone says it out loud.

Months 9 to 15 cover the exit and the backfill.

Months What is happening
1-2 Onboarding. Everyone is patient. Nothing is visible yet
3-4 The team notices. Nobody says it out loud, including to the manager
5-6 The manager notices. The first vague conversation happens
7-9 Real conversations, a plan, or an exit
9-15 Backfill: reopen the role, hire again, onboard again

The honest unit is a year, and often more.

The timeline of a bad hire: months one to two look normal, three to four the team notices, five to nine the manager acts, nine to fifteen the backfill
How long a bad hire takes to show

What is the true cost of a bad hire?

The true cost of a bad hire is 7 lines. Salary is the smallest of them. Four lines are direct, and three compound.

Direct: salary and overhead, the hiring cost twice, team time, missed work. Compounding: the code, team morale, your credibility.

Salary and overhead. Nine months of loaded cost. That is salary plus the employer’s taxes and benefits.

The hiring cost, twice. Sourcing, 5 rounds, the debrief, the agency fee. All of it again for the backfill.

The team’s time. Reviews that take 3 passes, and the rework. Rework lands on your strongest engineers.

The work that did not happen. Whatever the headcount was for is 12 months late. The roadmap assumed otherwise.

The compounding damage. Code to unpick. Decisions other things now depend on.

The morale cost. A team carrying someone for 6 months sees the bar. One resignation doubles the bill.

Your credibility. The next headcount request starts from a weaker position.

The seven lines on the cost of a bad hire: salary, the hiring cost twice, the team's time, the work that did not happen, code damage, morale and your credibility
What a bad hire actually costs, line by line

Why do teams keep paying the cost of a bad hire?

Teams keep paying the cost of a bad hire because the empty seat hurts today. Four reasons, all rational in the moment.

Urgency beats accuracy, and nobody owns the outcome. The false negative stays invisible. Sunk cost buys one more quarter.

Urgency beats accuracy. A team down 2 people lowers the bar to stop the pain. The pain returns in 6 months.

Nobody owns the outcome. Interviewers score a round. Recruiters fill a role. The manager inherits the result.

The false negative is invisible. Rejecting a good candidate costs nothing you can see. Accepting a weak one costs the whole list above.

Sunk cost. Six weeks of onboarding makes a manager try for one more quarter. And another.

Four reasons teams keep paying the cost of a bad hire: urgency, nobody owning the outcome, invisible false negatives and sunk cost
Why teams keep paying for a bad hire

What reduces the cost of a bad hire?

Five changes reduce the cost of a bad hire. None of them is another interview round.

A written bar before the first CV. Scorecards with evidence. Calibration. A debrief that decides. A 90-day checkpoint with teeth.

More rounds do not help. Longer loops mostly lose good candidates.

A written bar. What must be true, and what would be nice. Agreed with the panel before the first CV.

Scorecards with evidence. “3 out of 5” is a feeling. “Could not explain code they submitted” is a finding. Examples here.

Calibration. 2 hours a quarter reviewing real anonymised scorecards, together. That fixes more than any new question format.

A debrief that decides. Run from the scorecard, it catches the hire everyone doubted and nobody blocked.

A 90-day checkpoint. Book it at offer time, with one name next to the decision. Month 3 is far cheaper than month 9.

Five changes that reduce the risk of a bad hire: a written bar, scorecards with evidence, calibration, a real debrief and a used probation period
The 5 changes that reduce a bad hire

How do you calculate the cost of a bad hire?

A cost of a bad hire calculator needs 3 inputs. Loaded cost per month, months until the exit, and the team’s hours.

A director needs a comparison, and a precise figure can wait.

Take your loaded cost for the level. Multiply by the months in the table. Add a conservative estimate of the team’s time.

Bad hire calculator

For €11,000 a month over 9 months, plus 5 team hours a week:

Salary and overhead€99,000
The team's time€13,400
The bill, at least€112,400
A year of calibration, panel of 4€2,200

One bad hire costs 51 years of calibration.

Left out: the hiring cost paid twice, the work that did not happen, the code to unpick and morale. The real bill is higher.

Put that next to 2 hours of calibration per interviewer per quarter. The ratio is the whole argument for fixing the loop.

Published averages from SHRM or Robert Half fit on a slide. Your own number is the one a director trusts.

Common questions

How much does a bad engineering hire actually cost?

A bad engineering hire costs far more than its salary. At 11,000 euro a month loaded, 9 months costs 99,000 euro in salary and overhead. That is the smallest line on the bill. Add the hiring cost twice, and your best engineers’ time covering and rewriting. Then the missed work, and the standard the team now believes in.

Do more interview rounds reduce bad hires?

No, and longer loops mostly lose good candidates instead. Three things reduce bad hires. A written bar agreed before the first CV, and scorecards submitted before the debrief. And a probation checkpoint someone actually uses. Rounds 5 and 6 re-measure what the first 3 already showed.

How do you make the case to a director?

Make the case to a director with a comparison rather than a precise figure. Take your loaded cost for the level and multiply by the months in the timeline. Add a conservative estimate of the team time. Put that next to the cost of 2 hours of calibration a quarter. The director decides on the gap between the 2 numbers.

What is the 90-day checkpoint?

The 90-day checkpoint is probation used as a decision rather than a formality. Without a date in the calendar, the month-3 signal gets carried to month 9. Put a date in the calendar at offer time. Make someone answer whether they would hire this person again.

How long does it take to replace an engineer after a bad hire?

Replacing an engineer after a bad hire runs on three clocks. The exit runs the notice period in the contract. Then the search: Ashby’s 2026 data puts the median technical hire at 40 days. A quarter take longer than 57. Then the new hire serves their own notice before day 1. Ramp-up starts again after that.

The short version

A bad hire runs 12 months. Salary is the smallest line on the bill.

The largest costs are your strongest engineers’ time and what they conclude about the bar.

Loops keep producing them because urgency is visible and false negatives are not.

No part of the process ever gets told what happened.

Write the bar before the role opens. Score evidence. Calibrate. Run the debrief as a decision. Use the 90-day checkpoint.

Fixing this is the work on this site. An audit of the loop, or a workshop sprint.

Book a free 30-minute call.

Want this fixed in your loop?

SmartHiring trains engineering interview panels on their own open roles. Elman Huseynov, a Technical Interview & Calibration Trainer in Berlin, runs every engagement. One workshop writes the scorecards for your roles, then calibration runs until the panel agrees. It starts with a free 30-minute call.

No pitch if the loop is already fine. See an example audit report.