Behavioural interview questions: how to answer the 12 that keep coming up

Why these questions exist

Behavioural questions rest on a simple premise: how you handled a situation before predicts how you will handle it again. That premise is imperfect, but it is more reliable than asking what someone would hypothetically do, which mostly tests imagination.

The practical consequence is that hypothetical answers score badly. "I would always make sure to communicate clearly" is worth almost nothing. "Here is when I did not, and what it cost" is worth a great deal.

STAR, done properly

Most candidates know the acronym and still use it badly, usually by spending 80% of the answer on context and running out of time before the result.

• Situation — two sentences maximum. Enough for the interviewer to picture it, no more.
• Task — one sentence. What were you specifically responsible for?
• Action — the bulk of the answer, and it must be in the first person singular. "We" hides your contribution.
• Result — always include one, with a number or a concrete consequence, and where relevant what you learned.

Aim for ninety seconds to two minutes. If the interviewer wants more they will ask, and being asked a follow-up is a good sign.

The twelve questions

1. Tell me about yourself. — Not a biography. Present role, one relevant achievement, why you are here.
2. Why do you want this job? — Something specific about the role or company. Generic enthusiasm is a negative signal.
3. Tell me about a time you failed. — Pick a real failure with a real cost, and spend most of the answer on what changed afterwards.
4. Describe a conflict with a colleague. — Show that you separated the person from the problem. Never disparage anyone.
5. Tell me about a time you had to work to a tight deadline. — Focus on how you decided what to cut.
6. Give an example of when you influenced without authority. — Interviewers love this one; prepare it.
7. Tell me about receiving difficult feedback. — What did you actually change?
8. Describe a time you had to learn something quickly. — Method, not just outcome.
9. Tell me about a decision you made with incomplete information.
10. When have you disagreed with a manager? — Show the disagree-and-commit pattern.
11. What is your greatest weakness? — Something real, plus the mitigation you have built. Not a disguised strength.
12. Where do you see yourself in five years? — Direction, not a title. Show that this role is a plausible step towards it.

Build a story bank, not twelve answers

Trying to prepare a separate answer for every possible question is exhausting and produces rigid, recited responses. Instead prepare six strong stories from your career and practise reframing each one.

A single project where you rescued a slipping deadline can answer questions about pressure, prioritisation, conflict, influence and failure — depending on which part you foreground.

• A project you delivered under real constraint.
• A failure with a measurable cost.
• A conflict you resolved.
• A time you changed someone's mind.
• Something you taught yourself under time pressure.
• A moment you improved how the team works, not just what it produced.

Delivery matters more than people expect

• Practise aloud. Answers that read well silently often collapse when spoken.
• Record yourself once. Painful, effective.
• Pause before answering. Two seconds of thought reads as considered, not slow.
• Ask for clarification if the question is vague — that is assessed positively.
• If you blank, say so and come back to it. Interviewers are far more forgiving of that than of a rambling non-answer.