The Cost of a Bad AI Hire (It Is Not the Salary)
The cost of a bad AI hire is not the salary you wasted. It is the un-evaluated system they shipped, the roadmap that stalled, and the trust your team lost.
The cost of a bad AI hire is not the salary you wasted. It is the un-evaluated system they shipped, the roadmap that stalled, and the trust your team lost.
The cost of a bad AI hire is not the salary. The salary is the receipt you can see; the real cost is the un-evaluated AI system that person shipped, the four months of ramp you paid for before it broke, the roadmap that did not move while they were here, and the senior engineers you pulled off real work to clean it up. Add it up and a single bad AI hire on a senior seat routinely runs six figures, most of it invisible until a customer finds it for you.
I have hired and deployed more than 80 senior AI engineers at Devlyn, and I have also paid for the wrong ones. I sit in two seats at once: I read the model traces, and I read the P&L. From that seat, the salary line is the part of a bad hire I worry about least. This piece is the cost-of-failure deep-dive that branches off my pillar guide to hiring AI engineers, and I am going to give you the whole number, including the part of it that is specific to AI and that no generic hiring article will ever quote you.
- The salary is the floor, not the cost. Generic benchmarks put a bad hire at 30% to 50% of annual salary; for a senior AI engineer the all-in number is several times that once you count ramp, opportunity, and cleanup.
- The AI-specific cost is silent failure. A bad AI hire ships a system with no evals and no observability; it demos clean and fails in production, where the failure surfaces as churn, not a stack trace.
- Opportunity cost is the largest line. The roadmap that did not ship while a weak hire ramped and was replaced usually dwarfs the direct replacement cost.
- Morale compounds the bill. Seniors pulled into cleanup ship less and trust the AI less; that drag outlasts the person who caused it.
- You can compute your own number, and you should. A finance-ready estimate is the cheapest insurance against making the same hire twice.
If you are weighing this cost right now because a hire is not working, or because you are about to make one and want the math first, the fastest way to take the hiring risk off the table is to start with vetted senior engineers on a trial. That is exactly what Devlyn's AI application engineers are for: senior, trial-first, priced as an outcome rather than a gamble.
The visible cost everyone quotes, and why it is the small number
Start with the number you can already find. Generic hiring research puts the cost of a bad hire at roughly 30% of the employee's first-year earnings, a figure commonly attributed to the U.S. Department of Labor, and the widely cited 50% to 200% replacement range from HR sources scales with seniority. A CareerBuilder survey famously pegged the average bad hire at about $14,900, with 74% of employers admitting they had hired the wrong person. Those numbers are real, and they are the floor.
The visible cost is the stuff that hits an invoice. It is the salary you paid for the months the person was on the team. It is the recruiter fee or the sourcing time, the severance if there was any, and the cost of running the search a second time. For a US senior AI engineer at a $180,000 base, even the conservative benchmark math lands you in the $54,000 to $90,000 range before you have priced anything that does not appear on a payroll report.
I call this the small number on purpose. It is the part of the cost that finance already understands and that every cost-per-hire calculator will hand you. It is also, in my experience, less than half of what a bad AI hire actually takes out of the business. The benchmark articles stop here because the rest of the cost is hard to see and harder to attribute, which does not make it any smaller.
The hidden cost: ramp, opportunity, and morale
A senior AI engineer does not ship production-grade work on day one. There is a ramp: learning your stack, your data, your model behavior, your definition of good. You pay full salary through all of it, and with a bad hire you discover at the end of that ramp that the work does not hold up. The ramp was not an investment that paid off; it was a sunk cost you cannot recover.
Opportunity cost is the line that almost nobody computes and that is almost always the largest. While the wrong person occupied the seat, the roadmap did not move; the feature that should have shipped in Q2 slips to Q4. The competitor who shipped it in Q2 takes the customers who would have been yours. That gap does not show up on any invoice, but it shows up in revenue, and it is frequently larger than salary, ramp, and replacement combined.
Then there is morale, which is real money wearing soft clothes. When a hire ships work that breaks, your good engineers stop their own work to fix it and review everything more defensively. They learn, quietly, that the AI in your product cannot be trusted, and that distrust slows every future decision. I have watched one weak hire turn a fast team into a cautious one, and the caution outlasted the person by quarters.
The AI-specific cost nobody prices: the un-evaluated system that fails silently
Here is the cost that makes a bad AI hire categorically worse than a bad hire in any other engineering role. In most software, a weak engineer writes code that breaks loudly. It throws an exception, the build goes red, a test fails, and you find out in CI before a customer ever sees it. The failure is visible, and visibility is mercy.
AI does not fail that way. A bad AI hire ships a system that compiles, demos beautifully in the room, and is confidently wrong in production, with no evals behind it because the person did not know to build them or did not bother. There is no observability either, so when the model starts hallucinating on real traffic, nothing turns red. The failure surfaces as a customer who got a wrong answer, lost trust, and left, and you learn about it from churn and support tickets weeks later, long after the cause is cold.
This is not a rare edge case; it is the dominant pattern. RAND's 2024 research found that more than 80% of AI projects fail, roughly twice the failure rate of non-AI IT projects. A large share of that failure is judgment that was never evaluated for: shipping un-instrumented systems, mistaking a clean demo for a production-ready one, and treating the model's confident output as correct output. That is precisely the judgment a good vetting process screens for and a bad hire lacks.
Let me make it concrete with an NDA-safe composite. A team I advised hired a strong-on-paper engineer who shipped a customer-facing assistant that tested perfectly on the handful of prompts they tried in the demo, then confidently gave wrong account information to a slice of real users. There were no evals, no logging of model outputs, and no alerting. The team found out from a spike in support escalations, spent three senior-weeks reconstructing what the system had been telling people, and spent more rebuilding customer trust than they ever spent on the build; the salary was the cheapest part of that quarter.
A cost breakdown you can put in front of finance
Here is the full cost of a bad AI hire, broken into the lines that actually make it up. The figures are illustrative, modeled on a US senior AI engineer at a $180,000 base who is on the team for about five months before being replaced. Your numbers will differ; the structure will not.
| Cost line | What it is | Illustrative figure | Who absorbs it |
|---|---|---|---|
| Wasted salary and benefits | Fully loaded comp for months on the team with no durable output | $90,000 | Finance |
| Recruiting and replacement | Sourcing, fees, and running the search a second time | $25,000 | Talent / HR |
| Ramp written off | Onboarding and senior time spent bringing them up that returns nothing | $30,000 | Engineering |
| Cleanup and rework | Senior engineers pulled off roadmap to fix the un-evaluated system | $60,000 | Engineering |
| Opportunity cost | Roadmap that did not ship; revenue and position lost to the delay | $120,000+ | Revenue / the business |
| Trust and morale | Defensive review, slower decisions, churn from production failures | Hard to price, rarely zero | Everyone |
The visible lines at the top sum to about $115,000. The hidden lines below them are where the number more than doubles, and the largest of those is the opportunity cost that no calculator will hand you. This is why I tell founders that the salary is the receipt, not the bill. The bill arrives later, in pieces, from departments that never approved the hire.
How to compute the cost of a bad AI hire for your team
You do not need a perfect figure; you need a defensible one. The formula is simple enough to run on a napkin, and running it once before a hire is the cheapest diligence you will ever do.
// Cost of a bad AI hire, illustrative formula wasted_comp = monthly_loaded_cost * months_on_team replacement = recruiting_fee + second_search_cost ramp_writeoff = onboarding_weeks * senior_weekly_cost cleanup = cleanup_weeks * senior_weekly_cost opportunity = delayed_revenue_or_roadmap_value
total = wasted_comp + replacement + ramp_writeoff + cleanup + opportunity // morale and churn are real; add a deliberate buffer, do not set them to zero
Work a quick example. A senior at $180,000 base is roughly $20,000 a month fully loaded; five months on the team is $100,000 in comp before anyone ships. Add $25,000 to replace them, $30,000 in ramp you wrote off, and six senior-weeks of cleanup at about $10,000 a week, and you are at $215,000 before opportunity cost. Put any reasonable number on the quarter of roadmap that slipped, and the total clears a quarter of a million dollars for a single hire.
That math is the argument for spending more on vetting and seniority up front, not less. Every dollar you move from cleaning up a bad hire to preventing one buys you leverage, because prevention is cheap and the failure is expensive. For the other side of this ledger, what a good AI engineer actually costs to hire well, I wrote a full breakdown in the AI engineer cost guide.
How to avoid the cost of a bad AI hire: vet, hire senior, or partner
The cost of a bad AI hire is almost entirely preventable, and the prevention is not mysterious. It comes down to three moves, in order of how much risk they take off the table.
First, vet for judgment, not vocabulary. The engineer who can describe RAG is not the same as the one who will instrument it, evaluate it, and refuse to ship it without observability. Vet for the habits that prevent silent failure: do they build evals, do they log model outputs, do they distrust a clean demo. My guides on how to vet AI engineers and the red flags that predict a bad AI hire are the screening playbook I actually use.
Second, bias toward seniority on anything that touches production. The single most expensive mistake I see is hiring a junior into a role that needs judgment and hoping the title grows into the work. In AI, where failure is silent, the gap between senior and junior is not speed, it is whether the system fails safely; I made the full case in senior vs junior AI engineer.
Third, if you cannot absorb the hiring risk, do not absorb it. The reason a transparent-rate partner exists is to move the variance off your books: vetted senior engineers, a trial before you commit, and an outcome you can hold rather than a resume you have to bet on. That is the model behind Devlyn's AI application engineers, and it is the most direct way to make the cost of a bad AI hire someone else's problem to underwrite. The deeper framework for building a team that does not generate these costs is in my book, Building an AI-Native Team.
Frequently asked questions
What is the real cost of a bad AI hire?
The benchmark floor is 30% to 50% of annual salary, but for a senior AI engineer the all-in cost commonly runs $150,000 to $300,000 or more once you add wasted ramp, senior cleanup time, lost roadmap, and the production damage from an un-evaluated system. The salary is the smallest part of that total. The largest is usually the opportunity cost of the roadmap that did not ship while the wrong person held the seat.
Why is a bad AI hire more expensive than a bad hire in other roles?
Because AI fails silently. A weak engineer in most roles writes code that breaks loudly in CI, so you catch it before a customer does. A bad AI hire ships a system with no evals and no observability that demos clean and is confidently wrong in production, so the failure surfaces as churn and support tickets weeks later, when the cause is cold and the trust is already spent.
How do I calculate the cost of a bad hire for my own team?
Add wasted loaded comp for the months on the team, recruiting and second-search costs, the ramp you wrote off, senior cleanup time, and the value of the roadmap that slipped, then add a deliberate buffer for morale and churn rather than setting them to zero. Run that number before you hire, not after. A defensible estimate beats a precise one, and it is the cheapest diligence you will do.
How do I avoid the cost of a bad AI hire?
Vet for judgment rather than vocabulary, bias toward seniority on anything that touches production, and if you cannot absorb the hiring risk, use a trial-first partner so the variance lives on someone else's books. The habits that prevent silent failure, building evals and instrumenting outputs and distrusting a clean demo, are screenable, and screening for them up front is far cheaper than cleaning up after a hire who lacks them.
If the math in this piece describes a hire you are about to make, or one you are currently regretting, the lowest-risk path is to start with vetted senior engineers on a trial rather than betting a quarter of roadmap on a resume. That is what Devlyn's AI application engineers are built for. Price the bad hire honestly, then make sure you never pay it twice.