The STAR Method for Behavioural Interviews

Every behavioural interview question rests on one assumption: past behaviour is the best predictor of future behaviour. That is why you are asked for a real memory rather than a theory:

• "Tell me about a time you handled a conflict."
• "Describe a situation where you had to decide under pressure."
• "Tell me about a project that failed."

The people who lose points here are not the ones without stories. They are the ones who cannot structure them.

What STAR stands for

A four-step narrative skeleton:

• S — Situation: the context. Where, when, under what conditions?
• T — Task: your responsibility. The critical word is your.
• A — Action: what you did, step by step, in the first person.
• R — Result: what changed, with a number where possible.

A good balance: Situation 15%, Task 15%, Action 50%, Result 20%. Most candidates invert this — five minutes of context, then a single sentence for the outcome.

A worked example

Question: "Tell me about a time you managed a disagreement within a team."

Weak answer:

Disagreements happen in every team. I usually keep communication open and listen to people, and we normally find common ground.

There is no situation, no action and no result here. That is an opinion, not a story.

Strong answer:

(S) Last year, while we were rolling out a new order system, the sales and operations teams could not agree on the delivery commitment we would publish. The project was already two weeks late.

(T) As project coordinator, it was my responsibility to get both teams to a single agreed commitment table.

(A) I first ran separate thirty-minute conversations with each side and found that the real objection was not the timeline but who would own the risk. I pulled the actual delivery data from the previous three months and designed a joint session where we would argue from data rather than assumptions. In that session I presented three scenarios and mapped, openly, which risk each one left with which team.

(R) They agreed on the second scenario, the system went live within nine days, and delivery-commitment compliance rose from 71% to 94% in the following quarter.

Same event, same person. The entire difference is structure.

Build a story bank before the interview

Memorising a separate story for every possible question is impossible and unnecessary. Prepare six to eight strong stories instead; most behavioural questions can be answered from that pool.

Cover these themes:

1. A measurable success
2. A failure and what changed afterwards
3. Conflict, or working with a difficult person
4. A fast decision under pressure
5. Leadership or taking initiative
6. Persuading someone without authority
7. Improving a process
8. Handling ambiguity

Write each on one page in STAR format, and break the Action section into at least five steps. You will not narrate all of them — but having written them keeps you from drifting when you improvise.

Getting the failure question right

There are three traps in "Tell me about a failure":

• Humble bragging: "I am too much of a perfectionist." Not credible.
• Blaming outward: "The team did not support me." The worst possible signal.
• Choosing something trivial: it suggests you cannot see risk.

The right shape: a real event with a real consequence, where you owned your part and can show what you changed afterwards. End the Result section with a behaviour change, not a lesson.

Frequent mistakes

• Saying "we". Even in teamwork, the actions should be yours: not "we did it as a team" but "my part in the team was this."
• Skipping the result. If you have no number, give a qualitative outcome: client feedback, whether the process stuck, what changed in the team.
• Using stories that are too old. Prefer the last two to three years.
• Talking in one breath. Leave micro-pauses so the interviewer can step in.
• Over-explaining context. Two sentences set the scene; the company history is not needed.

How to rehearse

Say each story out loud and time it: 90 to 120 seconds. Then reframe the same story as an answer to a different question. The order-system example above works for "conflict management", "persuading with data" and "taking initiative" alike.

In short

A behavioural interview is a test of narration, not memory. STAR puts your experience into an order the listener can follow; a story bank stops you from thinking from scratch under pressure. With both in place, the interview stops feeling like an exam and starts feeling like a conversation.

If you would like to build your own story bank and rehearse it live, that is what a mock interview session is for.