top of page

Why Hiring for Fit Beats Hiring for Individual Excellence

Sep 26
6 min read
Mismatched geometric shapes fitting together, representing hiring for fit and complementary team skills over uniform excellence

Every hiring process I've sat in claims to be looking for the best candidate. Ask "best against what" and you mostly get a blank look, because nobody's actually defined it. They're ranking people against each other on a shortlist, not against the team those people are meant to join.


I think about it more like finding product-market fit than finding the smartest person available. You can build something brilliant and still watch it die because nobody wanted it. Hire someone brilliant who doesn't fit the room they're walking into and you get the same outcome, just slower, and with a much bigger invoice.


There are two decent reasons to hire someone. Either there's a gap in the team and this person closes it, or someone's good enough that you make room for them even though you didn't know you needed to. Anything past those two is filling a seat because the req's been open too long.


Skill depth gets someone through the interview and through the first sprint. It tells you nothing about what happens once they're sat next to the six people already on the team, on a bad Tuesday, when a deadline's slipping. Most processes never test for that bit.

This is where the odd, specific stuff earns a look in. The strongest hire for a team right now might not be the strongest engineer on the shortlist at all. Could be someone who's spent years buried in fraud detection models for a completely different industry. Could be someone who's actually shipped a platform migration rather than talked through one in a system design round. None of that reads as "better" on a scorecard, because a scorecard's built to rank, and this doesn't rank. It sits sideways to everything else on the team.


Most hiring is built to find the strongest individual on paper. Very little of it asks whether the group gets stronger with this person dropped into it. Answer that second question honestly and you often land on a different name to the one who topped the technical interview. That gap is where the commoditisation creeps in. Best person for the best price, priced like a spare part rather than assessed against the actual space you're trying to fill.


Google's Project Aristotle gets quoted constantly, usually backwards. It's the two year study of 180 internal teams that people assume proved composition is everything. What it actually found was psychological safety mattered more than raw talent, seniority, tenure or team size, full stop. How the team worked together beat who happened to be in the room. Awkward finding for anyone leaning too hard on "just get the mix of skills right and the team sorts itself out." Fit isn't only about which skills you slot in next to each other. It's whether the team can do anything useful with what you've handed it.


Team composition matters more for the type of diversity you're chasing than for diversity as a fact on its own. Anita Woolley's work at MIT found that groups doing tasks which benefit from a range of skills or expertise will underperform unless they're built with the cognitive diversity that task needs, even against groups made up of individually smarter people. Five people who all think about a problem the same way lose to five people who don't, whatever each of them scores on their own. The same body of research found a team's collective intelligence predicts its performance far better than the ability of its best individual member does. The academic way of confirming something most experienced managers already suspect but rarely say plainly in a hiring debrief.


Meredith Belbin found much the same thing decades earlier, running international management teams through business simulations at Henley Management College over nine years. What came out of it was that team success came down to behaviour rather than intellect. His nine team roles have stuck around because the pattern keeps repeating itself. Load a team with people who all want to challenge and drive and push, and you get infighting and nothing finished. Load it with people who all want to generate ideas, and you never run short of ideas, you just never build any of them.


McKinsey's Diversity Wins research found companies in the top quartile for gender diversity on their executive teams were 25% more likely to post above average profitability than the bottom quartile, and their 2023 follow up put the figure at a 39% increased chance of outperforming. A 2024 attempt to rerun McKinsey's own methodology against S&P 500 data couldn't find a statistically significant link at all. Take those numbers as directional evidence the case has legs, not as proof you staple to a board deck.


The cost of getting it wrong is easier to defend, because it's less about correlation and more about what actually happens after someone starts. Leadership IQ tracked over 20,000 new hires and found 46% fail within eighteen months. When they dug into why, attitude accounted for 89% of those failures against just 11% for a lack of technical skill. That's the fit argument showing up as an actual line in the accounts. Nobody's technical screen let them down. Their ability to sit inside the team they'd just joined did.


None of this is an argument for dropping the technical bar. Clear it, and the interesting conversation should start rather than stop.


Before you open a role, work out what the team's actually missing, properly, rather than defaulting to a job title. Not "we need a senior engineer" as a description, but an honest look at where the team's thin. Four people who all think in the same architectural patterns and nobody who's actually run distributed systems at real scale, say. Written like that, it's a completely different brief to a spec sheet, and it changes who you go looking for.


If co-location is genuinely the strategy, build the working rhythm into the decision up front rather than discovering the mismatch three months in. Someone who thrives remotely and struggles in a hub-first culture isn't a character flaw. It's a hiring decision that ignored something everyone already knew going in.


Swap "culture fit" for "culture add" if you're still running the old language internally. The shift asks what someone contributes rather than how smoothly they'll disappear into what already exists, which is the whole esoteric-skill argument above in one phrase. The EHRC has flagged cultural fit criteria as a potential source of unlawful discrimination in the UK when they're not tied to something defined and job-relevant. Culture add gives you a reason you can stand behind in a review. A gut feeling about fit doesn't.


Keep the individual bar and the team decision as two separate checks rather than letting one quietly stand in for the other. Amazon's Bar Raiser programme makes a good contrast here, even though it's not the model I'd copy wholesale. It's an outside interviewer with no stake in the team, whose whole job is confirming the candidate clears a general excellence threshold. Solid mechanism for what it's built to do. It was never built to ask whether this particular group, with its particular gaps, actually gets stronger with this particular person added to it. Run a version of both checks if the idea appeals to you. Just don't assume passing the first one answers the second.


And ask the question most hiring debriefs skip entirely: what happens to this team if we play it safe and hire the more obviously impressive generalist instead of the person who actually covers the gap. Almost nobody asks it out loud, because defending a strong CV in front of a panel takes no effort at all, and defending a case built on how someone's difference helps the team think differently takes real conviction, especially in front of people who've never had to make that call before.


Hiring for fit takes longer to argue for in the room. You're building a case for what someone adds to a system, not reading a ranked list back to people who already trust rankings. That's a harder sell, and it should be, because it's a bigger claim. But the system is what actually ships the work, not any single name on it. Get comfortable making that case, because the alternative is a roster full of genuinely brilliant people who've never once been asked to work as a team.

Comments


bottom of page