A bad hire is like a bad haircut. Everyone notices, it takes months to grow out, and you are not going back to that barber. ✂️ In IT, though, the cost is a lot more than a few awkward weeks.
What a bad IT hire really costs
- The fee and salary already paid for someone who did not deliver
- Lost delivery time: missed sprints, delayed releases and deadlines that slide
- Rework: code, configuration or data someone else has to fix
- Team impact: your best people carry the load and start looking around
- Management time: performance conversations, HR involvement and exits
- Rehiring: another search, another fee, another notice period
A simple rule of thumb many leaders use: a failed senior hire in the first six months can cost well over half a year’s salary once delivery delays are included.
Why bad hires happen in IT
- Keyword screening. The CV says Kubernetes. The person has heard of Kubernetes.
- Rushed processes. Pressure to fill leads to skipped steps.
- Unclear roles. If you cannot define success, you cannot hire for it.
- Culture and motivation ignored. Skills get people hired. Fit keeps them.
How to avoid it
- Define the first 90 days before you advertise
- Use structured technical assessment, not just a chat
- Check references properly, with specific questions about delivery
- Ask about motivation: why this role, why now, why leave?
- Insist on a meaningful warranty. Many agencies offer two or three months. We offer six months on permanent placements, because problems rarely show up in week three.
👉 Want vetted candidates rather than the first three profiles a search engine finds? Share your requirement, or see how our permanent placement process works.
Employer
Employer
