The Real Cost of a Bad Tech Hire
Updated 26 March 2026
The US Department of Labor estimates a bad hire costs 30% of first-year salary. For tech roles, the real number is closer to 1-3x annual salary when you account for all the knock-on effects.
Example: Bad hire at $150,000/year salary
$235,000 - $545,000
Total estimated impact over 12 months, including rehiring, lost productivity, management time, and technical debt
Direct Rehiring Cost
$40,000 - $120,000When a bad hire leaves or is let go, you pay the full hiring cost again. For a $140k engineer this is $52,000-$70,000 in recruiter fees, interview time, and onboarding. If the bad hire lasted 12 months, you have effectively paid two years of hiring costs.
Lost Productivity During Tenure
$60,000 - $180,000A bad tech hire typically operates at 40-60% of the expected productivity level throughout their tenure. For a $150k developer over 12 months, that is $60,000-$90,000 in underperformance. Multiply by team drag effects and the total can reach 2x.
Management Time
$15,000 - $45,000Engineering managers and senior engineers spend disproportionate time managing, reviewing, and fixing the work of a bad hire. Research consistently shows managers spend 2-3x as much time on underperformers as high performers. That time has an opportunity cost.
Technical Debt Created
$20,000 - $80,000Code written by a substandard developer often requires significant remediation. Technical debt created by a bad hire typically takes 6-18 months to fully address. If 3 senior developers spend 10% of their time cleaning up bad code for a year, that is $50,000-$70,000.
Team Morale and Attrition Risk
Potentially $100,000+High performers are sensitive to quality standards. A visible bad hire who is not managed out signals poor leadership judgment and can drive top performers to look elsewhere. Losing one senior developer due to morale issues costs another $80,000-$120,000 in replacement costs.
Customer and Product Impact
VariableIn customer-facing or critical infrastructure roles, the impact of a bad hire extends to product quality, system reliability, and customer satisfaction. Bugs shipped, features delayed, and incidents caused all carry financial consequences beyond HR metrics.
How to reduce bad hire risk
- Use structured interviews with consistent scoring rubrics across all candidates
- Include a practical technical assessment relevant to the actual work, not abstract puzzles
- Check references with specific questions about performance and working style
- Set explicit 30-60-90 day success criteria and review against them honestly
- Do not ignore early red flags in the first 30 days: act on them quickly
- Involve the team in the hiring decision, as they will spot culture mismatches you might miss
Calculate your hiring cost baseline
Know what you are investing per hire so you can make the case for better process.
Open Calculator