The STAR method for behavioural interview questions, with examples

Behavioural interview questions ask you to describe what you actually did in a past situation: "Tell me about a time you…". They are common because past behaviour is one of the best clues an interviewer has to how you will behave in the job. The STAR method is a simple way to structure your answers so they are clear, specific and complete.

What is the STAR method?

STAR stands for:

• Situation: the context. Where were you, and what was going on?
• Task: your responsibility or goal in that situation.
• Action: what you did, step by step.
• Result: what happened in the end, and what you learned.

It works because it mirrors how a good story is told, and it makes sure you answer the question the interviewer actually asked: what did you do, and did it work?

How to structure a STAR answer

The parts are not equal. A good balance is roughly:

• Situation and Task: short. Two or three sentences in total. Just enough context for the rest to make sense.
• Action: the longest part. This is what the interviewer is assessing. Describe your specific steps and your reasoning.
• Result: clear and honest. Say what happened. If you can measure it truthfully, do so. Then add a sentence on what you learned.

Aim for about two minutes per answer. Much shorter usually means too little detail in the Action; much longer usually means too much Situation.

Worked example: a conflict question

Question: "Tell me about a time you disagreed with a colleague."

Situation: "In my final-year group project, four of us were building a mobile app, and two weeks before the deadline a teammate wanted to add a new feature."
Task: "I was responsible for the project plan, and I was worried the feature would put the deadline at risk."
Action: "Rather than argue in the group chat, I asked to talk one-to-one. I asked what problem the feature solved, and it turned out to be a real usability issue users had raised in testing. I suggested we solve the same problem with a smaller change that we could finish in two days, and offered to take on some of their other tasks to free up time. We agreed to put the full feature on the 'next version' list."
Result: "We submitted on time with the smaller fix included, and our assessors specifically mentioned the usability testing. What I learned was to ask about the problem behind a request before reacting to the request itself."

Why it works: the context is brief, the actions are specific and clearly the candidate's own, and the result includes a lesson.

Worked example: a failure question

Question: "Tell me about a time you failed."

Situation: "In my first month as a sales assistant, I was asked to run the weekly stock count."
Task: "I needed to finish it before the Monday order was placed."
Action: "I didn't ask how the previous person had done it, and I counted one storeroom twice, so our order was wrong. When my manager spotted the mismatch, I owned up straight away, recounted that evening, and helped correct the order with the supplier the next morning. Then I wrote a one-page checklist for the count and asked my manager to review it."
Result: "The corrected order arrived a day late, which was my fault. But the checklist became the standard for the store, and I haven't made that mistake since. I learned to ask how a task is usually done before I start."

Failure questions test honesty and learning. Choose a real failure with real consequences, take responsibility, and spend most of the answer on what you did about it.

Common behavioural interview questions

Prepare stories that could answer several of these:

• Tell me about a time you led a team or took the initiative.
• Describe a time you had to meet a tight deadline.
• Tell me about a mistake you made and what you learned.
• Give an example of a conflict with a colleague and how you resolved it.
• Tell me about a time you had to learn something quickly.
• Describe a time you went above and beyond for a customer or user.
• Tell me about a time you had to persuade someone.
• Give an example of a time you had to change your plan at short notice.

Common STAR mistakes

• Too much Situation. If the backstory takes a minute, the interviewer stops listening before the important part.
• Hypothetical answers. "I would…" is not an answer to "Tell me about a time…". Use a real example.
• No Result. Many answers just stop after the Action. Always say what happened.
• Inventing or inflating results. Only use numbers you can stand behind; follow-up questions will test them.
• Using the same story for everything. Have a range so you are not repeating yourself across a panel.

How to prepare your STAR stories

1. Make a story bank. Write down five to eight experiences from work, study, volunteering or projects: a success, a failure, a conflict, leading, learning fast, a difficult person, a tight deadline.
2. Draft each one as STAR bullet points. Not a script, just the key beats.
3. Map stories to questions. Most stories can answer two or three different questions with a change of emphasis.
4. Practise out loud. Time each story and cut it to about two minutes. Listen for "we" where you mean "I".
5. Practise against follow-up questions. Real interviewers dig in: "What would you do differently?" or "What exactly did you say?" In an AI mock interview, the interviewer follows up on your answer, and a tougher interviewer like Rachel will push back on vague claims, which is exactly the pressure that shows whether a story holds up.

With a story bank you have practised out loud, behavioural questions stop being something to dread and become a chance to show what you have actually done. Pair it with a strong "Tell me about yourself" and you are well prepared for the most common parts of any interview.