This isn’t about hiring an adequate person. This is about hiring the best person available, watching them sail through the process, with everyone in the room nodding along by the second interview, and still ending up with a hire that doesn’t work out.

That version of a bad hire is harder to talk about. There’s usually no obvious failure to point to, and no single bad call you can replay and wince at. The person wasn’t wrong, the process wasn't broken, and it felt like nobody settled for less than excellent. But something subtler happened, and it usually comes down to the same thing: the hire was right for a different environment than the one they walked into.

This is the mismatch problem. It’s more common than most companies realise and harder to spot in advance. It’s also very expensive to unwind once someone is already sitting at the desk.

When profile isn’t the problem

A Series A startup hired a product manager from Google. On paper she was the easiest yes the company had ever made. Exceptional by any conventional measure, she was sharp in every interview, bright, personable, and she was genuinely aligned with the mission. She’d been doing real, impactful work at one of the most demanding product organisations in the world, the kind of place every startup dreams of becoming one day.

She joined, but within a few months it was clear something wasn’t landing. The pace of a startup was different from anything she’d experienced, in a way that’s hard to describe to anyone who hasn’t lived both sides of it. The scrappiness and context-switching, the expectation to operate across US and UK product work in the same week, sometimes inside the same afternoon.

It’s a low-resource environment where you have to make things work without the infrastructure that had always just been there for her at Google, where resource is just water you swim in. At a ten-person startup, resource is the problem you’re solving and the thing you’re fighting for every day. That shift is genuinely significant, and it doesn’t show up in an interview.

She wasn’t wrong for the role, she was wrong for the environment. And those are different problems with different causes.

Exceptional is contextual

This is the thing that gets missed most often in hiring. Exceptional isn’t a fixed standard, it’s contextual. What makes someone outstanding at a large, well-resourced company can be almost irrelevant at an early-stage startup, and vice versa.

A founding engineer who thrives on ambiguity, builds without a clear brief, and takes ownership instinctively might struggle in an environment with mature processes and defined scope. A senior engineer from a larger organisation who executes brilliantly within structure might flounder when the structure doesn’t exist yet.

Neither of those people is less talented, they’re just calibrated to different environments. The mistake is not knowing which environment you actually have before you start looking.

This sounds obvious stated plainly, but in practice, it’s surprisingly easy to overlook. Hiring benchmarks tend to form around previous hires, familiar profiles or what a particular pedigree suggests about quality. Google, Meta, Stripe, top university, strong trajectory. These are reasonable proxies, but they’re proxies for performance in those environments. What they are not is guarantees of performance in yours.

Hiring someone exceptional from Google and expecting them to thrive at a ten-person startup is a bit like hiring a Formula One driver and expecting them to do their best in a muddy field instead of on a track. The reflexes are still going to be there and their instincts are still going to be razor sharp, but none of it transfers cleanly to a completely different terrain with completely different conditions. And no amount of talent closes that gap if nobody thought to ask which environment they were actually built for.

Where the mismatch comes from

Most hiring mismatches happen because nobody answered the harder questions first.

What does ownership mean in this team, at this stage? How much direction will this person get, and how much will they need to create for themselves? What does pace look like here? What’s the resource environment? What behaviours will be rewarded, and which ones, however impressive in another context, won't translate?

These are the questions that define what exceptional means for a specific role in a specific environment. When they’re answered clearly before the search begins, the profile becomes genuinely specific. Interviewers know what they’re looking for. Feedback has somewhere to land. The debrief produces a real decision rather than a collection of impressions.

When they’re not, the process tends to default to surface signals. “Strong communicator.” “Good experience.” “Impressive background.” “Positive attitude.” All of which might be true, but none of which tells you whether this person will thrive in the ecosystem you’re cultivating.

The signals that tend to get missed

There are patterns that show up in hiring processes when this kind of mismatch is about to happen.

The feedback in the debrief is positive but vague. People use words like "solid" and "capable" and "would probably do well here," but nobody says specifically what this person will bring or how the team gets better because of them. The hire gets made because nobody is against it, not because everyone is genuinely for it.

Or the process tests for the wrong things. Technical depth is assessed rigorously, but cultural fit almost not at all, or the reverse. There are strong opinions in the room about pedigree, but much less clarity about what operating in this environment actually requires.

Or the role itself hasn’t been properly defined. What does success look like in six months? What problems does this person need to solve? What are they walking into? When those questions don’t have clear answers before interviews start, every interviewer ends up evaluating something slightly different, and the feedback becomes almost impossible to reconcile.

Spotting it earlier than the debrief

Most founders who’ve been through this kind of hire say that looking back, the signals were there. Not glaring red flags necessarily, but a slight hesitation in the debrief that got rationalised and smoothed over. A question about fit that got answered with optimism instead of evidence, or a sense that the profile was so strong that surely the environment questions could be sorted out later.

They usually can’t. The environment is the job, and if it doesn’t match what the person is calibrated for, the gap tends to surface quickly, even when everything else about the hire looked right.

The fix here isn’t more rounds, but asking a more specific question before the search starts: not just how good is this person, but what does good actually look like inside this particular team, at this particular stage, doing this particular job. Build the debrief around answering that question directly, and the vague "solid, would probably do well here" feedback stops being acceptable, because it stops answering what was actually asked.

Get that right, and you’re no longer sat hoping that someone exceptional in general turns out to be exceptional here. You’re checking, specifically and early, whether they will be.