The behavioural round is a structured assessment of how you have worked with other people, scored against a written competency rubric rather than on how likeable you seemed. It is where senior candidates are rejected most often, and it rewards a small bank of real stories over memorised answers.
High demand21 min readHiring Manager, Engineering Manager, Senior / Staff Engineer on an interview panel, Technical Recruiter / Talent Partner, HR Business Partner running a values roundUpdated 2026-07-27
Assumes you know: Two or three years of work you can describe in specifics, technical or not, Willingness to say what you personally did, and what you got wrong
Overview
What this area actually covers
A behavioural interview asks you to describe things you have already done, on
the theory that past behaviour predicts future behaviour better than a
hypothetical does. The questions are variations on a small set of stems — a
conflict, a failure, something you owned, a time you influenced someone, a time
nobody could tell you what the requirement was — and the answers are scored
against a list of competencies written down in advance. Everything
arbitrary-feeling about the round becomes legible once you accept that the
interviewer is not forming an impression of you: they are collecting evidence
against named criteria and will have to defend the rating afterwards.
Three things get wrongly bundled in. Salary, notice period and levelling are the
offer conversation, which has different rules and a different counterparty.
Culture fit, in a company that hires competently, means alignment with how the
team works — how disagreement is handled, how much autonomy is expected — not
whether you would be fun at lunch. And "tell me about yourself" is not a
warm-up; it is scored on whether you can choose what matters out of ten years of
material.
There is a fourth confusion worth heading off, because it changes how you should
prepare. A behavioural question is not a hypothetical. "How would you handle a
disagreement with your tech lead" and "tell me about a disagreement you had with
your tech lead" look like the same question and are graded differently: the
first invites a philosophy, the second demands an episode with a date and a
person in it. If you answer the second with the first, you have produced no
evidence, and an interviewer who is short of time may not push you back onto the
rails.
Now practise it
25 interview questions in Behavioural & Culture Fit, each with the rubric the interviewer is scoring against.
This section is divided by the competency being probed rather than by the
literal wording of questions, because the same story is re-cut to answer several
stems and organising by wording would duplicate everything. Read the STAR
material first, since it is the container everything else sits inside.
Subsection
What it is for
The STAR Method
The shape an answer has to have to be scoreable
Introduction & Career Narrative
Choosing what matters out of ten years
Conflict & Collaboration
Disagreement described without blame
Ownership & Impact
Scope, outcome, and your honest slice of it
Failure & Learning
A real failure, owned, with a consequence
Leadership & Influence
Moving people who do not report to you
Pressure & Ambiguity
Acting when the brief is missing or impossible
Questions to Ask Them
The reverse interview, and reading the answers
The STAR Method covers the structure — situation, task, action, result — and
more usefully, the proportions. It exists as its own subsection because almost
everyone has heard of it and very few people apply it correctly: the standard
failure is three minutes of situation and twenty seconds of action, which is
precisely inverted from what is being scored. You will find timings, worked
answers, and the two extensions experienced interviewers listen for that the
acronym omits.
Introduction & Career Narrative handles "tell me about yourself" and "walk
me through your resume", which sound like formalities and are not. They are
separated out because the skill is editorial rather than descriptive: you are
being scored on what you chose to leave out and whether the sequence has a logic
that arrives at this role. Expect a structure for the ninety-second version, and
guidance on the harder variant where your history genuinely does not point in a
straight line.
Conflict & Collaboration covers disagreements with peers, with a manager,
and with stakeholders outside your team. It has its own area because it is the
single most discriminating question family in the round and the one candidates
most reliably mishandle, either by choosing a conflict where they were
transparently right or by choosing one where they were blameless. The material
is about describing an opposing position fairly, which is the actual signal.
Ownership & Impact is about describing scope honestly and quantifying an
outcome without claiming a causal chain you cannot defend. It is separate
because it contains a specific technical difficulty: saying "I" without erasing
your colleagues. You will find phrasings that attribute a team result to a team
while making your own contribution unmistakable, and worked examples of
quantifying impact when no number was ever measured.
Failure & Learning deals with choosing a failure that is genuinely a failure,
taking responsibility for it in a way that does not read as performance, and
showing what changed afterwards. It exists as its own subsection because the
selection problem is most of the difficulty: a failure that was somebody else's
fault, or one so small it cost nothing, both score as evasion. Expect criteria
for what makes a usable failure story and how to end one without a moral.
Leadership & Influence covers driving change without authority, mentoring,
and carrying a technical decision through an organisation that did not
initially want it. It is separated out because it is what senior and staff loops
weight most heavily, and because the evidence required is different — not that
you were in charge, but that people who could have ignored you did not.
Pressure & Ambiguity is about competing deadlines, unclear ownership, and
decisions taken without enough information. It has its own area because the
competency underneath is decisiveness rather than endurance: interviewers are
checking whether you act and adjust or wait for clarity that never arrives. The
material includes how to describe a decision that turned out badly but was
correct on the information available.
Questions to Ask Them is the reverse interview at the end of the hour. It
sits last because it is both the least prepared and the only part where you are
gathering rather than giving evidence. You will find questions that reveal
something the careers page cannot, and — more valuably — what specific answers
tell you about how the team actually operates.
Where it sits in a real system
In a typical loop the signal is collected in two or three places: the recruiter
screen, which checks motivation and coherence; the hiring manager conversation;
and at larger companies a values or leadership round run by someone outside the
team, whose job is to be unmoved by how badly the team wants the seat filled.
Amazon's bar raiser is the best-known version of that role.
What happens next is the part candidates never see, and it explains most of the
advice on this site. The interviewer maps their notes to competencies and writes
a recommendation before the debrief, so opinions are not contaminated by the
room. In that debrief "I liked them" carries almost no weight, because it cannot
be argued with; what carries weight is a quoted specific — she described the
tradeoff she rejected and why, or he could not name one thing he would do
differently. A story that produced no quotable specific is filed as no
evidence, which is nearer a no than a neutral.
Loading diagram…
The branch that decides most outcomes is the left one. Notice that "no evidence"
does not send you to a rejection directly — it flows into the debrief and then
strands you at the gate that asks whether every competency was covered. This is
why a pleasant hour in which nothing concrete was said produces a rejection the
candidate finds inexplicable: nobody disliked you, and nobody could write
anything down.
Competency
What the interviewer is trying to establish
Where it is usually probed
Ownership
Whether you hold outcomes or hold tickets
"Something you owned end to end"
Collaboration
Whether working with you is expensive
Conflict and disagreement questions
Self-awareness
Whether you can be given feedback
Failure questions, "what would you change"
Influence
Whether you can move people who do not report to you
Leadership without authority
Judgement under ambiguity
Whether you act or stall when the brief is missing
Unclear requirements, bad deadlines
Communication
Whether a stakeholder would understand you
The whole hour, every answer
Who does this work
The people running these rounds are mostly not specialists. A hiring manager or
engineering manager conducts them because the hire is theirs to live with;
senior and staff engineers get pulled onto panels with one training session and
a question bank. Recruiters and talent partners run the first screen and, in a
mature company, own the design of the loop and the calibration of its
interviewers. An HR business partner may run a values round. Designing
structured interviews is a discipline of its own, but you will rarely meet a
specialist in the chair opposite you.
This matters practically. Your interviewer is probably under-trained, short of
time, and working from a question sheet. They will not extract your best
material for you. If a story needs a preamble to make sense, it will die.
It also means the quality of the hour varies enormously and none of that
variance is about you. One interviewer will ask four questions and ladder deeply
into each; another will ask twelve and take no notes; a third will spend twenty
minutes describing the team. Your defence against all three is the same: answer
in a shape that is easy to write down, and put the most quotable sentence early
rather than saving it for a conclusion that may never be reached.
Worth knowing too is that most panels are calibrated against each other. Where a
company runs calibration properly, an interviewer's ratings are compared over
time against outcomes and against their colleagues, which is why an experienced
interviewer will seem oddly unmoved by charm. They have been shown, in a
meeting, that their instincts about likeability predicted nothing.
The vocabulary of the loop
Interviewers use a private vocabulary about you, and hearing it used correctly
by a candidate is mildly disarming. More usefully, knowing the words makes the
process legible: once you understand what a debrief is for, the advice to leave
behind quotable specifics stops being a stylistic preference and becomes
obvious.
Term
What it means
Why it affects your answers
Competency
A named behaviour the loop must gather evidence on
Your story is filed under one of these or under nothing
Rubric
The written description of what weak, adequate and strong look like
The gap between adequate and strong is usually specificity, not scale
Signal
Anything in your answer that maps to a rubric line
An enjoyable anecdote with no signal in it is a wasted ten minutes
Laddering
Following one story with progressively narrower questions
Prepare depth on three stories rather than breadth on ten
Debrief
The meeting where interviewers compare notes and decide
Quotes survive it, impressions do not
Calibration
Comparing an interviewer's ratings against colleagues and outcomes
Why charm moves an experienced interviewer less than you expect
Bar raiser
An interviewer from outside the team with a veto
Their incentive is the long-run bar, not filling this seat
Coverage
Whether every competency was evidenced somewhere in the loop
A competency nobody probed can trigger an extra round
Downlevelling
Offering the role at a lower level than advertised
Often decided on scope of ownership described in this round, not on coding
Values round
An interview specifically on stated company principles
Read the published principles and map two of your stories to each
Two of those rows are worth dwelling on. Coverage explains the round that
appears out of nowhere after you thought the loop had finished; it usually means
one competency has no evidence rather than that anything went wrong.
Downlevelling explains a rejection that arrives phrased as an offer, and it is
frequently decided here: the scope you describe owning in your stories is the
strongest available proxy for the scope you can be trusted with, and a candidate
who only ever describes tasks will be levelled against tasks.
The word people most often misuse is "culture fit". In a company that hires
competently it names a small number of concrete working preferences — how much
autonomy is expected, whether disagreement happens in the room or afterwards,
how much process there is around a change. Those are legitimate things to
select for and legitimate things for you to evaluate in return. Where the phrase
is used loosely it becomes a licence for exactly the unstructured judgement the
rest of the apparatus exists to suppress, and hearing it used that way in your
own interview is information about the employer.
Demand, adoption and how that is changing
Structured behavioural interviewing spread for two reasons that have not gone
away. Unstructured conversation is a weak predictor of job performance and
produces feedback nobody can defend, and in several jurisdictions a hiring
decision you cannot evidence is a legal liability. The direction of travel for
two decades has therefore been away from the free chat and towards a fixed
question set with a written rubric; large employers went furthest, because they
hire at volume and get sued.
Two newer pressures push the same way. Remote hiring removed the incidental
signal that used to come from a day on site, so more weight now sits on how you
talk in a scheduled hour. And as take-home exercises and coding screens become
easier to complete with AI assistance, employers lean harder on the rounds that
are difficult to outsource — live conversation about work you personally did,
with unscripted follow-ups. That second pressure has a direct consequence for
you: expect more laddering than candidates met five years ago, and expect at
least one interviewer to keep asking about the same episode until they reach a
detail you would only know if you were there.
The honest counterweight is that adoption is uneven: at a twenty-person startup
the founder may still decide on instinct in half an hour. Assume structure and
be pleasantly surprised. The other counterweight is that some organisations
implement the form without the substance, running a rubric they never calibrate,
which produces the worst of both worlds — a rigid script and an arbitrary
outcome. You cannot detect this from outside, and preparing for the structured
version costs you nothing in the unstructured one.
What makes it hard
The difficulty is not that the questions are unknown — they are famously
predictable. It is retrieval. You have lived through hundreds of relevant
episodes and you are asked to produce the right one in four seconds, under
adrenaline, in a form that fits ninety seconds of speech. Without preparation,
the story that surfaces is the most recent rather than the best.
Second, honesty and self-presentation pull against each other here. You have to
say "I" without erasing four colleagues, and claim a result without claiming a
causal chain you cannot defend. Most candidates resolve this by drifting into a
comfortable "we", which reads as hiding, or an inflated "I", which reads as
unreliable once one follow-up lands.
Third is the problem nobody writes about: some people's work has been genuinely
unremarkable. Five years of tickets on a stable internal system, no incidents,
no migrations, no conflict worth the name. That is common and it is not a
character defect, but the round is unkind to it. The way out is not to invent
something; it is to lower the scale and raise the resolution — how you sequenced
a schema change, a colleague you talked out of a bad abstraction, a bug you
shipped and how you found it — because the rubric asks about judgement, not
scale. What fails is the alternative candidates reach for, which is borrowing a
story from a blog post or a teammate. Fabrication collapses on the first
follow-up, because the next question is always about a detail only a participant
would hold: what the volume was, who pushed back, what you decided not to do.
Invented stories have no second layer, and the silence when one is asked for is
unmistakable.
Fourth, and specific to experienced candidates, is compression. Ten years of
work does not fit in an hour, and the instinct of a senior person is to describe
the system rather than the decision, because the system is the part they are
proud of. An interviewer who asks about a conflict does not need three minutes
of architecture to understand it. Learning to give exactly enough context for
the decision to make sense — usually two sentences — and then spending the
remaining time on what you did, is the adjustment that separates senior
candidates who pass this round from equally senior candidates who do not.
How an answer is scored, sentence by sentence
It is worth seeing what a rated answer looks like from the other side, because
the difference between a strong and an adequate performance is narrower and more
mechanical than candidates imagine. Both of these answer the same stem —
describe a time you disagreed with a colleague about a technical decision — and
both are honest.
ADEQUATE
"We were deciding between two message brokers and I disagreed with our
tech lead. I thought the simpler option was better because the team
was small. We discussed it, I made my case, and in the end we went
with his choice. It worked out fine and I learned to pick my battles."
Interviewer note: disagreed, deferred. No detail on the argument.
Cannot tell whether he was right or whether he engaged with her case.
Competency: Collaboration - insufficient evidence.
STRONG
"Our tech lead wanted Kafka for an event stream we expected to grow.
I argued for the queue we already ran, because we were four people
with no Kafka operational experience and the volume projection came
from a sales forecast rather than measured traffic.
Her case was that migrating later would be expensive once consumers
existed - which was the strongest argument against me, and correct.
So I proposed we make the consumers idempotent and hide the transport
behind one interface, which put the migration cost at about a week
whenever we needed it.
We stayed on the existing queue. Volume never reached the forecast,
so we did not migrate, but I would still call her concern the right
one to have raised - if it had grown, the interface is the only
reason the switch would have been cheap."
Interviewer note: stated the opposing case better than his own, and
named it as correct. Resolved by changing the shape of the decision
rather than winning it. Quotable: "her case was the strongest
argument against me".
Competency: Collaboration - strong. Judgement - strong.
The structural differences are countable. The strong answer names the other
person's argument and rates it fairly; it describes an action that changed the
option set rather than the volume of the argument; it separates the outcome from
the judgement, so being right by luck is not claimed as being right; and it
gives the interviewer a sentence they can quote in the debrief without
paraphrasing. None of that requires a more impressive career. It requires
knowing what is being written down.
The follow-up is where the round is decided
Most candidates prepare an answer and stop. Interviewers do not stop; they
ladder, and the second and third questions are where the rating is actually set.
The pattern is stable enough to rehearse against.
Loading diagram…
The question to look at is the third one. It is the fabrication detector, and it
is asked casually enough that candidates answer it carelessly. Only a
participant knows who else was present and how the room divided; anyone
recounting a story they read or heard produces a vague answer here, and the
vagueness is the finding. Prepare your stories with the cast list attached and
this question becomes the easiest of the four.
The fourth question has its own trap, which is answering it with a virtue. "I
would have communicated more" is not a change, it is a genre. "I would have put
the two options in a document before the meeting instead of arguing them live,
because two of the four people had no context and could not participate" is a
change, and it tells the interviewer you have thought about the episode since
rather than during.
Why study it
Because it is the round where senior candidates are rejected, and the round they
prepare for last. A staff-level loop will forgive you for fumbling one
algorithm; it will not forgive an hour in which you could not describe a
disagreement without blaming someone. Three hours of honest preparation moves
this round further than the same hours spent on a fourth system design practice,
and the preparation is transferable in a way technical cramming is not — writing
down what you decided over the last three years, with the alternatives you
rejected, is also how you build a promotion case.
There is a second return that has nothing to do with interviews. The exercise
forces you to look at your own last few years as a sequence of decisions rather
than a sequence of jobs, and most people discover in doing it that they have
been telling themselves an inaccurate story: that a period they remember as
wasted contained the decision they are proudest of, or that a project they
describe as a success was carried by someone else. That recalibration is worth
having regardless of whether you are looking.
Who should skip it: if you are failing at the technical screen, fix that first,
because this round will never be reached. And with no employment history at all,
spend the time on projects instead — you can only tell stories from a life you
have lived. If you are early enough in a career that your best material is a
university group project, one honest small story is still better than one
inflated large one, and interviewers calibrate the scale expected to the
seniority in front of them.
How few stems there really are
The reason a story bank works is that the question space is small. Almost every
behavioural question you will ever be asked is one of these, rephrased. Map your
episodes against the right-hand column and you can see your own gaps.
Stem, as it is usually said
Competency being gathered
Tell me about yourself
Communication, and editorial judgement
Something you owned end to end
Ownership, scope
A time you disagreed with someone
Collaboration, and whether you argue fairly
A failure, or something you would do differently
Self-awareness
A time you influenced without authority
Influence
A time the requirements were unclear
Judgement under ambiguity
Competing deadlines, or too much at once
Prioritisation, and whether you escalate
Feedback you received and did not like
Coachability
Someone you helped grow
Mentoring, and whether you invest in others
Why this role and this company
Motivation, and whether you will stay
Ten rows, and a bank of three well-worked episodes can usually reach seven of
them. The two that most often have no candidate story behind them are
coachability and mentoring, because both require you to have been in a slightly
uncomfortable position and remembered it. If your bank cannot answer those two,
that is the gap to fill before the loop rather than the tenth conflict story.
Your first hour
Do not read more advice. Build the story bank, because every question in this
section draws from it. List eight to twelve episodes from the last three or four
years, one line each, no polish: anything where you decided something, argued
with someone, broke something, or finished something unglamorous. Then, for the
three strongest, fill in five fields:
Episode: one line, the thing itself
The fork: the decision that was mine, and the option I rejected
My slice: who else was involved, and precisely what I did
The number: before value, after value, how it was measured (or: scope instead)
The residue: what changed afterwards because of it - process, code, or in me
An hour gets you three of these, and the artefact is a one-page bank. The test
of it is whether each episode can answer at least three different stems — the
ownership one, the conflict one, the ambiguity one — because that re-cutting is
what replaces memorised answers. A story you can only aim at one question is a
liability, since that question may not be asked.
Once the three exist, do one more pass that takes ten minutes and is the part
people skip. Against each episode, write the cast: who else was in the room,
what each of them wanted, and who was still unconvinced at the end. That list is
what the third follow-up question asks for, and having it written means you
recall it under adrenaline instead of reconstructing it.
Then say one of them out loud, timed. Ninety seconds is shorter than it sounds,
and the first attempt almost always spends sixty of them on context. Cut until
the situation fits in two sentences. That single edit does more for your rating
than anything else you could do with the hour.
What this is not
It is not a personality test, and there is no personality it prefers. Quiet and
direct is fine; what fails is unevidenced. Interviewers are not screening for
extroversion, and where they accidentally do, calibration is what catches it.
It is not a memorisation exercise. Answers learned as text are audibly recited,
go rigid when the question turns out to be slightly different, and have nothing
behind the paragraph you prepared. The bank above stores facts precisely so the
sentences stay fresh.
It is not an invitation to confess. The failure question is asking for
self-awareness, not for the worst thing you have ever done, and a candidate who
volunteers something disproportionate has misread the register rather than
demonstrated honesty. The useful failure is one that cost something real, was
yours, and led to a change you can name.
And it is not soft. The phrase "soft skills" does real damage here, because it
implies leniency. This is the round with the least tolerance for a vague answer,
since vagueness is the one thing it measures directly.
Treat the behavioural round as an evidence round: your job in the hour is to
leave the interviewer holding three specifics they can quote in the debrief.