What “Not a Culture Fit” Usually Means

The hardest calls I make are the ones where I have to explain a rejection I don’t understand myself.

A candidate who was technically excellent. A client who says they just weren’t a culture fit. Nothing after that.

I’ve been given that reason for twenty years. It’s the one I can explain least. So here’s what it usually means.

The Feedback I Get Most and Can Explain Least

There’s an asymmetry in hiring that I don’t think most managers ever see.

When you decide against a candidate and tell your recruiter it was a culture fit thing, that’s the end of it for you. You move to the next name on the list, and the sentence you used to close the file never gets examined again.

The candidate doesn’t hear it. Almost nobody says that phrase to someone’s face, and I understand why. It sounds like a judgement about the person rather than the match, and it’s hard to deliver without causing hurt.

Which leaves me. I’m the only one in the transaction who has to hold both ends of it: the manager who said it and moved on, and the person on the other end of the phone who wants to know what to do differently next time.

Twenty years of standing in that particular spot gives you a fairly clear view of when the phrase is doing real work and when it’s covering for something. Both happen. They’re worth telling apart.

The Version That’s Real and Worth Protecting

Let me be clear before I get critical, because I don’t want this read as an argument that only skills should count. It isn’t.

There’s a version of culture fit I believe in completely.

It’s about whether someone will hold the standards the team holds:

• Pace. Do they work at the speed this group works at, or will that speed grind them down?
• Conflict. Do they raise things directly, or go quiet and go around?
• Ambiguity. How much can they sit with before they need a decision? That matters enormously on a project team and hardly at all in a stable function.
• Commitment level. Whether they go all in at roughly the rate the people around them do.

That last one is worth dwelling on. I noticed something about my own working life recently, which is that I’ve ended up surrounded by people who commit to things at roughly the level I do. Nobody screened for that. It accumulated. But it’s real, and it’s not nothing, and a team where half the people are committed and half are along for the ride is a team with a problem no org chart will show you.

All of that is legitimate. It’s also why technical ability on its own doesn’t predict whether a hire works out, and why the culture a company actually has matters more than the benefits it advertises. I’ve argued both of those things and I still would.

So when a manager tells me a candidate wasn’t a fit and can describe which of those things they mean, I take it seriously and we adjust the search. That’s a useful conversation and it makes the next round better.

The Version That’s Just Familiarity

Then there’s the other one.

Sometimes “not a culture fit” means: this person didn’t feel familiar to me.

They didn’t come up the same way. They don’t talk about work in the same register. They went to a different school, or worked in a different industry, or have an accent, or are noticeably older or younger than the rest of the group, or simply didn’t produce the small easy rapport that makes an interview feel like it went well.

That’s not a hiring criterion. It’s a comfort reflex. And it’s extremely difficult to see in yourself, because it doesn’t arrive as a thought. It arrives as a feeling that something was slightly off, and then the mind supplies a respectable-sounding reason afterward.

I’m not accusing anyone of bad faith. The managers I work with are decent people who would be genuinely upset to think they’d done this. That’s exactly what makes it worth naming: nobody catches it by intending to be fair, because intending to be fair is not the mechanism it operates on.

There’s a particular moment where it shows up. When you’ve got a shortlist of three and all of them can do the job, something has to break the tie, and the honest tiebreaker is often the one you can’t say out loud. I’ve written before about what to do when every candidate is genuinely exceptional. The short version is that this is precisely the moment to have decided your criteria in advance, because if you haven’t, comfort will decide for you and call itself judgement.

The Arithmetic Problem in Alberta

Here’s why this isn’t only a fairness argument, and why I’d raise it with a manager who has no patience for that framing at all.

In this province, for a senior technical role, you are frequently choosing from a pool of a few dozen people.

Not a few thousand.

Consider:

• A Process Engineer with the right project background and the right regulatory exposure
• A finance leader with SAP consolidations depth
• A Contract Specialist who’s managed claims on a major capital build

When I map those searches properly, the number of people in Alberta who genuinely qualify is often between twenty and sixty, and a good portion of them are settled, not looking, or already spoken for.

Apply a familiarity filter to a pool that size and you don’t have a fairness problem. You have an availability problem. You’ve taken a group that was already barely large enough and quietly removed the people who came from a different industry, or trained somewhere else, or are ten years older than the team, or arrived in Canada as an adult. That’s not a rounding error at that scale. That’s most of your remaining options.

I’ve watched companies run the same search three times over eighteen months, rejecting people each round for reasons nobody could articulate, and conclude that the talent doesn’t exist. Sometimes it genuinely doesn’t. More often it walked through the door in month two and felt unfamiliar.

