How Much Does a Bad Hire Actually Cost in the IT Industry?
In the race for scarce IT talent, the pressure on HR teams, CTOs, and Hiring Managers is immense.
Projects are waiting, clients are getting nervous, and the roadmap cannot stand still. In such an environment, it is easy to fall into the trap and make a decision driven by the logic:
"Let's just fill the position, and we'll handle the details later."
The problem is that the consequences of such a decision are often not visible immediately.
A new developer, DevOps, or QA engineer might seem perfectly fine during the first few weeks, only for the real trouble to surface once daily collaboration with the team begins.
And that is exactly when companies realise that the cost of a bad hire has very little to do with just that person's salary.
A Bad Hire Is Not Just a Financial Problem
What I have noticed through practice is that a bad hiring decision rarely remains a problem of budget and money spent alone.
Much more frequently, it becomes a risk for the existing team.
Some costs are visible and can be calculated relatively easily.
Others are far more dangerous because they aren't obvious right away, yet they directly impact productivity, atmosphere, and employee retention.
And there is no major difference whether a person is a poor technical or cultural fit - both situations can have an equally destructive impact on the company.
What Happens When Technical Quality Isn't Up to Par
When a new team member fails to deliver code of the expected quality, someone else has to fix the mistakes.
In practice, this almost always falls on seniors and people who have known the system for a long time.
Instead of developing new features and focusing on what adds value to the product, they become "firefighters."
The result is highly predictable:
- Frustration among key people
- Team overload and burnout
- Slowing down development
- Sprinting delays
- Additional pressure on the rest of the organisation
I am aware that the onboarding process can sometimes fail, but that is not what I am talking about here.
I am talking about situations where the problem is actually the candidate's quality and the level of knowledge they brought into the team.
A single link that is constantly lagging can slow down the entire sprint and, consequently, the delivery to the client.
At that point, the problem is no longer just internal - it enters the zone of the company's reputation.
The Biggest Risk: Losing Your Best People
This is the part that companies most frequently underestimate.
High-quality employees have a fairly high tolerance threshold.
They understand that everyone needs time to adjust, ask questions, and make rookie mistakes in a new environment.
However, when the situation does not improve for months - say, four or five months - you enter a serious risk zone.
That is when previously loyal and satisfied employees start to think:
"Do I want to keep working in an environment where I am constantly fixing someone else's work?"
At that exact moment, quiet market research often begins.
Someone checks job boards, someone replies to a recruiter's message, and someone very quickly receives an offer they no longer have a reason to refuse.
That is why I often say: don't let one bad apple spoil ten kilograms of good ones.
Costs That Everyone Sees
Of course, there are direct financial costs:
- Gross salary with taxes and contributions
- Sign-on bonuses
- Benefits
- Work equipment
- Licences and tools
- Education budgets
- Potential severance pay
There are also the costs of the hiring process itself: job ads, LinkedIn licenses, internal HR time, hours spent on technical interviews, and potential collaboration with an external IT recruitment agency.
But this is only the visible part of the bill.
Costs That Almost No One Calculates
A much bigger problem is the time lost by the people who are already the most valuable in the organisation.
Leads and seniors spend hours on additional code reviews, mentoring, explaining basic concepts, and fixing implementations that should never have passed in the first place.
This is time that was not invested in architecture, system optimisation, developing new features, or working with clients.
And there is another cost that is almost impossible to calculate: the team's energy.
When people spend months draining their energy on resolving internal problems and conflicts, much less of it remains for innovation, growth, and product development.
How One Wrong Person Can Shift Team Culture
I had an experience with a company where candidates didn't want to leave for years.
In interviews, they described it as a great place to work, with a healthy culture and excellent interpersonal relationships.
Then the company grew, and changes began.
First, an HR manager was introduced who did not understand the existing team culture.
People didn't have an issue with introducing processes as such, but with the way the changes were implemented - abruptly and without regard for existing relationships.
Next, a larger number of Project Managers who were not technically sound were hired, making communication between teams significantly more complicated.
Within a relatively short period, most of the people who had spent years building that culture left the company.
This example was an important lesson for me that even a non-technical person can seriously disrupt team dynamics if they do not fit into the way of working and the values of the organisation.
The same applies to technical teams.
If a person enters a team with a strong need to push other people's boundaries, has a more aggressive communication style, or struggles to accept feedback, the team's energy is quickly spent on conflict resolution instead of product development.
That is why it is always worth asking: Is this person bringing long-term growth to the company, or are they just a short-term plug for a hole in the team?
How to Reduce the Risk of a Bad Hire
Mistakes happen to even the best of companies, but a quality process can significantly reduce the risk.
In my experience, the most important thing is to combine four types of assessment:
- Technical fit
- Product fit
- Team fit
- Candidate expectations