STAR Method Examples With Annotated Breakdowns

STAR stands for Situation, Task, Action and Result. It is a way to organise an answer about something you actually did. This guide breaks down fictional examples part by part and shows how to describe your real contribution, including when your role was partial, when the result was unclear and when you do not know how it ended.

The practice suggestions here are optional, so adapt them to the question and to any limit or instruction the interviewer gives. Honesty, confidentiality and permission are not optional. All examples are invented. Do not copy them, and do not borrow any of their details as claims about your own experience.

What each part is for

• Situation: the context. Give only what the listener needs to follow the rest.
• Task: what you were responsible for or trying to do, which may be only a small part of a larger piece of work.
• Action: what you personally did, in the order you did it.
• Result: what happened. It can be measurable, qualitative, partial, unresolved or unknown.

This guide sets no required number of sentences or minutes, but follow any limit or instruction the interviewer gives. As a suggestion, you might spend more words on the Action than on the background, because the Action shows what you did.

When STAR fits

STAR fits questions that ask about a real past event, such as "Tell me about a time you..." If a question asks what you would do in an imagined scenario, you are being asked to reason, not to recall. Our guide to situational interview questions covers that.

Annotated fictional examples

Fictional example, a team role that was only part of the work:

• Situation: "A small team was preparing a presentation, and two members disagreed about how to structure it."
• Task: "I wasn't the leader. My part was to collect the slides and keep the shared draft up to date."
• Action: "I listed each person's concern in the shared draft, grouped the points that overlapped and asked the team which structure they wanted to try first."
• Result: "The team chose one structure and we presented. I don't know whether another structure would have worked better, and I wasn't the one who made the final choice."

What to notice: the speaker says plainly that they were not the leader and who made the decision. The result is qualitative, and the speaker admits what they do not know. Nothing about the example needs a title or a figure to be useful.

Fictional example, helping with part of a problem:

• Situation: "A customer-reporting spreadsheet kept showing totals that didn't match."
• Task: "I was asked to check one section of it."
• Action: "I compared my section with the source records, found two entries that had been typed twice and told the person who owned the spreadsheet."
• Result: "They corrected the entries. I don't know whether the other sections had similar problems."

What to notice: the speaker describes checking one section, not fixing the whole spreadsheet. Do not turn "helped" or "checked" into "led" or "solved". Use the verb that matches what you did.

Fictional example, a mistake:

• Situation: "I was preparing a weekly summary for my team."
• Task: "I was responsible for the figures in my section."
• Action: "I realised I had used the previous week's file. I told my supervisor as soon as I noticed and sent a corrected version."
• Result: "The summary was corrected. After that I checked the file date before I started each week."

What to notice: the answer owns the mistake without blaming anyone. Only describe a change if you actually made it, and do not claim that it "prevented" anything unless you know that.

Describe your real part

Partial and team roles are valid. Before you answer, ask yourself:

• What did I do myself?
• What did other people do?
• Who made the decisions, and who approved them?

You can say "I" for what you did and "we" for what the team did. Both can be accurate. Choose verbs that match your role, such as supported, drafted, checked, proposed, organised or led, and use "led" only if you led.

Results

A result does not have to be a number. You can describe what changed, what the reaction was, what was left unfinished, or that you do not know the outcome. Use a figure only if you know it and can explain where it came from. Do not estimate a number to fill a gap. If there was no measurable result, you can say what you learned or what you would check next.

Build your answers from real events

Keep a short list of real events from work, study, volunteering or other experience. Under each, note the situation, the task, what you did, what happened and anything you do not know. One event can suit more than one question, but keep the facts the same each time.

Do not combine actions from different events into one story, and do not add a step you did not take to make an answer feel complete. If an event is missing a piece, say what you do not know, or choose a different event. If an example involves other people, leave out names and anything confidential.

Follow-up questions

You may be asked more about the same event, for example what you would do differently, how others reacted or what was hardest. Answer from what happened. If you do not remember, say so instead of inventing a reaction. If you would do something differently, you can say what and why. Our guide on what to do when you don't know an answer covers questions you cannot answer fully.

Practice

Say an example aloud, and record yourself if you wish. If you practice with another person, agree with them before recording. For a routine you can repeat, see our guide to behavioural interview practice.

In a real interview, do not use any tool to generate answers unless the organiser has explicitly allowed it, and do not record the conversation unless the interviewer has agreed.

This guide is published by Muqabala. You can visit our interview practice page for your next practice session. Use any method that suits you, and check how any tool handles your data first. Do not paste confidential employer, client or personal information into a practice tool.