Ask an interviewer why they passed on a candidate and, more often than you would like, the answer is some version of "great on paper, but I am not sure about the culture fit." It sounds responsible. It sounds like the interviewer is protecting something valuable. In practice, culture fit as it is commonly used is the least rigorous filter in the whole process, and it is quietly doing damage that the rest of your hiring discipline cannot repair. This is the argument for retiring it and putting something concrete in its place.
I want to be fair to the idea, because there is a real kernel inside it. Teams do share values, and a person who fundamentally disagrees with how the work gets done will struggle no matter how talented they are. That part is legitimate. The problem is that almost nobody uses culture fit to mean that. In the room, culture fit usually collapses into a single question that nobody says out loud: does this person feel like us.
Trajectory fit is a hiring approach that matches candidates on the journey they have already completed rather than on how familiar they feel. It asks a concrete, checkable question: has this person already done the journey the role requires, such as taking a company through the stage transition you are about to attempt. Culture fit, by contrast, asks whether a candidate feels like they belong, which rewards similarity and predicts little about performance. Trajectory fit trades a feeling for evidence.
What culture fit actually measures
Strip the language back and culture fit measures familiarity. It fires hardest when a candidate went to a similar school, shares a communication style, laughs at the same references, or reminds the interviewer of themselves five years ago. None of that is culture in any meaningful sense. It is resemblance, and resemblance is a poor proxy for whether someone can do the job.
This matters because the interviewer experiences that familiarity as a signal of quality. The candidate who feels easy to talk to gets the benefit of the doubt. The candidate who is a little different, a little harder to place, has to clear a higher bar without anyone deciding to raise it. The filter feels like judgment. It is mostly just comfort.
The three things wrong with it
The case against culture fit is not that culture does not matter. It is that this particular filter fails on three fronts at once.
- It rewards similarity and narrows the team. A group that keeps hiring for fit gets more like itself with every round. You lose the friction that produces better decisions, and you build a monoculture that is confident and wrong in the same directions.
- It drifts toward bias, and it is hard to defend. Because familiarity tracks background, age, and class, a fit filter quietly correlates with exactly the characteristics you are not allowed to hire on. When a rejected candidate asks why, "they were not a culture fit" is not a reason you can stand behind. It is an ethical and legal liability dressed up as instinct.
- It predicts very little about performance. The thing culture fit is supposed to protect, whether someone will succeed and stay, is barely correlated with whether they felt familiar in a forty-five minute conversation. It measures the interviewer's comfort, not the candidate's future output.
Put together, you have a filter that shrinks your talent pool, exposes you legally, and does not even buy you better hires in exchange. That is a bad trade.
Keep the kernel, drop the vagueness
None of this means values do not matter. Separate the two clearly. There is a legitimate question hiding inside culture fit: does this person agree with how we work, how we make decisions, and what we refuse to compromise on. That is values alignment, and it is worth screening for. You screen for it by naming the specific behaviors your culture actually depends on and asking for evidence of them, not by checking whether the person feels like one of the group.
The vague version, the feels-like-us version, is the part to throw out. Once you remove it, you are left with an obvious gap: if not familiarity, then what should carry the weight in a hiring decision. That is where trajectory fit comes in.
Trajectory fit is the concrete alternative
Trajectory fit replaces a feeling with a track record. Instead of asking whether a candidate belongs, it asks whether they have already done the journey the role requires. The best hire for a company trying to get from Seed to Series A is usually someone who has already made that exact transition and can recognize its failure modes before they arrive. That is checkable. You can point to the company, the stage, the dates, and the decisions the person owned.
The mechanics of this live in what we call career triggers, the specific, evidence-backed markers in a history that predict stage fit, and in trigger-based matching, the practice of screening for those markers instead of keywords or vibes. The anchor idea for the whole approach is trajectory fit, and it is deliberately built to be the opposite of culture fit: concrete where culture fit is vague, evidence-based where culture fit is instinctive, and far easier to apply consistently across candidates who look nothing like each other.
This is also why trajectory fit is the fairer filter. When you evaluate people on documented experience rather than on how much they remind you of the incumbents, you can compare very different candidates on the same terms, and you can explain any decision you make. No filter removes bias by itself, and a lazy trajectory read can still smuggle in assumptions. But a concrete, evidence-based question gives you a much better starting point than a feeling you cannot articulate.
How to make the switch in the interview
The change is smaller than it sounds. Start every search from the hardest problem the hire has to solve in their first year, written as a problem and not a title. Translate that problem into the triggers a person would carry if they had already solved it. Then use the interview to confirm what the candidate personally did, as opposed to what the team around them did, and to probe the decisions they owned when the plan broke. You are gathering evidence of a journey, not testing for belonging.
That evidence is only as good as your ability to review it later. Trajectory signals come out in specific stories, and those stories are easy to lose to a debrief that happens three days after the conversation. An interview intelligence tool keeps the interview as a structured, reviewable record so the panel is comparing what candidates actually said, not competing memories of who felt like the better fit.
Where Numi fits
Numi is an EU-hosted interview intelligence tool. It records, transcribes, and structures interviews on European infrastructure so the trajectory evidence, the transitions a candidate drove and the calls they owned, is captured as a comparable record. It does not score, rank, or produce a culture-fit rating, and that is deliberate. Whether a candidate is the right hire is a judgment your team should make on the evidence, not a number a model hands you. Numi's job is to make the evidence clear and reviewable, so the loudest voice in the debrief is the transcript rather than whoever felt the most comfortable.