The STAR Method for Interviews: How It Works, With Examples and a Template

The STAR method is a way to structure answers to interview questions about past experience. STAR stands for Situation, Task, Action, Result. Instead of rambling through a story, you set the scene briefly, say what you were responsible for, spend most of the time on what you did, and finish with the outcome. Interviewers at many companies are trained to listen for these four parts, so using them makes your answer easier to score.

The four parts

The most common mistake is spending too long on the situation. The interviewer doesn't need the full history of the project; they need enough context to understand your actions.

When to use STAR

Use it whenever a question asks about a real past event. These usually start with:

• "Tell me about a time…"
• "Describe a situation where…"
• "Give me an example of…"
• "Have you ever…"
• "What did you do when…"

You'll hear these in behavioral interviews, in competency-based interviews used by many public-sector employers, and in structured formats such as Amazon's leadership principles interviews. For a list of common questions, see our behavioral vs traditional interview questions guide.

STAR is less useful for factual questions ("What's your notice period?") or opinions ("What do you think of our product?").

A fill-in template

Situation: At [company or school], [what was going on, in one sentence]. Task: I was responsible for [your goal or duty]. Action: First I [step one]. Then I [step two]. I also [step three, often how you worked with others]. Result: As a result, [outcome, with a number if possible]. I learned [one lesson], and since then I [what you do differently].

Write your stories in this shape first, then practice saying them in a natural way. The template is a skeleton, not a script.

Five full examples

"Tell me about a time you solved a difficult problem."

Situation: Our online store's checkout was failing for some customers, and support tickets had doubled in a week. Task: I was the developer on call, so it was my job to find the cause. Action: I pulled the error logs and saw that all the failures came from one payment method. I reproduced it in our test environment, found that a recent update had changed a currency field format, and wrote a fix with a test so it couldn't happen again. I also posted an update in the support channel every two hours. Result: The fix went live the next morning and failures dropped to zero. Tickets returned to normal within three days. We added that test to our standard checklist.

"Describe a time you had a conflict with a colleague."

Situation: A designer and I disagreed about whether to remove a form field that sales relied on. Task: I was the product owner and needed a decision before the release. Action: I asked each of them for the data behind their view, found that only 4% of leads filled in the field, and suggested moving it to a later step instead of deleting it. I set up a short meeting where both could see the numbers. Result: Both agreed to the change. Form completion went up, and sales still got the information for the leads that mattered.

"Tell me about a time you failed."

Situation: I planned a client workshop and underestimated how long the setup would take. Task: I was responsible for the agenda and materials. Action: When we started 30 minutes late, I told the client directly, cut one section, and sent the missing material afterward with a short video. Result: The client was satisfied, but it wasn't my best work. Now I do a full rehearsal of setup the day before every workshop, and I haven't started late since.

"Give an example of when you showed leadership."

Situation: Our team's manager left suddenly in the middle of a busy quarter. Task: I wasn't the most senior, but I volunteered to coordinate until a replacement was hired. Action: I set up a 15-minute daily check-in, made a shared list of who owned what, and took the escalations to the director once a week. Result: We hit all three of our quarterly deadlines. When the new manager arrived, she kept the daily check-in.

"Tell me about a time you worked under pressure."

Situation: Two days before a grant deadline, a co-author withdrew from our application. Task: I had to rewrite her section and still submit on time. Action: I listed what the funder required for that section, reused our existing data, asked a colleague to review it overnight, and moved my other tasks to the following week after telling my manager. Result: We submitted six hours before the deadline, and the grant was approved.

Variations of STAR

They all follow the same idea: brief context, clear actions, real outcome.

Mistakes that weaken a STAR answer

• Too much setting. If you're still on the situation after 30 seconds, skip ahead.
• "We" instead of "I". The interviewer needs to know what you did.
• Vague actions. "I handled it" says nothing. Name the steps.
• No result. Always finish, even if the result was mixed.
• Sounding memorized. Practice until you know the points, then say it in your own words.
• The same story for everything. Prepare six to eight stories so you can choose the best fit.

Using STAR on a resume

On a resume, STAR shrinks into one line: an action verb, what you did, and the result. The situation and task are usually implied by the job title.

• "Rebuilt the onboarding checklist, cutting new-hire setup time from five days to two."
• "Led weekly vendor calls for a 1,200-person payroll migration completed with no missed pay runs."
• "Created a shared FAQ for the support team, reducing repeat tickets by about a fifth."

Keep the numbers honest. If you don't know the exact figure, use a range you can explain.

How to prepare your STAR stories

1. List the skills the job post asks for.
2. For each skill, write down a real example from work, school or volunteering.
3. Fill in the template above for six to eight of them.
4. Practice aloud and time each one; aim for under two minutes.
5. Check that each story has a clear "I did" and a result.

If you want help drafting stories from your own experience, our guide to the STAR interview answer generator shows how to turn rough notes into structured answers without sounding scripted. Many "what would you do" questions can also be answered with a past example; see situational interview questions.

Practice in your own words and review a recording or transcript to check your timing. Follow the employer's rules on AI tools in any live interview or assessment.