Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / How One Bad Hire Cost 300k in Hidden Expenses
Transcript
- Lucas: A few months ago I was talking to the VP of Engineering at a mid-sized SaaS company, about 400 employees, and she told me about a hire that cost them roughly three hundred thousand dollars over two years. Luna: Three hundred thousand? Was this an executive role or something? Lucas: No, that's the thing. It was a senior software engineer. Base salary around one-fifty. But when she walked through the full cost — onboarding drag, manager hours, lost productivity, rework, team churn, severance — the real number was double the salary. And she said most of it was completely invisible on a P&L. Luna: So the salary is just the tip of the iceberg. What went wrong with this particular hire? Lucas: The guy had a great resume. Ten years at a well-known company, solid GitHub profile, strong technical interview. But within three months, it became clear he struggled with cross-team collaboration. He'd build things that worked in isolation but didn't integrate well. He was resistant to code reviews. And because he was senior, his output had outsized influence. Luna: So the hiring process missed the collaboration filter. How long did it take before they realized it wasn't working? Lucas: About six months. But by then, he had already shipped two features that had to be partially rewritten. The team had lost a junior engineer who was frustrated with the dynamic. And the engineering manager was spending maybe 40 percent of her time on performance management and rework coordination instead of strategic work. Luna: That manager time is a huge hidden cost. Did they actually calculate it? Lucas: They did after the fact. They tracked everything: the manager's hours, the onboarding time for the hiring committee, the productivity dip for the team during the ramp-up, the cost of the rework, and then the severance and legal costs when they eventually let him go. It came to about $290,000. That's not counting the opportunity cost of features they didn't ship because they were fixing his code. Luna: And that's just one hire. If a company makes even two or three of those a year, it's a million-dollar problem. Lucas: Exactly. And the VP told me the worst part was that they had the data to catch it earlier. They had a structured interview process, but they didn't use a weighted scorecard. The technical round carried the most weight, but the behavioral and collaboration rounds were almost a rubber stamp. Luna: So the process was in place, but the weighting was off. That's a common story. What did they change afterwards? Lucas: They rebuilt their scorecard with weights that reflected what actually predicted success in their environment. Technical skill got 40 percent. Collaboration and communication got 30 percent. Learning agility and adaptability got 20 percent. And culture add — not fit — got 10 percent. They also introduced a work sample exercise where candidates had to pair-program with a team member on a real-ish problem. Luna: And has it made a difference? Lucas: She said in the two years since, they've had zero performance terminations for senior engineering hires. Attrition in the engineering org dropped by about 25 percent. They estimate they've saved north of half a million dollars just in avoided bad hires and reduced turnover. Luna: That's a huge return on a fairly simple process change. And it's not just about the money — the team morale, the velocity, the quality of work. Lucas: Right. The hidden costs of a bad hire are real, but they're also avoidable. And we talk about this kind of thing on the show because we believe better hiring decisions lead to better companies. If these conversations have moved your work forward in some small way, that's our goal. Luna: We deliberately don't run ads on these episodes. It keeps the focus on the content. Lucas: And if you want to support that choice, the link is buy me a coffee dot com slash fexingo. No pressure, truly. Luna: Yeah. Back to the math — one of the most useful frameworks I've seen for estimating bad-hire cost comes from a Harvard Business Review piece a few years back. Lucas: Oh, the one that breaks it into direct and indirect costs? With a multiplier? Luna: Yes. They suggest taking the employee's annual salary and multiplying by somewhere between 1.5 and 3, depending on the role's complexity and interdependence. For a senior individual contributor like that engineer, they'd use 2 to 2.5. That gets you close to the three hundred thousand figure. Lucas: And that multiplier covers recruitment fees, onboarding, training, productivity loss during ramp-up, mistakes and rework, management time, and the impact on team morale and turnover. The HBR piece also has a nice worksheet. Luna: I've used it with a couple of clients. It forces you to be specific. Like, how many hours does your hiring manager spend per new hire? What's the average time to full productivity? What's the error rate in the first six months? Most companies don't track that. Lucas: No, they don't. And that's why bad hires are so insidious. The costs are spread across departments and time periods. No single person sees the full picture. The recruiter sees the time to fill. The manager sees the performance issues. Finance sees the severance. But nobody adds it up. Luna: So what's the one thing a company could do tomorrow to start tracking this? Lucas: Start a simple spreadsheet. For every hire, track: recruiter hours, interview panel hours, onboarding time, manager coaching hours in the first six months, and any rework or bug fixes attributed to that person. After a year, you'll have a baseline. Then you can start to see patterns. Luna: And those patterns might tell you that your interview process is missing something, or that you're hiring too fast, or that you're not setting clear expectations. Lucas: Exactly. The VP I mentioned said the biggest insight from their post-mortem wasn't about the hire himself — it was about their process. They were so focused on technical signals that they ignored everything else. And they paid for it. Luna: There's a parallel here to something I read about the US Army's hiring for special forces. They use a multi-day assessment that includes cognitive tests, physical tests, and crucially, peer evaluations. Candidates who are technically brilliant but can't work with others get weeded out. Lucas: Right. And peer evaluations are powerful because teammates see things interviews never catch. A candidate can be charming for an hour, but after three days in the field, their patterns emerge. Most companies can't do a three-day assessment, but they can do a work sample or a team interview. Luna: Or even a paid trial project. Some startups do a two-week contract before making a full-time offer. It's expensive but it's cheaper than a three-hundred-thousand-dollar mistake. Lucas: Absolutely. And I'll add one more thing: the cost of a bad hire isn't just financial. It's the cultural drag. The team that works around a low-performing or difficult colleague starts to normalize dysfunction. They either leave or they lower their standards. That's hard to quantify, but it's real. Luna: So the real takeaway is that the cost of a bad hire is almost always higher than you think, but the cost of fixing your hiring process is lower than you fear. Lucas: That's a good way to put it. And if you're a leader listening, I'd challenge you to do the math on your last bad hire. Be honest about the time, the rework, the team impact. The number might surprise you. And it might motivate a change. Luna: I think that's a solid note to end on. Thanks, Lucas. Lucas: Thanks, Luna. See you next time.