Bad hires in IT recruiting: Costs and prevention
7
Morten Laufer
Founder
A bad hire costs one to three annual salaries (Kienbaum); in medium-sized businesses, the total costs are underestimated by up to 40%. More expensive than a visible bad hire is a silent one: they do not resign, only fulfil the role to 60%, and therefore never trigger a correction. Nova Search is a founder-led tech recruitment consultancy with a two-stage screening process and a 90-day guarantee — the risk of replacement lies with the consultant.
Bad hires cost one to three times an annual salary; the indirect costs are usually higher than the direct ones.
The silent bad hire does not appear in any statistics, but reduces productivity in the engineering team for months.
Time pressure is the strongest driver of bad hires: from the fourth month onwards, availability often wins over genuine professional fit.
Nova Search shares the risk of a bad hire: 90-day guarantee, two-stage screening, shortlist in 5 working days.
AI This article was created with the help of AI.
What a bad hire in IT really costs
When a newly hired tech professional leaves a company after just a few months, the financial damage is almost always drastically underestimated in practice. Medium-sized companies often only calculate obvious expenses like job postings or the salary paid, significantly underestimating the true total cost of an unfilled or poorly filled position. The HR consultancy Kienbaum estimates that the cost of a bad hire, especially for specialists and managers, can add up to 1.5 to 3 times the annual salary when lost productivity and re-hiring are factored in. According to CareerBuilder, a bad hiring decision can cost a company in Germany more than €50,000. Crucially, the real cost drivers are the indirect costs due to lost productivity, extra workload on the team, and internal management effort, not the directly visible expenses.
Particularly in software engineering and IT infrastructure, bad hires weigh heavily: in addition to direct costs, massive opportunity costs arise from blocked senior capacities and delayed product releases. The following overview shows which cost blocks accumulate when a company parts ways with a senior backend engineering position after just a few months.
Cost category | Included cost factors | Weight in total damage |
|---|---|---|
Direct costs | Recruiting effort and employer branding, internal working hours of HR and hiring department, onboarding costs, as well as recruiting a replacement | Easy to measure; the cost-per-hire is effectively incurred twice in the event of a bad hire |
Indirect costs | Onboarding effort for mentoring and code reviews by senior colleagues, administrative management effort for the team lead | Usually higher than the direct costs |
Follow-on & vacancy costs | Project delays, renewed search phase, loss of productivity in the team until the position is refilled | Grows with each month it takes to detect and correct |
Total damage | Sum of all measurable direct and indirect burdens | One to three times the gross annual salary of the position |
Damage on the scale of an entire annual salary or more shows that recruitment errors are not just an administrative nuisance, but directly threaten the operational budget and strategic roadmap of a tech team.
The silent bad hire: the case that doesn't appear in any statistics
In HR statistics, usually only the loud bad hire appears: an employment relationship is terminated during the six-month probationary period, the desk is cleared, and the recruiting process starts over. This process is costly, but it is visible, limited in time, and forces an immediate correction. However, the far more dangerous scenario in the IT sector is the silent bad hire.
In a silent bad hire, the hired person remains with the company. In everyday work, they might perform at 50 to 60 percent of the expected level, deliver tickets slowly, or produce architectural debt. In an agile software team, this performance deficit often goes formally unnoticed for months because the existing team instinctively compensates for the gaps: senior engineers take on complex refactoring, pull requests are corrected in time-consuming loops, and deadlines are saved with overtime. The result often only becomes apparent after 12 to 18 months, when frustrated high performers resign.
Dimension | Loud bad hire | Silent bad hire |
|---|---|---|
Course & duration | Termination during probationary period (months 1 to 6) | Remaining in the team for 12 to 24 months |
Visibility | Immediately measurable through termination and vacancy | Diffuse: falling velocity, increasing ticket cycle times |
Impact on the team | Short-term extra work until replacement is hired | Ongoing overload and latent frustration among high performers |
Primary cost driver | Repeated search and onboarding costs | Creeping productivity loss and chain turnover |
To uncover a silent bad hire within the first quarter, superficial probationary talks are not enough. What is required are clear, measurable 30-60-90-day goals, structured code contributions, and open peer feedback from the engineering team before the probationary period expires.
Where bad hires happen: five points in the process
Contrary to popular belief, bad hires almost never happen in the actual interview, but rather during the preparation stage. Anyone who does not precisely define the requirement profile and tech stack reality before starting the search will end up checking the wrong things with great thoroughness in the interviews. In addition, the time factor plays a crucial role: according to StepStone, the average vacancy time for professionals in Germany is around 180 days. In the specialised IT sector, the vacancy duration is often 7.7 months, while the pure time-to-hire from initial contact is around 4.5 months. From the fourth month of an unfilled position, the decision-making logic of many hiring managers shifts: the criterion of 'quickly available' suddenly trumps the criterion of 'technically suitable'.
Process step | Typical source of error & symptom | Effective countermeasure |
|---|---|---|
1. Role briefing | Wish-list profiles without prioritization of must-haves and nice-to-haves | 60-minute technical calibration call before starting the search |
2. Tech stack reality | Discrepancy between job description and real legacy or cloud architecture | Honest realistic job previews on frameworks, tools, and technical debt |
3. Screening depth | CV keyword matching without testing actual technical depth | Two-stage screening: coding/architecture check separated from soft skills |
4. Interview structure | Unstructured interviews based on sympathy and subjective gut feeling | Structured interviews where all applicants receive the same core questions in the same order, allowing for a fair and objective comparability of answers |
5. Decision pressure | Compromise hiring out of fear of further months of vacancy | Fixed quality standards and guaranteed shortlist speed |
Systematically shortening the time-to-shortlist significantly reduces the risk of bad hiring decisions: decisions are made based on suitability again, rather than staffing desperation.
Shifting risk instead of bearing it: what a process must deliver
To reliably rule out bad hiring decisions in tech recruiting, companies must treat technical suitability and cultural fit as two independent dimensions. A resilient hiring process therefore begins with a thorough 60-minute briefing to accurately map the tech stack, architecture, and team dynamics. This is followed by a two-stage screening: in the first step, technical depth is methodically validated; in the second step, experienced consultants check whether working methods and communication patterns fit the organization during a culture interview.
Speed protects against quality loss: if a tailored shortlist is presented after a maximum of 5 business days and both sides exchange structured feedback within 48 hours, the process remains highly committed and prevents top candidates from dropping out prematurely. A specialised tech recruitment consultancy ensures that support is provided by senior consultants or founders, without mandates being handed over to junior recruiters.
For the permanent employment of tech professionals and executives, Nova Search relies on a contractually anchored 90-day guarantee: should a placed professional leave the company within the first three months, a replacement will be recruited free of charge. Such a guarantee naturally does not prevent every individual human case, but it redistributes the economic risk fairly. The collaboration with PPI AG proves that a structured direct approach and sound screening have a lasting effect: over four years, the process achieved a 100 percent retention rate across more than ten successfully filled key positions.
Would you like to rule out bad hires in your engineering and IT teams from the start? Arrange a non-binding initial consultation with Nova Search and receive your first vetted profiles for your open vacancies within 5 business days.
Read more
Sources
FAQ
What is the cost of a bad hire in IT?
A bad hire costs, on average, one to three times the annual salary of the respective position. According to CareerBuilder, a bad hiring decision can cost a company in Germany more than 50,000 euros. Direct costs include recruiting and salary, while productivity losses make up the largest indirect item.
What is a silent bad hire?
A silent bad hire remains with the company despite only partially fulfilling the technical requirements of the role. In IT, this is common as technical underperformance is often compensated for by the team for a long time - for example, through longer code reviews. Since it does not trigger an immediate dismissal, it does not appear in any direct cost statistics.
Why do bad hires occur in IT recruiting?
Most mistakes happen right at the briefing stage and not during the interview. If the requirements for the tech stack and the team culture are not precisely clarified beforehand, the wrong things are tested during the selection process. A two-stage screening that assesses technical and cultural fit separately prevents this.
How does the vacancy duration affect the quality of the hire?
The average IT vacancy duration is 7.7 months. From the fourth month onwards, enormous time pressure often builds up, leading to quickly available candidates being preferred over those who are truly suitable. A short time-to-shortlist protects you from having to make compromises out of pure necessity.
Does a probationary period protect against the costs of a bad hiring decision?
No, a separation during the probationary period limits long-term damage, but still incurs high costs. The salary already paid, the recruiting effort, and the onboarding time invested by the team are lost, and the search process has to start all over again.
How does a recruitment consultancy minimise the risk of a bad hire?
Specialist providers minimise the risk through deep technical assessments and cultural fit interviews before candidates are presented. Furthermore, providers like Nova Search offer contractual protection: if a placed specialist leaves the company within 90 days, a replacement is provided free of charge.
