Every article about bad engineering hires eventually arrives at a cost figure. The estimate tends to land somewhere between one and three times annual salary: the recruiter fees, the sign-on bonus, the salary during a short tenure, maybe a severance package. This is real money and it's reasonable to account for it.
But in five years working in recruiting operations at technical companies, I found that the financial cost was almost never the reason a wrong hire was actually damaging. The reason was always the team cost. And the team cost, because it's diffuse and doesn't show up on a single line item, almost never gets calculated at all.
The Financial Cost Is the Visible Part
Let's get the financial accounting out of the way because it's the part that gets discussed. For a mid-level backend engineer with a $160k-$190k compensation package: recruiter fee or advertising spend (roughly $15k-$25k for an agency placement), 3-4 months of salary before performance issues become undeniable (roughly $45k-$60k), severance if applicable ($5k-$20k depending on how it ends), then the cost to open the role again and hire again (another full cycle, another $15k-$25k). Call it $80k-$130k all-in, and that's before opportunity cost.
For a senior or staff engineer, the numbers are proportionally larger. For a tech lead or engineering manager, they can become substantial.
But the financial accounting misses the part that I've seen cause the most actual damage: what happens to the team during and after the wrong hire.
The Onboarding Tax: The Cost Nobody Tracks
Every new hire generates a load on the team around them. Senior engineers get pulled into pairing sessions, code reviews, and context-setting conversations. Slack channels are more active. Tickets take longer because there's more clarifying back-and-forth. This is normal and expected. A good hire generates this load and repays it quickly as they ramp.
A wrong hire generates the same load and never repays it. The team invests six to ten weeks of distributed senior-engineer time in onboarding someone who is eventually let go. That investment is not recoverable. Those code review cycles, those pairing sessions, those architecture explanation calls, they were real hours that produced nothing of lasting value for the product.
If you have four engineers and one is in the process of onboarding a new hire, the team is functionally operating at a reduced velocity for that entire window. On a small team with tight shipping commitments, this isn't a rounding error. It's the difference between making a sprint and missing it.
The Team Morale Effect: Often Worse Than the Financial Hit
A wrong hire on a small team can degrade the working environment for every other engineer in a way that takes months to repair.
The most common pattern I've seen: a new engineer struggles with a combination of technical gaps and misaligned working style. They're not malicious. They're in a role that isn't right for them. They ask a lot of questions that create interruption overhead. They miss PRs. Code review cycles become longer and more tense. They may not communicate well when they're blocked, creating coordination problems that surface at inconvenient moments.
The rest of the team is now managing two things simultaneously: their own work and the friction generated by the wrong hire. Engineers are generally too professional to say this explicitly, but it registers. In exit interview data from the teams I worked with, "team quality" and "team cohesion" appeared as departure factors more frequently than compensation in engineers who left within 18 months of a notable bad hire. That connection is hard to prove causally, but it's consistent enough to be worth taking seriously.
The Velocity Loss: How Long It Actually Takes to Recover
The velocity impact of a wrong engineering hire doesn't end when the hire ends. There's a recovery arc that lasts considerably longer than most teams expect.
After the departure, the team needs to absorb the work that was supposed to be owned by the departed engineer. Depending on what they were working on, there may be partially complete features, undocumented decisions, or code that only they understood (this is more common than it should be). The senior engineers who were pulled into onboarding now have to do triage on whatever was left behind.
The role opens again. The team is back in interviewing mode, which is itself a non-trivial time sink. Calibration discussions, screen calls, debrief cycles, offer negotiations. For a small engineering team doing 6-8 interviews over 6-8 weeks, this is a meaningful chunk of collective focus that isn't going into the product.
The new hire arrives, and the onboarding cycle starts again. From initial wrong hire to full productivity of the right replacement, the realistic timeline is often 9-14 months. That's not a theoretical cost. It's a competitive disadvantage over the period that matters most in early product development.
Prevention Is Cheaper Than Recovery
The point of doing this accounting is not to create anxiety about hiring. It's to make the case that the investment in getting the hire right is almost always justified on cost grounds alone.
A longer, more careful screen process that adds three weeks to time-to-hire is vastly cheaper than the cost of a six-month wrong hire that requires recovery. Additional interview rounds that add a week and a half of calendar time are cheap relative to 9 months of velocity loss. Better sourcing that produces five qualified candidates instead of twenty mixed-quality applications is worth paying for.
We built the working-style and culture matching layer in Fonzi specifically because the financial cost and the team cost of a wrong hire are both so disproportionate to the cost of better pre-hire signal. Stack matching is necessary but not sufficient. A technically qualified engineer who is a poor working-style fit for your specific team will generate most of the costs described in this article. The technical competence does not offset them.
The wrong hire is not the salary you paid. It's the senior engineer time absorbed into an unproductive onboarding, the morale degradation across the team, and the velocity loss that stretches months past the departure. When you price it correctly, the investment in getting the signal right at the sourcing and screening stage starts to look very different.
