Common behavioural interview questions, and what each one is really testing

There appear to be hundreds of behavioural questions. There are about six things being tested, asked in different words, and preparing for the six is a far better use of an evening than memorising the hundreds.

Here they are, with what each is actually checking.

1. Ownership

Tell me about a project you led. Describe something you drove end to end. When did you take responsibility for something outside your remit?

Being checked: whether you do things or things happen around you.

What decides it: the ratio of "I" to "we". Be generous about credit and precise about your part. "The team shipped it; I owned the data model and the migration plan" is both honest and clear.

2. Conflict and disagreement

A time you disagreed with your manager. A difficult colleague. When you had to push back.

Being checked: whether you can disagree without it becoming a problem — and, quietly, whether you are the difficult one.

What decides it: how you describe the other person. Candidates who fail this question describe an idiot. Candidates who pass describe a reasonable person with a different view, and explain how it resolved. Steelman them, even if they were wrong. Especially if they were wrong.

3. Failure

Tell me about a time you failed. A mistake you made. A project that went badly.

Being checked: whether you can hold responsibility without either collapsing or deflecting.

What decides it: choosing a real one. A failure that turned out fine answers nothing, and interviewers know it. Pick something that genuinely went wrong, say what you did, say what you learned, and do not over-apologise. The strongest versions include the part that was your fault.

4. Ambiguity

A time with unclear requirements. Starting something with no precedent. Deciding without enough information.

Being checked: what you do when nobody tells you what to do.

What decides it: describing your actual method. Who you asked, what you assumed, how you reduced the risk of being wrong. "I made a decision and moved on" is not a method.

5. Influence without authority

Getting another team to prioritise your work. Convincing someone senior. Building agreement.

Being checked: whether you can get things done across a boundary — the thing that distinguishes senior people from productive ones.

What decides it: showing you understood what the other side wanted. Most answers describe persuading; good answers describe finding the overlap.

6. Pressure and prioritisation

Too much at once. A tight deadline. Competing priorities.

Being checked: whether you triage or panic.

What decides it: naming what you dropped. Everyone says they prioritised. Few say what they consciously chose not to do, and who they told — which is the part that shows judgement rather than effort.

How to prepare in one hour

Do not write six answers. Write your material and map it.

List eight to ten things you have actually done over the last two or three years. Two lines each. Then, against each of the six categories above, note which of them could serve.

You will find one substantial project covers four or five categories on its own — the migration was ownership, conflict, ambiguity and pressure, depending on which part you lead with. That is normal, and it means you need far less material than you think.

What you are building is not a set of answers. It is the ability to find one quickly when the question is not the one you expected, which is the situation you will actually be in.

The follow-up decides it

Whatever you prepare, the interviewer's second question is the real test: what would you do differently? What did the other person say? What broke?

These are easy if you were there and impossible if you were not. Which is the argument for preparing from things you actually did, in as much detail as you can still remember.

---

The six categories are the map. Rehearse against the role to find which of yours are thin.