Cost drivers
The Cost of a Bad Tech Hire: $150K to $500K+
Leadership IQ research shows 46% of new hires fail within 18 months. SHRM puts the cost at 50-200% of annual salary depending on level. For tech roles the impact is bigger because the work compounds: bad code, broken systems, lost team trust.
The math
A bad hire at $150K salary who exits at month 8 costs roughly $235,000-$545,000 across 6 impact categories. That is 1.5x to 3.5x annual salary in real cost. Calculate yours below.
Bad hire impact calculator
Total bad hire cost
$238,470
Roughly 1.6x annual salary
6 impact categories of a bad tech hire
Each is a quantifiable cost. The calculator above applies these to your specific scenario.
Rehiring cost
$40K-$120KPer SHRM data, rehiring costs roughly equal the original hiring cost: recruiter fee, interview time, onboarding ramp loss for the replacement. For a senior tech role this is $40,000-$80,000 in direct costs alone, more if you go to retained search after losing confidence in your sourcing channel.
Lost productivity during tenure
$60K-$180KA bad hire typically delivers 30-50% of expected output. Over 8 months, that gap on a $150K salary is $40K-$50K just in opportunity cost. The team output usually drops further because their work creates rework downstream.
Management time
$15K-$45KEngineering managers spend 4-10 hours per week on performance issues with a struggling hire. At a $150/hr loaded EM rate, 6 hours x 32 weeks = $28,800 of management time that should have gone to roadmap or other reports.
Technical debt and rework
$20K-$80KBad code from a bad hire compounds. Engineer-weeks spent reading, refactoring, or replacing their work add up. Senior engineers frequently report 4-12 weeks of cleanup after a bad hire exits, at $4,000+ per engineer-week loaded.
Team morale and attrition
$100K+Gallup data shows that 1 disengaged team member affects engagement scores across the team. The cost of one good engineer leaving because of a bad teammate easily exceeds $100,000 (the cost of replacing them, plus their lost productivity during their last weeks). Many teams report at least one regretted attrition tied to a bad hire.
Customer and product impact
VariableHardest to quantify but often the largest cost. Bad hires in customer-facing engineering roles cause incidents, deploy bugs, and missed deadlines. One McKinsey case study tracked $1.2M in customer churn back to a single bad senior engineering hire over an 11-month tenure.
Bad hire statistics
46%
of new hires fail within 18 months (Leadership IQ)
89%
of failures are attitude / culture, not skills (Leadership IQ)
8.4 mo
average tenure of a bad hire before exit
50%
of hiring managers knew within 30 days but waited too long
Prevention framework
Most prevention advice focuses on hiring better. The data says hiring better only takes you so far - attitude problems are hard to detect in interviews. The bigger lever is identifying bad hires faster and acting on them sooner.
Better hiring
Structured interview rubrics
20-30% reduction in bad hires
Work-sample tests over algorithm puzzles
15-25% better calibration
Reference checks with former direct reports (not just managers)
Catches attitude issues
Multi-interviewer calibration sessions
10-15% reduction in disagreement-driven misshires
Pay for take-home challenges
Higher completion rates, better signal
Faster identification
30-60-90 day check-ins with explicit success metrics
Catches issues 4-8 weeks earlier
Peer feedback loops at day 30
Surfaces team-fit issues early
Manager training on performance conversations
Reduces wait-and-hope tenure by 2-3 months
Probation-like 90-day formal review
Creates clear off-ramp
PIP playbook ready before issues arise
Faster, fairer, lower legal risk
Early warning signs
What to watch for in the first 90 days. Single instances are normal; patterns are warning signs.
Days 1-30
- !Not asking questions during onboarding
- !Avoiding pair programming or code reviews
- !Defensive posture on early feedback
- !Slow to integrate with team rituals
Days 31-60
- !Still cannot ship a small change without help
- !Misalignment with role expectations
- !Repeated lateness or missed standups
- !Peer-feedback themes about communication
Days 61-90
- !Output 50%+ below expected for level
- !Conflicts with multiple teammates
- !Resistance to standards (testing, review, on-call)
- !Misrepresentation of progress in updates
If three or more signs appear in a phase, escalate to a structured performance conversation. The cost of a 60-day awkward conversation is much smaller than the cost of an 8-month bad hire.
FAQ
How much does a bad tech hire actually cost?
For a $150K salary tech hire that exits at month 8, expect $235,000 to $545,000 in total impact across rehiring, lost productivity, management time, technical debt, team morale, and customer impact. SHRM benchmarks put the cost at 50-200% of annual salary depending on seniority and the role's leverage on the team.
How quickly should we act on a bad hire?
Sooner than feels comfortable. Leadership IQ data shows half of hiring managers know within 30 days but wait an average of 5 months to act. The cost of a 30-day awkward conversation is dramatically smaller than 5 months of underperformance plus eventual exit.
What is the difference between a bad hire and a slow start?
Slow starts ramp eventually. Bad hires do not. The clearest signal is trajectory: a slow start at day 30 should be visibly better at day 60 and approaching expectations by day 90. A bad hire stays flat or regresses despite mentoring and feedback.
Should we use a contractor-to-hire pattern to avoid bad hires?
Yes for the right scenarios. A 3-month contract gives you live data on output, communication, and team fit before committing to FTE. The cost is roughly equivalent to direct hire when you include conversion fees, but the risk of a bad hire drops by 50-70%. See contractor vs FTE TCO.
Are remote hires more likely to fail than in-office?
Slightly, in 2026 data, but the gap is shrinking. Remote-failure rates run 5-8 percentage points higher than office-failure rates, mostly tied to weak async-collaboration screening. Companies that test specifically for remote work skills see no meaningful difference.