Ask any hiring manager what the cost of a bad hire is and you will probably hear the same answer: “about 30% of their first-year salary.” It is quoted in board decks, vendor brochures and LinkedIn posts. It is also, for technical roles, badly wrong.
When we rebuilt the math for a single mis-hired senior software engineer, line by line, the total came to roughly $121,000 — about 86% of salary, nearly three times what the 30% rule predicts. And that is before counting a delayed product launch, a security incident or a lost customer.
This guide shows exactly where that money goes, gives you a formula to calculate the cost of a bad hire for any IT role, and lays out a seven-step playbook to make sure it does not happen on your team.
Key Takeaways
- The popular “30% of first-year earnings” figure is widely attributed to the U.S. Department of Labor, but no current primary DOL source for it has been found. Treat it as folklore, not a benchmark.
- For a $140,000 senior engineer who leaves after five months, a conservative model puts the cost of a bad hire at about $121,000.
- The biggest line items are not recruiting fees. They are wasted salary, team drag, rework and the second ramp-up.
- Technical mis-hires cost more than most because of access, code ownership and the way mistakes compound in shared systems.
- Most bad IT hires trace back to the process — a vague requisition, a keyword screen, a rushed loop — not to bad luck.
Table of Contents
- The “30% Rule” Everyone Quotes
- What Counts as a Bad IT Hire?
- The 8 Buckets That Make Up the Cost of a Bad Hire
- Worked Example: A $140,000 Senior Software Engineer
- Why Bad Tech Hires Cost More Than Other Hires
- 6 Root Causes of Bad IT Hires
- The 7-Step Prevention Playbook
- A Formula to Calculate Your Own Number
- Warning Signs in the First 90 Days
- FAQ
The “30% Rule” Everyone Quotes (and Why You Shouldn’t)
Search for the cost of a bad hire and the first dozen results repeat one line: the U.S. Department of Labor says a bad hire costs at least 30% of the employee’s first-year earnings. The number is tidy, easy to remember and endlessly recycled. The problem is that independent researchers who went looking for the original DOL publication have not been able to find it in any current primary source.
Even if the figure were properly sourced, a single percentage cannot fit every role. A mis-hired help-desk technician and a mis-hired principal cloud architect do not fail in the same way, for the same length of time, or with the same blast radius. A flat 30% understates the damage on senior technical roles and can overstate it on simple, well-supervised ones.
There is also a measurement gap. According to SHRM’s benchmarking data, only around one in five organizations formally tracks quality of hire. If most companies do not measure hiring outcomes, most also have no idea what their failures actually cost them — which is exactly why a borrowed rule of thumb fills the vacuum.
What Counts as a Bad IT Hire?
Before calculating anything, define the failure. In IT staffing we see four distinct types, and each carries a different cost profile:
- The capability miss. The person interviewed well but cannot do the work at the level the role needs. This is the most expensive type because it hides the longest.
- The level miss. A strong mid-level engineer hired into a senior or lead role. They are competent, just not at the scope you are paying for.
- The early leaver. Good hire, wrong match on pay, remote policy or role scope, and they are gone in under six months. Our guide to why IT candidates say no covers the same misalignment at offer stage.
- The integrity failure. Misrepresented experience, a proxy interviewer or outright identity fraud. This one is rising fast — see our breakdown of fake IT candidates and deepfake interviews.
The 8 Buckets That Make Up the Cost of a Bad Hire
The true cost of a bad hire is not one number. It is the sum of eight separate buckets, most of which never appear on a single budget line.
1. Recruiting the first hire
Job ads, sourcing tools, recruiter time and any agency fee. SHRM’s 2025 benchmarking puts average cost per hire at $5,475 for non-executive roles — and specialized technical roles usually run higher. If you used an agency on a permanent placement, the fee is often a percentage of first-year salary; our explainer on IT staffing agency cost breaks down typical ranges.
2. Interview loop time
A typical engineering loop pulls in a hiring manager, two or three engineers and sometimes a product lead. Those hours come straight out of delivery work, and they are paid at senior rates.
3. Onboarding, equipment and access
Laptops, software licences, cloud accounts, security reviews and the time IT spends provisioning — and later de-provisioning — all of it.
4. Wasted salary (pay minus output)
This is the largest bucket and the one most often ignored. You pay full loaded compensation while getting a fraction of the expected output. Loaded means benefits too: the Bureau of Labor Statistics measured private-industry compensation at $46.15 per hour in December 2025, of which $13.79 was benefits — roughly 43% on top of wages.
5. Team drag
Senior engineers spend extra hours reviewing pull requests, re-explaining architecture and pairing to unblock. Managers spend time on coaching, documentation and, eventually, a performance plan.
6. Rework and technical debt
Code that shipped still has to be understood, fixed or rewritten after the person leaves. In infrastructure roles this can include misconfigured environments and undocumented changes.
7. Separation
Severance, HR and legal time, final pay and, in some cases, the risk of a dispute.
8. Rehiring and the second ramp-up
You pay to recruit again, and the replacement needs its own ramp-up period. Every week the seat sits empty or under-productive pushes the roadmap back — the same problem we tackle in our guide to reducing time-to-fill for IT roles.
Worked Example: The Cost of a Bad Hire for a $140,000 Senior Software Engineer
Here is a deliberately conservative scenario. A company hires a senior software engineer at a $140,000 base salary. It becomes clear around month three that they are working well below the required level; they exit at the end of month five. We assume a benefits load of about 43% (in line with BLS data), giving a loaded cost of roughly $16,630 per month, and an internal engineering cost of $100 per hour for colleagues’ time.
| Cost bucket | Assumption | Cost |
|---|---|---|
| Recruiting the first hire | SHRM non-executive average plus ~24 hours of interview time | $7,875 |
| Onboarding and equipment | Laptop, licences, provisioning | $3,000 |
| Wasted salary | 5 months loaded pay ($83,150) at 40% of expected output | $49,890 |
| Team drag | 5 hours a week of senior time for 20 weeks | $10,000 |
| Rework and cleanup | 3 weeks of a senior engineer’s time | $12,000 |
| Separation | 2 weeks’ severance | $5,385 |
| Recruiting the replacement | Same as first hire | $7,875 |
| Second ramp-up | 3 months at 50% productivity | $24,945 |
| Total | About 86% of base salary | $120,970 |
Under the 30% rule, this hire would have “cost” $42,000. The line-by-line figure is nearly three times that. Swap in an agency placement fee instead of the SHRM average and the total climbs higher still.
What this model leaves out
The $121,000 is a floor, not a ceiling. It excludes several costs that are real but hard to price without company-specific data:
- Delayed revenue from a feature or launch that slipped.
- Morale and attrition when strong engineers get tired of carrying a weak teammate.
- Security and compliance exposure if the person had production or data access.
- Customer impact from outages or bugs that reached users.
Why Bad Tech Hires Cost More Than Other Hires
Technical roles amplify the cost of a bad hire for four reasons.
Shared systems compound mistakes. A salesperson’s weak quarter mostly affects their own numbers. An engineer’s weak code sits in a shared codebase that everyone else builds on top of.
Problems hide for longer. Technical underperformance is often invisible to non-technical managers until a release slips or an incident happens. The longer it hides, the larger bucket four becomes.
Access is broad. Engineers, DevOps staff and security analysts frequently hold keys to production, customer data and cloud billing. That is why screening for judgment matters so much in roles like the ones covered in our DevOps hiring guide and cybersecurity staffing guide.
Ramp-up is long. A senior engineer typically needs months to become fully productive in a complex codebase, so every restart is expensive.
6 Root Causes of Bad IT Hires
After years of filling technical roles, we rarely see bad hires caused by bad luck. They almost always trace back to one of these six process failures:
- A vague requisition. “Senior full-stack developer” with a 20-tool wish list tells nobody what success looks like in month six.
- Keyword screening. Filtering on tool names rewards resume writing, not engineering ability.
- Panic hiring. A deadline or a resignation creates pressure to accept “good enough.”
- Unstructured interviews. Each interviewer asks whatever they like, so feedback cannot be compared.
- No real-work evaluation. Trivia questions and whiteboard puzzles instead of problems that look like the actual job.
- Weak verification. References, identity and employment history taken at face value.
The 7-Step Playbook to Reduce the Cost of a Bad Hire
Step 1: Write a scorecard, not a job description
Define three to five outcomes the person must deliver in their first six to twelve months. Every interview question should map to one of them.
Step 2: Separate must-haves from nice-to-haves
Limit hard requirements to what genuinely cannot be learned on the job. Long wish lists shrink your pool without improving quality.
Step 3: Use a structured, consistent loop
Same questions, same scoring rubric, written feedback submitted before the debrief so the loudest voice does not decide.
Step 4: Test with work that looks like the job
A short, paid or time-boxed exercise based on a real problem — debugging an existing service, reviewing a pull request, designing a small system — reveals more than any number of algorithm puzzles.
Step 5: Verify identity and history
Camera-on interviews, consistent identity checks from first screen to first day, and references you source yourself rather than only those the candidate provides.
Step 6: De-risk with contract-to-hire where it fits
For roles where fit is hard to judge in interviews, a trial period caps your exposure. If it does not work out, the engagement ends without severance or a second permanent search. Our guide to contract-to-hire IT staffing explains how conversion fees and timelines work, and the contract vs permanent comparison helps you choose per role.
Step 7: Run a real 30-60-90 day plan
Set clear milestones and check them. Catching a mis-hire at day 45 instead of month five cuts the wasted-salary bucket by more than half.
A Formula to Calculate the Cost of a Bad Hire for Any IT Role
Plug your own numbers into this structure:
Total cost = Recruiting (×2) + Onboarding + (Loaded monthly pay × Months employed × Output gap %) + Team drag hours × Hourly rate + Rework hours × Hourly rate + Separation + (Loaded monthly pay × Ramp months × Ramp gap %)
Two inputs matter more than any other: months employed and output gap. That is why the fastest way to lower the number is not cheaper recruiting — it is catching a mismatch earlier, or not making it at all.
Warning Signs You Made a Bad Hire in the First 90 Days
- Onboarding tasks that should take days are still open after weeks.
- Pull requests repeatedly need major rework, or they rarely appear at all.
- The person struggles to explain decisions in their own words.
- Their performance on camera differs sharply from the interview.
- Teammates quietly route work around them.
If you see two or more of these, act early: have a direct conversation, set written milestones and decide within weeks rather than quarters. Disengagement is expensive across the economy too — Gallup’s State of the Global Workplace research links low engagement to hundreds of billions in lost productivity each year.
How KJIT Solutions Lowers the Cost of a Bad Hire
At KJIT Solutions, our IT staffing, contract hiring, permanent recruitment and workforce solutions are built around the prevention steps above. We scope every role against outcomes, screen with technical specialists rather than keyword filters, verify identity and history, and offer contract and contract-to-hire models so you can validate fit before committing. If you are comparing partners, our 12-point agency checklist shows what to ask any firm — including us — and our engagement model guide helps you decide which structure fits your roadmap.
Frequently Asked Questions
What is the average cost of a bad hire?
There is no reliable single average because few companies track hiring outcomes. For technical roles, a line-by-line model typically lands well above the commonly quoted 30% of salary; our worked example for a $140,000 senior engineer came to about $121,000, or 86% of base pay.
Did the Department of Labor really say a bad hire costs 30% of salary?
The claim is widely attributed to the DOL, but researchers have not been able to locate it in a current primary DOL publication. It is best treated as an unverified rule of thumb.
What is the biggest hidden cost of a bad hire?
Wasted salary — the gap between what you pay in loaded compensation and the output you actually receive. In our example it was more than 40% of the total, far larger than the recruiting fee.
How quickly should you act on a bad hire?
As soon as the pattern is clear, usually within the first 60 to 90 days. Each extra month adds a full month of loaded pay to the loss and pushes the replacement search back.
Does contract-to-hire reduce the cost of a bad hire?
Often, yes. A trial period lets you evaluate real work before a permanent commitment, and ending a contract avoids severance and a second permanent search. It works best for roles where on-the-job fit is hard to judge in interviews.
Conclusion: Stop Quoting 30% and Start Measuring
The cost of a bad hire in IT is not a tidy percentage. It is wasted salary, lost team hours, rework and a restarted search — and for a senior engineer it can easily approach a full year’s pay. The companies that hire well are not luckier. They define success before they source, test with real work, verify what they are told and catch problems early.
Hiring for a critical technical role and cannot afford to get it wrong? Talk to the KJIT Solutions team about vetted IT talent on contract, contract-to-hire or permanent terms — your partner in smart hiring.