STAR method examples: six worked answers

These six STAR method examples answer common behavioral questions: a failure, a conflict with a coworker, a tight deadline, a customer problem, leading without authority and a decision with incomplete data.

By Updated 7 min read

Six paper cards, one yellow and five cream, each with four black bars, the third bar the longest.

How to read these STAR examples

Each follows the STAR interview method, plus STARI’s Improvement, and is shorter than a spoken answer:

  • Situation and task: a sentence or two each.
  • Action: most of the answer, as decisions with reasons.
  • Result: what changed, including what didn’t work.
  • Improvement: what the candidate changed afterwards.

Borrow the shape, not the words: follow-up questions ask for details only your own story has.

STAR example: a time you failed

Fictional example: “Tell me about a time you failed.”
Situation
I owned an online furniture store’s weekly sale email.
Task
For a spring sale, each customer group needed the right discount code.
Action
I skipped my usual test send to save time, and one group’s code didn’t work. I told my manager it was my mistake before anyone asked, and paused the other sends, so no other group got a broken code. I sent that group an apology with a working code and checked every list before sending again.
Result
Some customers gave up before the fix, and that group’s sales fell short of plan.
Improvement
I made the test send a written step, and a colleague now checks the lists.

Written for this guide. The company, people and figures are invented.

What the interviewer hears: the candidate’s own mistake, raised before anyone asked, and an honest cost. Earn Trust asks leaders to be “vocally self-critical, even when doing so is awkward or embarrassing” (Amazon Leadership Principles).

Where it goes wrong: a success in disguise, or someone else’s failure. Read how to answer “Tell me about a time you failed”, or start a focused session on Earn Trust.

STAR example: a conflict with a coworker

Fictional example: “Tell me about a time you had a conflict with a coworker.”
Situation
I was a data engineer sharing a monthly revenue report with a finance analyst.
Task
I owned its pipeline. She wanted a new data source added, which I thought would make the numbers less reliable.
Action
Instead of arguing in the team channel, I asked her for half an hour, one to one. She explained that the report missed refunds, so finance fixed it by hand each month. I hadn’t known that. We agreed to add only the refund data, with a check that flagged days where the sources disagreed, so neither side had to trust the other’s data.
Result
The next report included refunds, and the hand fixes stopped.
Improvement
Now I ask what a request is for before I answer it.

Written for this guide. The company, people and figures are invented.

What the interviewer hears: the coworker’s view, stated fairly, and a candidate who changed position because of it. Earn Trust describes leaders who “listen attentively, speak candidly, and treat others respectfully” (Amazon Leadership Principles).

Where it goes wrong: a villain, or an ending where you simply won. Read how to answer “Tell me about a conflict with a coworker”, or start a focused session on Earn Trust.

STAR example: a tight deadline

Fictional example: “Tell me about a time you had to meet a tight deadline.”
Situation
I coordinated trade show booths. Two weeks before a show, our printer said a client’s banners would be late.
Task
I was responsible for getting the whole booth there by setup day.
Action
I checked every part; only the banners were at risk, so I put my time there. Another printer could meet the date with a simpler material. Before agreeing, I sent the client photos of both and explained the trade-off, so it wouldn’t surprise them at the show. They approved it, and I moved delivery a day earlier in case anything slipped.
Result
Everything arrived on time, and the booth ran for the whole show.
Improvement
Now I line up a backup printer when the order goes in.

Written for this guide. The company, people and figures are invented.

What the interviewer hears: the one real risk found, and a trade-off shared before it became a surprise. Deliver Results says: “Leaders focus on the key inputs for their business and deliver them with the right quality and in a timely fashion” (Amazon Leadership Principles).

Where it goes wrong: long hours as the whole story. The interviewer is listening for the decisions that saved the date. To practice, start a focused session on Deliver Results.

STAR example: a customer problem

