The STAR Method: How to Answer Behavioural Interview Questions
· 5 min read
"Tell me about a time when you disagreed with a colleague." "Describe a situation where you had to meet a tight deadline." "Give me an example of a mistake you made." These are behavioural interview questions, and they appear in almost every interview, from graduate schemes to senior leadership roles.
They exist because past behaviour is one of the better predictors of future behaviour. Anyone can say they work well under pressure. A behavioural question asks you to prove it with a real example. The STAR method is the simplest way to structure that proof so it is clear, specific and memorable.
What STAR stands for
Situation: the context. Where were you, what was happening?
Task: your responsibility. What needed to be done, and why did it fall to you?
Action: what you did, step by step.
Result: what happened as a result, ideally with a number, and what you learned.
The proportions matter. Situation and Task together should take about 20% of your answer. Action should take most of it, around 60%, because that is what the interviewer is assessing. Result takes the final 20%. Many candidates spend a minute describing the background and rush the part that actually shows their ability.
A full example
Question: "Tell me about a time you had to deal with a difficult customer."
Situation: In my last role at a software company, one of our largest clients threatened to cancel after three failed updates in a month.
Task: As their account manager, I needed to keep the contract and rebuild trust before their renewal in six weeks.
Action: I called the client's operations director the same day, listened without defending us, and wrote down every problem they raised. I then met our engineering lead to agree a fix date for each one, and sent the client a written plan with named owners. For the next six weeks I sent a short update every Friday, even when there was nothing new, and invited their team to test each fix before release.
Result: All the issues were fixed within five weeks, the client renewed for two years and later expanded their contract by 20%. I now use the same weekly-update approach with any account that has a serious problem.
Notice the details: a specific situation, a clear personal responsibility, concrete actions in order, a measurable result and a lesson. That is what makes an answer credible.
Build a story bank before the interview
You cannot predict every question, but you can prepare six to eight stories that between them cover most of what interviewers ask. Choose examples that show:
A significant achievement you are proud of
Working under pressure or to a tight deadline
A conflict or disagreement you resolved
A mistake or failure and what you learned
Leading or influencing others without formal authority
Solving a difficult problem or improving a process
Handling a difficult customer, client or stakeholder
Adapting to a big change
Each story can often answer several questions. A project that ran late might illustrate pressure, problem solving and communication, depending on which part you emphasise.
Write each story down in STAR form using bullet points, not a script. Practise saying them aloud until each takes about two minutes. Memorising word for word makes you sound robotic; knowing the structure lets you sound natural.
Use the job description to choose your stories
Read the advert and list the competencies it emphasises: stakeholder management, attention to detail, leadership, analytical thinking. Interviewers often build their questions directly from that list. Make sure you have at least one strong story for each competency, drawn from your most recent and relevant experience.
Common questions and what they are really testing
"Tell me about a time you failed." Self-awareness and learning. Choose a real failure with modest consequences, own it, and spend most of the answer on what you changed afterwards.
"Describe a conflict with a colleague." Maturity and communication. Show that you sought to understand the other person, focused on the shared goal and reached a workable outcome. Never make the other person the villain.
"Give an example of leadership." Influence, not just job titles. Leading a project, mentoring a new starter or persuading a team to change a process all count.
"Tell me about a time you had too much to do." Prioritisation. Explain how you decided what mattered most, what you delegated or renegotiated, and what you would do differently.
"Describe a time you had to learn something quickly." Adaptability. Show your method: who you asked, what you read, how you tested your understanding.
Mistakes that weaken STAR answers
"We" instead of "I". Teamwork matters, but the interviewer is hiring you. Say what you personally did: "I proposed", "I analysed", "I called".
Hypothetical answers. "I would…" is not an example. If you truly have no direct example, say so and use the closest real situation you have.
No result. Ending with the action leaves the interviewer wondering whether it worked. Always finish with the outcome.
Too long. Answers over three minutes lose focus. If the interviewer wants more detail, they will ask.
Old or irrelevant examples. Prefer stories from the last few years, from work that resembles the role you want.
What if the result was not good?
Not every story needs a happy ending. For failure questions especially, a poor outcome is expected. Be honest about it and put the weight on the learning: "We missed the launch date by two weeks. Since then I build a two-week buffer into every plan and flag risks to stakeholders in the first week rather than the last." Interviewers value candidates who can reflect on what went wrong.
Variations: CAR and STARL
You may hear of other versions. CAR (Context, Action, Result) is simply a shorter STAR. STARL adds L for Learning at the end. The idea is the same: give context briefly, focus on your actions and close with the outcome. Use whichever helps you remember, and always include what you learned when the question invites it.
Practising effectively
Write down ten behavioural questions likely for the role.
Match each to a story from your bank.
Record yourself answering on your phone and listen back. Check the balance of Situation versus Action and whether you said "I".
Practise with a friend who interrupts with follow-up questions such as "Why did you choose that approach?" Real interviewers often probe.
The bottom line
Behavioural questions reward preparation more than any other part of an interview. With six to eight well-rehearsed STAR stories, you can answer most questions calmly and with evidence. Keep the background short, make your own actions the centre of every answer and always finish with a result. That structure turns "I'm good at this" into "here is what I did, and here is what happened".