Avoiding bad hires in IT recruiting: costs and prevention
7
Morten Laufer
Founder
A bad IT hire costs up to three years' salary – and a silent bad hire within the team causes even more damage. Learn how to eliminate risks during the briefing stage and consistently avoid hiring mistakes with Nova Search, thanks to a 90-day guarantee and rapid shortlists.
Bad hires cost between one and 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 wrong decisions: from the fourth month onwards, availability often wins over genuine technical fit.
Nova Search reliably protects you from expensive recruiting mistakes through a two-stage screening process and a 90-day guarantee.
AI This article was created with the help of AI.
The true cost of a bad hire in IT
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 calculate only the obvious expenses, such as job advertisements or the salary paid, and significantly underestimate the actual total cost of an unfilled or badly filled position. The Kienbaum HR consultancy estimates that the cost of a bad hire can add up to 1.5 to 3 times the annual salary, especially in the case of specialists and managers, when loss of productivity and rehiring are taken into account. 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 of lost productivity, additional workload in the team and internal management effort, rather than the directly visible expenses.
In software engineering and IT infrastructure in particular, bad hires carry heavy consequences: in addition to direct costs, massive opportunity costs arise from blocked senior capacities and delayed product releases. The following overview shows the cost blocks that accumulate when a company parts ways with a senior position in backend engineering 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 specialist department, onboarding costs as well as the replacement recruitment of a successor | Easy to measure; the cost-per-hire is effectively doubled in the event of a bad hire |
Indirect costs | Onboarding effort for mentoring and code reviews by senior colleagues, administrative management effort of the team lead | Usually higher than the direct costs |
Consequential & vacancy costs | Project delays, renewed search phase, loss of productivity in the team until replacement is found | Grows with each month that the identification and correction takes |
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 year's salary or more shows that recruitment errors are not merely an administrative nuisance, but immediately threaten the operational budget and strategic roadmap of a tech team.
The silent bad hire: the case that is absent from any statistics
HR statistics usually only show the loud bad hire: an employment relationship is terminated during the six-month probationary period, the desk is cleared and the recruitment process starts all over again. This scenario is costly, but it is visible, limited in time and forces an immediate correction. The far more dangerous variant in the IT sector, however, is the silent bad hire.
In a silent bad hire, the hired person remains with the company. In day-to-day operations, they might deliver only 50 to 60 per cent of the expected performance, 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 refactorings, pull requests are corrected in time-consuming loops and deadlines are rescued 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 |
|---|---|---|
Timeline & duration | Resignation/termination during probationary period (month 1 to 6) | Remaining in the team for 12 to 24 months |
Visibility | Immediately measurable through termination and vacancy | Diffuse: falling velocity, increasing ticket turnaround times |
Impact on the team | Short-term extra work until replacement is found | Long-term overload and latent frustration among high performers |
Primary cost driver | Repeated search and onboarding costs | Creeping loss of productivity and chain fluctuation |
To uncover a silent bad hire as early as the first quarter, superficial probationary period reviews are not enough. What is required are clear, measurable 30-60-90-day targets, structured code contributions and open peer feedback from the engineering team before the probationary period expires.
Where bad hires occur: five stages in the process
Contrary to popular belief, bad hires almost never occur in the actual job interview itself, but rather during the preparation. Anyone who does not precisely define the requirement profile and the tech stack reality before starting the search will test the wrong things with great thoroughness in the interviews. The time factor also plays a decisive role: according to StepStone, the average vacancy time for skilled workers in Germany is around 180 days. In the specialised IT sector, the vacancy period 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 'quickly available' suddenly beats the criterion 'professionally suitable'.
Process step | Typical error source & symptom | Effective countermeasure |
|---|---|---|
1. Role briefing | Wish list profiles without prioritisation of must-haves and nice-to-haves | 60-minute technical calibration meeting 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 personal liking and subjective gut feeling | Structured interviews in which all candidates receive the same core questions in the same order, allowing for a fair and objective comparability of responses |
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 tangibly reduces the risk of making bad decisions: decisions are once again made on the basis of suitability, not out of staffing emergencies.
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 distinct dimensions. A robust hiring process therefore begins with an in-depth, 60-minute briefing to accurately map the tech stack, architecture and team dynamics. This is followed by a two-stage screening process: in the first step, technical depth is methodically validated; in the second step, experienced consultants conduct a culture interview to check whether working methods and communication patterns fit the organisation.
Speed protects against loss of quality: when a custom-fit shortlist is presented after a maximum of 5 working days and both sides exchange structured feedback within 48 hours, the process remains 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 assignments being passed on to junior recruiters.
For the permanent employment of tech professionals and leaders, Nova Search relies on a contractually anchored 90-day guarantee: should a placed specialist leave the company within the first three months, a replacement will be found free of charge. Naturally, such a guarantee does not prevent every individual human case, but it redistributes the economic risk fairly. The fact that a structured direct approach and sound screening have a lasting effect is proven, among other things, by the collaboration with PPI AG: over four years, the process achieved a 100 per cent retention rate with more than ten successfully filled key positions.
Would you like to rule out bad hires in your engineering and IT teams right from the start? Arrange a non-binding initial consultation with Nova Search and receive your first vetted profiles for your open vacancies in 5 working days.
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.
