The STAR Method: How to Answer Behavioural Interview Questions

What are behavioural interview questions?

Behavioural questions ask you to describe how you handled a real situation in the past. They usually start with phrases like "Tell me about a time when," "Describe a situation where" or "Give me an example of." The idea behind them is simple: past behaviour is a reasonable predictor of future behaviour, so interviewers want evidence, not opinions.

Common themes include handling conflict, meeting a tight deadline, making a mistake, leading without authority, dealing with an unhappy customer and learning something quickly. Most behavioural questions are a variation on about eight or ten themes, which means you can prepare a handful of stories and reuse them.

What is the STAR method?

STAR is a way to organise a story so it is clear and complete. Each letter is a short step.

• Situation: Set the scene in one or two sentences. Where were you, and what was happening?
• Task: What was your responsibility or goal? What had to be achieved?
• Action: What did you do, step by step? Use "I" rather than "we" so the interviewer can see your contribution.
• Result: What happened? Include numbers if you have them, and mention what you learned.

The most common mistake is spending too long on the situation. Interviewers do not need the whole backstory. Give them just enough context to understand why the action mattered, then spend about half your answer on what you did and what came of it.

What does a good STAR answer look like?

Question: "Tell me about a time you handled a difficult customer."

Situation: "In my last role as a support agent, a customer wrote in three times about a billing error that had not been fixed.
Task: I had taken over the case and needed to resolve it and keep the customer.
Action: I called them instead of emailing, apologised for the repeated delays and walked through exactly what had gone wrong. I then worked with our billing team to correct the charge the same day and sent a written summary so they had it in one place.
Result: The customer thanked me, kept their subscription and later left positive feedback on the interaction. I also wrote a short internal note about the billing issue so the team could spot it earlier."

The answer is concrete, uses "I," and ends with an outcome and a small improvement for the team. It would take about a minute and a half to say aloud.

A second example: meeting a tight deadline

"Our team had two days to prepare a client presentation after the original plan changed. I owned the data section, so I listed what the client actually needed to decide, cut everything else, and built three clear charts instead of a long appendix. I also asked a colleague to review the numbers while I wrote the narrative. We delivered on time, and the client asked to use one of the charts in their own internal meeting."

How do you prepare stories in advance?

You do not need fifty stories. Aim for six to eight strong examples that cover a range of skills, and write each as short bullet points under the four STAR headings.

1. List the main requirements in the job description, such as leadership, problem solving, working with stakeholders or meeting deadlines.
2. Go through your resume and pick the projects or moments that best show those skills.
3. Write the STAR bullets for each story, including one real number or specific outcome where possible.
4. Label each story with the themes it can cover, because one good story often fits several questions.
5. Practise saying them out loud until each one runs under two minutes.

Your resume is a useful starting point. If your bullets already describe outcomes, you have the "Result" part of many stories written. If they only list duties, rewriting them as achievements is worth doing before you interview. The resume mistakes guide explains how to turn tasks into results.

What should you do if you have little experience?

Use any real situation where you showed the skill. University group projects, part-time jobs, volunteering, sports teams and personal projects all work. Say clearly what the context was, and do not exaggerate. Interviewers for entry-level roles expect examples from outside full-time work. What they look for is self-awareness and a clear explanation of what you did.

What should you do when you made a mistake in the story?

Questions about failure or mistakes are common. Choose a real example where the stakes were modest, explain what went wrong without blaming others, describe how you fixed it and say what you now do differently. A short, honest story with a clear lesson is far stronger than a "weakness" that is secretly a strength.

What are the common STAR mistakes?

• Saying "we" all the time. The interviewer is hiring you, so make your own contribution clear.
• Skipping the result. An answer without an outcome feels unfinished. If there is no number, describe the effect.
• Choosing an irrelevant story. Always match the example to the skill in the question.
• Over-rehearsing. Know the outline, but keep the delivery natural.
• Telling a story that makes you look bad and ending there. If the story is about a mistake, finish with what you learned.

Quick STAR checklist

• Situation and task together take no more than about 25 percent of the answer.
• Action uses "I" and describes two or three specific steps.
• Result includes a number, an outcome or a lesson.
• The story matches the skill being asked about.
• The whole answer takes under two minutes.

Once your stories are ready, make sure your resume and your answers support each other. If you want help tightening the document, you can run it through the free ATS checker or start from a clean template in the template library.