Fictional example: “Tell me about a time you solved a problem for a customer.”
Situation
I was an account manager for clinic scheduling software. A long-time customer said they might leave because patients kept missing appointments.
Task
I wanted to find out why, not just save the renewal.
Action
Instead of reading their tickets, I sat with the front desk for a morning, to see the problem as patients met it. Our reminder texts went out at one time for every patient, often mid-workday. I wrote up what I’d seen and asked the product team to bring forward a planned reminder-time setting. Meanwhile the clinic and I split reminders into two daily batches.
Result
Missed appointments fell, the clinic renewed, and a basic setting shipped that quarter.
Improvement
Now I see a customer’s process myself before I suggest a fix.

Written for this guide. The company, people and figures are invented.

What the interviewer hears: a candidate who works back from what patients experienced, not from what the product already did. Customer Obsession says leaders “start with the customer and work backwards” (Amazon Leadership Principles).

Where it goes wrong: the customer simply got a refund, which shows little about finding the problem. To practice, start a focused session on Customer Obsession.

STAR example: leading without authority

Fictional example: “Tell me about a time you led without formal authority.”
Situation
I was a quality analyst at a warehouse whose returns area kept filling up. Each shift lead blamed another shift.
Task
Returns weren’t my job, and no lead reported to me, but I offered to find the cause.
Action
I tracked returns for two weeks and shared the results with all three leads at once, so nobody felt singled out. Items waited for an inspection only day staff could do. I proposed training one person per shift and wrote a one-page guide. One lead worried about losing a picker, so I scheduled training in that shift’s quietest hours to keep picking on track.
Result
Within a month the returns area stayed clear on every shift.
Improvement
Now I bring a proposed next step along with the data.

Written for this guide. The company, people and figures are invented.

What the interviewer hears: someone else’s problem taken on, and the blocking objection answered. Ownership describes leaders who “act on behalf of the entire company, beyond just their own team” (Amazon Leadership Principles).

Where it goes wrong: “we” throughout, or a manager giving the orders. Read how to answer leadership questions when you don’t manage anyone, or start a focused session on Ownership.

STAR example: a decision with incomplete data

Fictional example: “Tell me about a time you made a decision with incomplete data.”
Situation
I was a meal-kit app’s product manager when a supplier said a popular ingredient would be out for an unknown time.
Task
I had a day to decide what went into the next week’s boxes.
Action
I knew which orders were affected, but not how long the shortage would last or which substitute customers would accept. Waiting meant missing the packing deadline, while a menu change could be undone the next week, so I decided to act. I used a substitute the chefs had already tested, to keep the risk small, marked it on each recipe and let customers switch recipes for free.
Result
Boxes shipped on time, and customer comments showed which substitute to keep.
Improvement
I told support late; now I tell them before any change customers will notice.

Written for this guide. The company, people and figures are invented.

What the interviewer hears: what the candidate knew and didn’t, and why waiting cost more than deciding. Bias for Action notes: “Many decisions and actions are reversible and do not need extensive study” (Amazon Leadership Principles).

Where it goes wrong: a bold decision with no reasoning. Say what you didn’t know and how you limited the risk. To practice, start a focused session on Bias for Action.

Practice your own STAR answers with follow-ups

Examples show the shape; telling your own story aloud shows where it’s thin. In MockRun you answer one question out loud or by typing, with one follow-up at a time. The debrief sorts your answer into STARI parts, quotes your words and names one detail to explain next.

MockRun’s debrief notes on how to make the story clearer: Situation and Task, each marked Explained, with the quoted words from the answer that support them.
A fictional practice example. Each STARI note quotes the words from the answer that support it. Open the full-size example

To choose which stories to tell, read how to prepare behavioral interview stories. For what may come next, see behavioral interview follow-up questions.

Common questions

Can I memorize one of these STAR examples?

Use them for the shape, not the words. They are written for this guide, and the roles and figures are invented. Tell a true story of your own, because follow-up questions ask for details only the real one has.

Can one STAR story answer more than one question?

Often, yes. A story about a tight deadline may also show how you treated a customer or handled a disagreement. Tell it from the angle the question asks about, and spend the most time on that part. In one interview loop, use different stories with different interviewers where you can.

Got a job post? See your practice plan