A bad engineering hire costs far more than the salary you paid. Gallup puts the cost of replacing one employee at one-half to two times their annual salary, so a failed $180,000 senior engineer can run $90,000 to $360,000 before you count the months of lost output, the senior time spent cleaning up, and the morale hit to the team that covered for them.
Every engineering leader has lived through some version of it. Weeks of sourcing and interviews, a start date, and within three months it's clear something is off. By the time you part ways, the money is the smallest part of what you lost.
Key Takeaways
- Replacing an employee costs one-half to two times annual salary, and Gallup calls that a conservative estimate (Gallup).
- In a CareerBuilder survey, 74% of employers said they had hired the wrong person, at an average cost of $14,900 per bad hire across all roles (HR Dive). Senior engineering hires cost more.
- The hidden costs are time and morale: senior engineers' review hours, a stalled roadmap, and good people picking up the slack.
- Work samples and structured interviews predict job performance better than unstructured chats or puzzle questions (Sackett et al., 2022).
What Does a Bad Engineering Hire Actually Cost?
Add up the pieces for one failed senior hire. The numbers below are an illustration, not a benchmark. Swap in your own.
| Cost | What it looks like | Illustrative amount |
|---|---|---|
| Salary paid while it wasn't working | 4 months at $180k/year | ~$60,000 |
| Recruiting the first time | Recruiter fee or internal recruiter time, job ads | $20,000-$40,000 |
| Interview hours | 5 engineers x 4 hours x ~15 candidates | 300 hours of senior time |
| Onboarding and review | A senior engineer spending a third of their time on support and code review | ~1-2 months of senior output |
| Cleanup | Rewriting or re-reviewing what shipped | Weeks to months |
| Doing it all again | A second search, a second ramp | Most of the above, again |
Gallup's range covers the replacement. What it doesn't capture well is the roadmap: a feature that slips a quarter because the person who owned it couldn't deliver.
How Does a Bad Hire Affect Team Productivity and Morale?
A bad hire doesn't just fail to contribute. They slow down everyone around them. Senior engineers review weak pull requests twice, re-explain decisions, and fix bugs that shouldn't have shipped. That time comes straight out of the work only seniors can do.
Morale takes the longer hit. When strong engineers watch a poor performer stay for months, they start doubting leadership's judgment, and they're the people with the most options to leave. In the CareerBuilder survey, employers most often described a bad hire as someone with a negative attitude (53%), who didn't work well with others (50%), or who lacked abilities they claimed to have (45%) (HR Dive). Two of those three are about the team, not the code.
Why Do Bad Engineering Hires Happen?
The resume-reality gap. A resume is a claim. "Proficient in Kubernetes" might mean they finished a tutorial. Most candidates aren't lying; written credentials are just a weak proxy for shipping production code and debugging under pressure. In 2026, add AI-written resumes and candidates who read answers off a second screen.
Interviews that test the wrong thing. A friendly unstructured conversation and a few algorithm puzzles select for people who interview well. A large 2022 reanalysis of selection research found structured interviews were among the strongest predictors of job performance, well ahead of unstructured interviews (Sackett et al., 2022).
Time pressure. When a critical role has been open for two or three months, the bar slips. "Not perfect, but good enough" is how a lot of bad hires get made. Red flags you'd have caught in week one get explained away in week ten.
How Do You Avoid a Bad Engineering Hire?
- Use a work sample. Give candidates a realistic codebase and a real problem. Watch how they approach it, what they ask, and how they explain trade-offs.
- Standardize scorecards. Every interviewer scores the same competencies on the same rubric. That's what makes an interview structured, and it makes debriefs shorter.
- Test communication directly. Can they write a clear pull request description? Explain a system to a non-engineer? Disagree in a code review without starting a fight?
- Do real reference checks. Not "would you hire them again?" Ask about specific situations, how they handled ambiguity, and what they needed help with.
- Define the anti-profile. List the patterns behind your past bad hires and share it with every interviewer.
- Set a confidence bar before you start. If the team isn't clearly confident, it's a no. "Maybe" is a no.
- Plan the first 90 days. A structured 30-60-90 plan with milestones catches a mismatch in weeks instead of months. Our post on engineering onboarding metrics covers what to track.
Where a Vetting Partner Fits
A staffing partner with a real vetting process does part of this work before you meet anyone. At Ruzora, every engineer passes a graded coding assessment and an AI-led technical interview before you see a profile, and if an engineer doesn't work out for documented performance reasons, there's a replacement guarantee for 60 days from their first working day. You still interview. You just start from people who have already shown they can code.
Frequently Asked Questions
How much does a bad engineering hire cost?
Replacing an employee costs one-half to two times their annual salary, according to Gallup. For a $180,000 senior engineer, that's $90,000 to $360,000, before counting lost output and team time.
What are the hidden costs of a bad hire?
Senior engineers' time spent reviewing and fixing work, delayed features, code that has to be rewritten, a second recruiting cycle, and lower morale on the team that covered the gap.
How long should you wait before letting a bad hire go?
Set clear 30, 60 and 90-day expectations at the start. If someone is clearly missing them by day 60 despite support, waiting longer usually makes every cost above bigger.
How do you avoid bad engineering hires?
Use work samples and structured interviews with a shared scorecard, run real reference checks, and onboard against a 30-60-90 plan so problems show up early.
The Bottom Line
A bad engineering hire costs salary, time, and team trust, and the last two are the expensive ones. Test for the actual job, structure your interviews, and plan the first 90 days.
Want to start from engineers who already passed a coding test? See vetted senior LATAM engineers, or tell us the role and get a vetted shortlist within 72 hours.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers.
