Cultural add
Also called: culture add
Why teams moved off “cultural fit”
“Cultural fit” was the standard hiring criterion for two decades, and it broke for two reasons:
- It encoded sameness. “Fits with our culture” usually meant “looks, sounds, and went to school like us”. The criterion is one of the strongest predictors of homogeneous teams.
- It was undefined. “Culture” became a placeholder interviewers used to justify a vague negative without saying what they actually meant.
Cultural add replaces both problems. The question shifts from “are you like us?” to “what do you bring that we don’t have?”.
How to evaluate cultural add concretely
The vague version of cultural add is no better than fit. The concrete version names dimensions:
- Experience the team lacks. A first product engineer who has shipped to enterprise customers. A first marketer with B2B-SaaS exposure. Name the gap before the interview.
- Working styles that complement the team’s defaults. A team that defaults to synchronous benefits from one async-first hire. A team that defaults to fast iteration benefits from one careful planner.
- Perspective on the user. A recruiting tool team adding the first person who has been a candidate recently, not a recruiter.
The output of the interview is a written claim: “this person adds X that the team currently lacks”. If the interviewer can’t write that claim, they shouldn’t be voting for cultural add as a reason.
What it doesn’t replace
Cultural add doesn’t replace the hiring bar. A candidate who would add range but can’t do the job is still a no-hire. Add is a positive signal, not a compensating one.
It also doesn’t replace diversity hiring — those are pipeline interventions; cultural add is an evaluation criterion. They reinforce each other but are not the same.
Where Join fits
Join’s interview scorecards support custom rubric dimensions per role, so a team can name “what we lack” as an explicit evaluation criterion alongside skills. See the features page.
