The Cost of a Bad Tech Hire
A bad hire at $150,000 salary costs your company $235,000-$545,000 over 12 months. That is not a theoretical number -- it is the sum of rehiring costs, lost productivity, management time, technical debt, and team morale impact, each backed by research from SHRM, Leadership IQ, and Gallup. Here is the complete math with a framework for prevention and early intervention.
The 6 Impact Categories
Rehiring Cost
$40,000-$120,000The cost of replacing the bad hire includes all the original hiring cost components: recruiter fees ($22K-$37K), interview process ($1,350-$2,400), job board reposting ($1,500), onboarding for the replacement ($18K-$25K), and vacancy cost during the repeat search ($28K-$40K). If the original hire was through a recruiter with a guarantee, you may recover some of the fee, but most guarantees are 90 days and bad hires often last 6-8 months before termination.
Lost Productivity
$60,000-$180,000A bad hire operating at 40-60% of expected output for 8 months costs $48,000-$90,000 in direct productivity loss. But the indirect impact is larger: teammates spend 15-25% more time reviewing substandard work, fixing bugs introduced by the bad hire, and compensating for missed deliverables. For a team of 6 engineers, this secondary productivity drag costs $30,000-$90,000 across the team over the bad hire's tenure.
Management Time
$15,000-$45,000Managers spend 3-5x more time on underperforming employees: additional 1:1 meetings, performance improvement plans, documentation for HR, conversations with the team about workload redistribution, and eventually the termination process itself. At a senior engineering manager's blended rate of $100-$150/hour, 150-300 extra hours over 8 months totals $15,000-$45,000 in management time diverted from the rest of the team.
Technical Debt
$20,000-$80,000Code written by a bad hire often requires significant remediation after their departure. Poorly designed systems, inadequate test coverage, insecure code, and architectural decisions that do not scale create technical debt that subsequent engineers must fix. A senior engineer spending 2-4 months remediating a bad hire's code output costs $30,000-$75,000 in engineering time, plus the opportunity cost of those engineers not building new features.
Team Morale and Attrition
$100,000+The hardest cost to quantify but often the largest. High performers on the team who see a bad hire tolerated for months lose confidence in leadership's judgement. Gallup data shows that employees working alongside chronic underperformers are 54% more likely to leave within 12 months. If one high performer leaves because of the bad hire situation, the replacement cost ($50K-$120K) exceeds many of the other categories combined. Two departures can destroy a team.
Customer and Product Impact
Variable ($0-$500K+)Bad hires in customer-facing roles or on critical product features can cause direct revenue impact through bugs, poor customer interactions, or delayed launches. A month-long delay in a product launch caused by a bad hire's underperformance can cost $100K-$500K+ in deferred revenue. Security vulnerabilities introduced by a bad hire can have catastrophic cost implications. This category is highly variable but represents the tail risk of bad hiring decisions.
Prevention Framework
Investing $5,000-$15,000 per hire in improved assessment processes can prevent bad hires that cost $235,000-$545,000. The ROI is 15-35x. These five interventions have the strongest evidence base for reducing bad hire rates in tech:
Structured Interviews
Replace unstructured conversational interviews with standardised questions, behavioural examples, and calibrated rubrics. Every candidate answers the same questions and is scored on the same dimensions by trained interviewers. Meta-analysis shows structured interviews are 2x more predictive of job performance than unstructured formats.
Work Sample Tests
Replace algorithmic whiteboard problems with realistic work samples: debug actual codebase issues, design a real system component, or extend an existing feature. Work samples are the single strongest predictor of job performance (r=0.54 validity) versus cognitive ability tests (r=0.51) or unstructured interviews (r=0.38).
Structured Reference Checks
Move beyond 'would you hire them again' to competency-specific questions: 'How did they handle disagreement with technical decisions?', 'Describe a time they received critical feedback on their code -- how did they respond?', 'What was their ramp time in your organisation?'. Structured references predict 12-month tenure with 78% accuracy.
30-60-90 Day Review Process
Establish explicit success criteria for the first 30, 60, and 90 days before the hire starts. Review performance against these criteria at each milestone. This creates a structured framework for early identification and gives both the hire and manager clear expectations. Companies with this process act on bad hires 3-4 months faster than those without.
Early Warning Signs
The 8.4-month average time between identifying a bad hire and acting on it is the most expensive aspect of this entire problem. Every month of delay costs $10,000-$25,000. Recognising these warning signs in the first 30-60 days and taking swift action can reduce the total impact by 60-80%.
Unable to ramp on core tools and processes despite adequate onboarding support and documentation
Pattern of missing commitments or deadlines without proactive communication about blockers
Defensive responses to code review feedback or resistance to team technical standards
Isolation from team activities, reluctance to ask questions, or avoidance of pair programming
Misalignment between interview-demonstrated skills and actual performance on real tasks
Negative impact on team dynamics: complaints from teammates, decreased collaboration quality
Related Resources
Frequently Asked Questions
How much does a bad tech hire cost?
A bad tech hire typically costs 1-3x their annual salary, ranging from $150,000 to $500,000+ for senior roles. The six cost categories are: rehiring ($40K-$120K), lost productivity ($60K-$180K), management time ($15K-$45K), technical debt remediation ($20K-$80K), team morale and attrition ($100K+), and customer/product impact (variable). SHRM estimates the average cost at 30% of salary for entry-level, but tech-specific data shows much higher figures.
What percentage of new hires are bad hires?
According to Leadership IQ research, 46% of new hires fail within 18 months. For tech roles specifically, the failure rate is approximately 28% within 12 months (SHRM Talent Acquisition Benchmarks). The most common reasons: 26% cannot accept feedback, 23% cannot manage emotions, 17% lack motivation, 15% have the wrong temperament, and only 11% lack technical skills. Technical competence is rarely the issue.
How quickly can you identify a bad hire?
50% of hiring managers report knowing about a bad hire within 30 days. However, the average time to act (termination or performance management) is 8.4 months. This delay is the most expensive aspect of a bad hire -- each month of inaction costs the company $10,000-$25,000 in continued salary, lost productivity, and compounding management burden. Companies with structured 30-60-90 day review processes act 3-4 months faster.
How can companies prevent bad tech hires?
Five evidence-based interventions: 1) Structured interviews with calibrated rubrics (reduces bad hire rate by 25-30%), 2) Work sample tests over whiteboard coding (better predictor of actual job performance), 3) Reference checks focused on specific competencies (not just 'would you hire them again?'), 4) Realistic job previews (reduces first-year turnover by 20%), 5) Probationary periods with clear success criteria (enables faster identification and action on mismatches).
What are the early warning signs of a bad hire?
Warning signs within the first 30-60-90 days: inability to ramp on core tools and processes despite adequate onboarding, pattern of missing commitments or deadlines without communication, resistance to feedback or defensive responses to code review comments, isolation from team activities and reluctance to ask for help, and misalignment between interview-demonstrated skills and actual performance on real tasks.