If the fairness case doesn’t move you, the arithmetic should. In a market this small you cannot afford to hire for comfort.

Why the Interview Can’t Find It Anyway

Set aside which version of culture fit a manager means. There’s a separate problem: the interview is a poor instrument for measuring either one.

An interview is a compulsory performance. Everybody arrives having prepared to be the right person. They’ve read the website, rehearsed their examples, thought about what this company probably wants to hear, and dressed the way they think you expect. That’s not dishonesty. It’s the format working as designed. We ask people to present themselves and then act surprised that we got a presentation.

What you can assess well in that setting is real: technical depth, how someone reasons through a problem, whether their examples hold up when you push on them. Structure helps a great deal with all of it, which is why a structured interview process produces better decisions than an unstructured one.

What you cannot assess well is how someone will be at month seven when the project is behind and they’re tired. Forty-five minutes measures interview skill and social ease, and those correlate with things you didn’t mean to hire for: confidence, extroversion, and having grown up around people who talk the way your panel talks. Some of the best hires I’ve placed interview adequately at most.

So when a panel says the skills were there but the fit wasn’t, my honest reaction is that the room couldn’t have told them that. Something else happened in there, and it’s worth working out what.

Where the Signal Actually Is

If the interview can’t find it, what can? Voluntary behaviour, mostly. The things people do when nobody requires them to.

What does a candidate ask about, unprompted? Not their prepared question at the end, but the thing they got curious about halfway through and interrupted to ask. That tells you what they actually care about, because it wasn’t rehearsed.

What have they done that nobody made them do? Took on the messy work nobody wanted. Learned a system that wasn’t their job. Stayed with a project through a bad stretch when leaving would have been easy and reasonable.

References, asked properly. Nearly everyone answers yes to “would you rehire them,” which makes it a question that costs a phone call and buys nothing. Ask instead what this person did when something went badly: how they behaved under pressure, what they’re like when they disagree with someone senior. You get real answers to that, because a referee has to actually remember something.

Why did the last three people leave this seat? Not the exit interview version, the real one. In a small market, recruiters hear the honest answer eventually, because people tell us things they don’t tell their employer. If a role has turned over three times for the same reason, you’re not looking for a better fit. You’re looking at a job that needs changing, and no hire fixes it. That’s also why the first ninety days tell you more about whether a hire worked than any interview did.

What to Say Instead

Here’s the practical part, and it’s simple.

Finish the sentence.

Not a culture fit because:

• “…this team ships fast and makes decisions with incomplete information, and everything in that conversation suggested he needs more certainty than we can give him.”
• “…we’re a small group where everyone raises problems directly, and she described three situations where she went around a manager instead of to him.”
• “…the role requires working alone for long stretches, and he lit up describing collaborative work and went flat describing solo work.”

Those are all real, defensible reasons. They’re specific enough to argue with, which is the point. They give me something to work with on the next round, and they give the candidate something honest if they ask.

If you can’t finish the sentence, you don’t have a reason yet. You have a feeling. Feelings are worth paying attention to, since they’re often early information about something real, but they’re worth interrogating before they become decisions. Sit with it for a day. If a specific reason surfaces, it was real. If nothing surfaces, that’s information too.

There’s a version of this that shows up as a team problem rather than an individual one, where one person on the panel is weighing experience and another is weighing fit and nobody agreed what mattered beforehand. That’s one of the more common interview pitfalls, and it’s fixable in a fifteen-minute conversation before anyone walks into the room.

And for candidates who’ve received this feedback: some of it is about you and most of it isn’t. If you’ve been told it more than twice, it’s worth asking someone honest whether there’s something specific in how you come across in interviews, because occasionally there is and it’s fixable. But if it’s happened once, from one company, with no explanation attached, take considerably less from it than you’re inclined to. You’ve likely been given a sentence somebody used to end a conversation, and it was never really about you at all.

If Every Rejection Sounds the Same

If you look back at your last three rejections in a search and they all came back as culture fit, that’s worth a conversation. Not because the instinct was wrong, since it might have been right all three times. But three unexplained rejections in a small market is expensive, and it’s usually a sign that the criteria were never agreed rather than that three good candidates were all subtly unsuitable.

We recruit senior technical, engineering, safety, finance and contracts roles across Calgary, Edmonton and Saskatchewan, in markets where the qualified pool is small enough that every avoidable rejection costs you real time. Part of what we do is push back when a search is losing people for reasons nobody can name.

If that would be useful, get in touch. I’d rather have the awkward conversation in week three than watch a good search stall through November.

Culture Fit FAQs