Culture Fit vs. Culture Add: What to Hire For Instead

In short: "Culture fit" usually ends up meaning "someone like us." That feels comfortable and makes teams weaker over time. "Culture add" asks a better question: what does this person bring that we're missing, while still sharing the standards we won't compromise on? Separate your values, which aren't negotiable, from your habits, which are. Then hire people who share the first and stretch the second. For global teams, this is the job itself.

A band with four guitarists

Picture a band that has just lost its drummer. They audition a few people and choose the one they got on with best. This candidate likes the same records, dresses the same way and laughs at the same jokes. They're great company. They're also a guitarist.

Now the band has four guitarists and no rhythm.

That's what "culture fit" does when nobody defines it. Interviewers quietly ask themselves "would I enjoy working with this person?", and the honest answer is almost always "yes, if they're like me." Nobody means any harm. But a team that hires this way gets more agreeable and less capable with every round.

What "culture" should mean in a hiring decision

The trick is to split culture into two lists.

Values are the things you won't bend on: owning your mistakes, telling a client the truth when the news is bad, finishing what you start. Everyone on the team has to share these.

Habits are how things happen to be done today: Slack over email, long meetings or short ones, jokes in standup, whether people speak up in the room or follow up afterwards. These are preferences. A team where everyone has the same habits has no way to notice its blind spots.

"Culture fit" tends to screen on habits and call them values. "Culture add" screens hard on values and deliberately looks for different habits.

How to interview for culture add

Before the interview, write down one or two things the team is noticeably bad at. Maybe nobody pushes back on the founder. Maybe everyone is great at starting work and weak at documenting it. Then look for the candidate who fills that gap.

A few questions that tend to reveal it:

• "Tell me about a time you disagreed with how your team did something. What did you do?"
• "What was your last team bad at that you ended up fixing?"
• "What would your previous manager say you do too much of?"

Add one rule for the debrief: "I just didn't click with them" doesn't count as a reason on its own. Name the value they fell short on, or the habit that worried you and why it matters to the work.

Why this matters more on global teams

When you hire across countries, you're certain to get different habits. A developer in Vietnam, an analyst in South Africa and a support lead in the Philippines will each bring different expectations about hierarchy, directness and how to disagree.

Some teams read those differences as poor fit. A developer who doesn't challenge a senior engineer on a group call can look passive, when in their last workplace doing so would have been rude. The answer isn't to hire only people who already behave like head office. It's to make your norms explicit. Write down how you want disagreement raised, how quickly you expect replies, and that "I'm not sure" is a perfectly good answer. Then people from any background can meet the same bar.

Handled this way, the differences become an advantage. The team in another time zone spots the edge case your local team stopped seeing long ago. The quieter hire writes the documentation nobody else would.

One practical step

At your next hiring debrief, ask every interviewer to answer two questions before anything else. Did this person show our values? What would they add that we don't have? If nobody can answer the second question, keep looking.

It's the same approach we use when we build dedicated offshore teams in places like South Africa and Vietnam. We write the norms down before the first hire starts.