Why your last hire didn't work out (and it probably wasn't the candidate)

Download "The Real Cost of a Bad Hire"

DOWNLOAD

Here's an uncomfortable pattern I've watched play out for years: a hire doesn't work. Six months in, the role is open again. Everyone in the post-mortem nods solemnly and lands on the same conclusion.

"Wrong person."

"Just not the right fit."

"They interviewed better than they performed."

It's a tidy story. It's also almost always wrong.

When a hire fails, the candidate is the easiest thing to blame because the candidate is the last variable in a long chain. But by the time someone is sitting at a desk underperforming, eight or nine decisions have already been made — about the role, the bar, the process, the timeline, the offer — and most of those decisions were made by the people now blaming the candidate.

You didn't hire the wrong person. You ran the wrong process. Here are the five places it usually breaks.

1. The intake was fuzzy

Most failed hires start at the intake meeting. The hiring manager says they need a "senior marketer" or a "strong ops person" or "someone who can really own this." Recruiting nods, writes it down, and starts sourcing.

Two months later, candidates are being rejected for reasons no one mentioned at intake. We need someone more strategic. We need someone more hands-on. They don't have enough enterprise experience. They have too much enterprise experience.

What happened: the hiring manager didn't actually know what they wanted, and the intake didn't force them to figure it out. So the criteria emerged in real time, candidate by candidate, often contradicting itself. The "right" hire eventually walks in — but only after eliminating five people who would have been just as good, and after burning enough calendar time that the urgency forced a rushed decision on whoever was left.

A real intake is a fight. It pins the hiring manager down on the three things that genuinely matter, the things that look like must-haves but aren't, and the trade-offs they're willing to accept. If your intake meeting is pleasant and quick, it didn't do its job.

2. The must-have list is a wishlist

Pull up the last three job descriptions your team posted. Count the requirements. If it's more than seven, you're not hiring — you're shopping for a unicorn.

Bloated must-have lists are the second most common upstream failure, and they cause two distinct problems. First, they shrink the candidate pool to the point where you're choosing from three people instead of thirty, which means you're choosing from a worse pool, period. Second, they teach your interview panel to optimize for box-checking instead of judgment. The panel grades against the list. The list is wrong. The hire reflects the list.

The pattern I see: a role lists ten requirements, the team hires the only candidate who hits all ten, and that candidate fails because the actual job required two of those things deeply and the other eight not at all. Meanwhile, the candidate who would have been excellent — strong on the two that mattered, weak on a few that didn't — was filtered out in week one.

The fix isn't subtle. Before you post a role, force a conversation about what the person needs to do in the first ninety days. Then back out the two or three capabilities that actually predict success. Everything else is preference, and preference belongs in a "nice to have" column where it can't kill a good candidate.

3. The process lost the right person at week three

Good candidates are not patiently waiting. They are talking to two or three other companies, they have a current job, and they have a finite tolerance for being passed around.

Here's what kills them: the gap between round two and round three. The interview that gets rescheduled twice. The reference check that takes nine days because the hiring manager is at a conference. The "we'll get back to you next week" that becomes next week, and then the week after.

Every one of those gaps is the candidate sitting in their kitchen at night, talking to their partner about the other offer they have. By the time you finally circle back, they've mentally moved on, even if they don't tell you yet. They'll either decline politely or accept and quietly keep looking. Either way, you didn't lose them on the merits — you lost them on calendar friction.

A process that respects candidates is fast, choreographed, and communicated. Five business days from first conversation to decision is a strong target. Ten is acceptable. Three weeks means the candidate you actually wanted has signed somewhere else, and you're now choosing from the people who had the time to wait — which is its own kind of signal you should pay attention to.

4. The interview measured the wrong things

Most interview loops are a collection of conversations that each panelist designed independently, asking whatever they happen to find interesting that day. One person digs into culture fit. Another runs through the resume chronologically. A third asks brain teasers because someone did that to them once. The debrief is a vibes-based negotiation between five people who each measured something different.

This is not interviewing. This is taking turns.

A real loop has a defined rubric. Each interviewer is assigned one or two specific competencies and given a structured exercise to evaluate them. The debrief compares notes against the rubric, not against gut feelings. When this is done well, hiring decisions become legible — you can point to the evidence and say this is why we said yes or this is why we passed — and the rate at which hires actually perform the way you expected goes up dramatically.

When this is done poorly, you hire the candidate who interviewed best. Interviewing well and doing the job well are correlated, but they are not the same skill. The gap between them is where bad hires live.

5. The offer went out too slow, or too low, or both

You picked the candidate. Everyone is excited. And then it takes four days to get the offer letter out the door because legal needs to review the equity language, the comp band needs an exception, and the hiring manager is in back-to-back meetings.

In those four days, the candidate's enthusiasm flattens. Doubt creeps in. The other company they were talking to moves faster. By the time your offer arrives, it's competing not with their current job — which they were ready to leave — but with a fresh, energetic offer from a place that acted like they wanted them.

And even if the offer arrives quickly, it sometimes arrives wrong. Hiring managers fight hard for a candidate, then anchor the offer to the bottom of the band because someone in finance asked them to be conservative. Candidates notice. They don't always negotiate — many of them just sign and start looking again within a year, because the offer told them exactly how much you valued the role.

A good offer is fast, generous within reason, and clearly communicated by someone the candidate has built a relationship with. Not a PDF in their inbox at 6 PM on a Friday.

So when a hire fails, what actually happened?

Almost always, one of those five things. Sometimes two or three of them stacked.

The candidate showing up on day one is the result of every decision made before they sat down. Fuzzy intake produces a misaligned hire. A bloated must-have list produces a narrow, weak pool. A slow process produces the candidate who was available, not the one who was best. A poorly designed loop produces a hire optimized for performance under interrogation. A late or stingy offer produces a hire who is already half out the door.

None of those are the candidate's fault.

This is also why "hire slow, fire fast" is bad advice when applied without thinking. Slow doesn't mean careful — slow usually means uncoordinated. The teams with the best hiring outcomes are not the ones with the most thorough processes. They're the ones with the most disciplined ones: clear intake, tight criteria, fast cycles, structured loops, prompt offers.

The next time a hire doesn't pan out, resist the easy answer. Don't ask was that the wrong person? Ask what did our process do to that person, and what would we need to change to not do it again?

The answer is almost never on the candidate's resume. It's in your calendar.

Most hiring leaders dramatically underestimate what a failed hire actually costs — not just in salary, but in lost productivity, team morale, ramp time for the replacement, and the opportunity cost of the work that didn't get done. We put together a breakdown of the real numbers, including how to model it for your own team.

Download "The Real Cost of a Bad Hire" →

DOWNLOAD