A commonly cited floor puts the cost of a bad hire at a minimum of 30% of that role's annual salary, and for engineering roles specifically, the real damage usually shows up somewhere the salary number doesn't capture at all. Below is a transparent cost model, with every assumption shown, not just a multiplier.
See the cost modelThe commonly cited 30%-of-salary figure is a useful floor, not a ceiling. It captures recruiting cost, onboarding time, and severance, but it doesn't capture what a bad engineering hire actually does to a codebase, a team's morale, or a roadmap's timeline. Those costs are real and usually larger, which is why the model below prices them out separately instead of hiding behind one multiplier.
Multiplier estimates ("1x to 10x salary") are easy to quote and hard to trust, because the multiplier hides what's actually being counted. Below is the same math broken into its parts, on a representative $160K senior engineer who doesn't work out and leaves after roughly four months. Change the assumptions and the total moves, but the parts stay honest.
| Cost component | Stated assumption | Estimated cost |
|---|---|---|
| Recruiting & screening time | Sourcing, interview panel hours, and job-board or agency spend across a multi-week search | $10K–$15K |
| Salary paid before fully productive | ~4-6 months to reach normal output on a technical role, commonly reported range, at fully loaded cost (roughly 1.25-1.3x base) | $65K–$90K |
| Teammates' time absorbing gaps | Two engineers spend roughly a fifth of their time for 8-10 weeks covering or reworking the mis-hire's output | $20K–$28K |
| Exit costs | Severance, offboarding admin, and knowledge-transfer time | $6K–$12K |
| Repeating the search | Same recruiting cost again, plus a second vacancy period with zero output on that seat | $15K–$20K+ |
| Transparent total | Roughly 80-100%+ of the role's annual salary, on countable costs alone | $116K–$165K+ |
This total intentionally excludes the costs in the next section, morale, roadmap slippage, and technical debt, because they're real but not reliably priceable. Treat this model as a conservative floor, and build your own version with your own salary and timeline assumptions; the structure matters more than the exact dollar figure.
Code written by someone who wasn't actually qualified often gets left in production long after they're gone, quietly slowing every future change.
Strong engineers notice when a peer or manager isn't credible. That erosion shows up in engagement and, eventually, in who else decides to leave.
A mis-hire on a critical project doesn't just fail to deliver, they often consume other engineers' time cleaning up or covering for them.
The full search cost repeats, on top of everything already lost, and now with a damaged team to rebuild trust with.
A bad individual-contributor hire is costly. A bad engineering leadership hire is compounding, because they influence every hire that comes after them, every architecture decision the team lives with, and whether your strongest engineers stay or start quietly interviewing elsewhere. This is exactly why we push so hard on uncontrolled references and retention-specific questions in leadership searches, the risk profile is different.
The salary number is the smallest part of what a bad engineering hire actually costs you. The real damage is what it does to the people around them.
Using a transparent, stated-assumption model on a representative senior engineer salary, the countable costs alone (recruiting, ramp time before they were productive, teammates absorbing gaps, exit costs, and repeating the search) commonly land in the 80-100%+ of annual salary range. That's a conservative floor, since it excludes morale, roadmap slippage, and technical debt, which are real but harder to price.
Different models count different buckets. Some only include hard costs like recruiting fees and severance, landing near a 30% floor. Others add ramp-time productivity loss, teammates' time, and roadmap damage, which push the real number several times higher. The gap isn't disagreement about the math, it's disagreement about what counts.
Roughly four to six months for a technical hire to reach normal output is a commonly reported range, with some benchmarks putting the ceiling closer to a year for full performance. Senior and niche-stack roles tend toward the longer end, since there's more context to absorb before they're fully load-bearing.
Yes, and it compounds rather than just scaling with salary. A bad leadership hire shapes every hire that comes after them, every architecture call the team lives with, and whether your strongest engineers stay. The same cost model applied to a leadership salary understates the real damage for exactly this reason.
Uncontrolled reference checks and a real technical evaluation before a candidate reaches final interviews catch most of what causes a bad hire. Both are slower than skipping them, but far faster than absorbing the cost model above and running the search again.
David runs every Beacon search personally, with uncontrolled reference checks as a standard part of the process.
Book a 15-minute call. We'll tell you what the market looks like for your role and how we vet for real depth.
Book a call