Behavioural and culture fit fundamentals

Whether your past behaviour predicts your future behaviour on their team, which is a narrower and less personal question than candidates assume. The premise of the format is that what somebody did under real constraints, with real colleagues, is the best available evidence for what they will do again, and that self-description is nearly worthless by comparison. So the interviewer is listening for a specific decision you made, the information you had when you made it, and what happened as a result. Likeability is not the criterion and is mostly a confound the format exists to suppress: a well-run round scores against written competencies, and a candidate who is charming with no evidence attached loses to one who is dull and specific. The practical consequence is that your preparation is a set of remembered events, not a set of adjectives.

Because a hypothetical measures your taste and your vocabulary, and the round is trying to measure your behaviour. "I would sit down with them and understand their perspective" is what everybody says, costs nothing to say, and is unfalsifiable — there is no follow-up that can distinguish someone who does it from someone who has read about it. A real event has friction in it: the thing you said that did not work, the week you left it, the colleague who was still annoyed afterwards. Interviewers are trained to notice the tense, because the slide from "I did" into "I would" is the commonest tell that a candidate has run out of examples and is improvising a policy instead. If you genuinely have no example, say so and offer the nearest real one rather than inventing a philosophy.

The same question answered twice, and the conversion is mechanical once you see where the tense slips.

Q: "How do you handle it when a colleague isn't pulling their weight?"

HYPOTHETICAL - what most candidates say
  "I'd speak to them directly first rather than going to the manager.
   I'd try to understand whether something else was going on, and I'd
   focus on the impact on the team rather than making it personal. If
   nothing changed I'd escalate."

  Score: no evidence. Every sentence is a policy. Nothing here could
  be untrue. The interviewer records "no example offered".

CONVERSION - three questions to ask yourself
  1  When did this last actually happen to me?
     -> Q1 last year, the reconciliation service, with Tom.
  2  What did I specifically say, in words?
     -> "Your two tickets have been in review for nine days and the
        release is blocked on them. What's in the way?"
  3  What happened next, and what did it cost?
     -> He was covering an on-call rota nobody had reassigned. Fixed
        in a day. Release slipped four days, not two weeks.

REAL - the same values, now with evidence
  "Last year on the reconciliation work, Tom's two tickets sat in
   review for nine days and the release was blocked. I went to him
   before I went to our lead, and I asked what was in the way rather
   than why he was late. It turned out he'd inherited an on-call rota
   nobody had reassigned when Anya left, so he was firefighting every
   afternoon. I took the rota for a week and we split his tickets.
   The release slipped four days. I also told our lead about the rota,
   because that was the actual defect and it would have hit whoever
   was next."

The conversion works because the values in the hypothetical were fine. What was missing was the event, and the three questions recover it: an occasion, a sentence you actually said, and a consequence. Nothing about your judgement had to change.

The detail that makes the real version score is that the diagnosis was wrong at the start. The candidate went in thinking somebody was slow and found a structural problem, which is evidence of asking before concluding — a thing the hypothetical merely claimed. Interviewers weight surprises heavily, because a story where the candidate's first assumption held is usually a story that has been smoothed.

The last two sentences do the work that separates a competent answer from a senior one. Fixing the instance is expected; naming the rota as the real defect and reporting it upward shows that you think past your own unblocking. Note that it is also the part that could not have been invented, because it is specific to this company and this departure.

Answers are not scored on the first telling. They are scored on what survives three follow-ups.

The three probes are not escalating scepticism, they are three different measurements. The first asks for words in quotation marks, because a candidate who was present can usually reconstruct roughly what they said and a candidate describing a summary cannot. The second asks for the other person's response, which is where invented stories collapse: made-up colleagues either agree immediately or are cartoonishly obstructive, whereas real ones say something partly reasonable.

The third probe is doing something else again. By that point the interviewer believes the event happened and wants to know whether you have thought about it since. "Nothing, it worked out" is a weak answer even after a success, because every real project contains a decision worth revisiting.

The practical preparation this implies is depth over breadth. Six stories you can survive three probes on beat fifteen you can only summarise, and the rehearsal that matters is not the ninety-second version — it is being able to answer what the other person said, who else was in the room, what the dates were, and what you would change.

Candidates lose here in a specific way worth naming: they answer the probe with more of the summary, at a higher volume. When asked what you said, say what you said. If you cannot remember, saying "I can't quote it, but the substance was that the deadline was at risk and I wanted to descope rather than add people" costs you nothing and reads as honest.

Evidence, ideally quoted, mapped to named competencies decided before you walked in. A well-run round has three or four of them — ownership, collaboration, dealing with ambiguity, handling disagreement — each with a written description of what a strong and a weak answer looks like, and the interviewer's job is to record what you said against those lines rather than to form an impression. This matters to you because it tells you what to supply: a fact somebody can write down. An answer with no quotable specifics leaves the scorecard blank, and a blank scorecard is scored as no evidence rather than as neutral, which is why pleasant, fluent, unspecific candidates are rejected with debriefs that say "did not get much".

Four recur almost everywhere, whatever the company calls them. Ownership, which is whether you carry a thing past the point where it stops being formally yours. Collaboration and conflict, which is what you do when a competent person disagrees with you. Dealing with ambiguity, which is how you move when the requirements, the priority or the owner is undefined. And self-awareness, which is whether you can describe your own mistakes and the feedback you have received without either defending or performing. Senior loops add influence and judgement about people. The reason this list is worth knowing is that it tells you how to build a story portfolio: not one story per question you have heard, but a small set of events rich enough to answer across these four.

It matters less than candidates fear and in a different way than they think. Structure exists precisely to stop the round measuring similarity to the interviewer, and the better the process the less warmth buys you. What does count is a narrow, defensible version of the same thing: whether the interviewer believes colleagues can raise a problem with you, disagree with you, and give you bad news. That is not charm — it is demonstrated in how you talk about people who were wrong, whether you concede a point during the interview itself, and whether any of your stories contain a colleague who improved your thinking. Contempt for a former colleague or manager is the version of unlikeability that actually costs offers, because it predicts how you will describe this team later.

Because two independent samples of the same behaviour are worth more than one, and because a story told twice is a consistency check. Interviewers in a well-run loop write their scores before the debrief, so two people asking about conflict is not duplication, it is calibration. It is also how invented examples are caught, since the details drift on the second telling in ways they do not for a real event. What follows for you is that you should not fear repeating a story across rounds — you should fear telling it differently. If you are asked something a previous interviewer covered, say so, offer to give the short version and then a second example, and let them choose. That reads as organised, not as evasive.