The STAR Method, With 6 Worked Examples
STAR (Situation, Task, Action, Result) turns a rambling story into a two-minute answer an interviewer can score. Below are six complete examples for the situations interviewers ask about most, one weak answer rewritten into a strong one, and a worksheet you can fill in tonight.
By NORDON Team
9 min read
Also in Srpski, Hrvatski, Deutsch, Français, Español, Português
What STAR is and why interviewers like it
Behavioral questions start with "Tell me about a time when..." or "Give me an example of...". The interviewer is not after a story for its own sake. They have a scorecard with a competency on it (ownership, collaboration, judgment) and they need evidence. STAR gives them that evidence in the order they want it:
| Part | What it answers | Share of your answer |
|---|---|---|
| Situation | Where were you, and what was going on? | About 10 to 15% |
| Task | What were you responsible for, and what was at stake? | About 10% |
| Action | What did you personally do, step by step? | About 60% |
| Result | What changed, and what did you learn? | About 15 to 20% |
The percentages are a rule of thumb, not a law, but they fix the most common problem: candidates spend a minute on background and twenty seconds on what they did. A full answer should run about 90 seconds to 2 minutes. If the interviewer wants more, they will ask.
A weak answer, rewritten
Question: "Tell me about a time you dealt with a difficult stakeholder." Here is what many candidates say:
"So at my last job we had a lot of difficult stakeholders, it was kind of the culture there. One time the sales director wanted a feature really fast and we said it wasn't possible, and there was some back and forth, but in the end we worked it out and everyone was happy. I think communication is really important in those situations."
What is wrong: no specific moment, "we" throughout, no actions anyone could check, a vague result and a generic moral. Here is the same story with STAR:
Situation: "I was the product analyst on our billing team. Two weeks before the quarter closed, the sales director asked for custom invoicing for one large prospect and wanted it live in five days."
Task: "My job was to scope the request and give a yes or no that both sales and engineering could live with."
Action: "I booked 30 minutes with him the same day and asked what the customer actually needed. It turned out they only needed their PO number on the invoice and a different due date. I checked with engineering: both fields already existed in the system, just not on the template. I wrote a one-page proposal with that small change for this week and the full custom invoicing as a later item, and I walked him through it before sending it to the wider group so he wasn't surprised in public."
Result: "The template change shipped in three days, the deal closed that quarter, and engineering didn't lose a sprint. Since then I always ask 'what does the customer need to see?' before scoping anything that arrives as urgent."
Six worked examples
Each example below is a different competency. They are fictional, but the shape is what interviewers reward. Swap in your own details; never borrow a story you did not live, because the follow-up questions will expose it within a minute.
1. Conflict with a colleague
Situation: "A senior developer and I disagreed on whether to refactor the payment module before adding a new provider. He wanted the refactor first; I was worried about the deadline we had promised the client."
Task: "I was the tech lead on the integration, so the call was mine, but I needed him on board because he knew that code best."
Action: "Instead of arguing in the standup, I asked him to list the three parts of the refactor that blocked the integration. We agreed to do only those, which was about four days, and I put the rest in the backlog with his name and a date. I told the client manager about the four days myself."
Result: "We shipped one week late instead of three, the new provider worked first time in production, and he finished the rest of the refactor the following month. The lesson for me was to split a disagreement into the part that blocks us now and the part that can wait."
2. A failure
Situation: "In my first marketing role I ran a webinar for a product launch."
Task: "I owned registrations, with a target of 300."
Action: "I put almost all of the budget into one paid channel because it had worked for a previous event. Registrations stalled at 90 a week before the date. I told my manager the same day instead of hoping it would pick up, moved the remaining budget to a partner newsletter and asked our sales team to invite their active prospects personally."
Result: "We reached 180, well short of the target. What I changed afterward: I now split any launch budget across at least two channels and check the numbers twice a week, not at the end. On the next launch I hit the target with a week to spare."
3. Leadership without authority
Situation: "Our support team had four different macros for refund requests, and customers were getting conflicting answers."
Task: "I was a regular agent, not a lead, but I had noticed the pattern in my own tickets and wanted it fixed."
Action: "I pulled 40 recent refund tickets and marked where the answers contradicted each other. I took that to our team lead and offered to draft a single macro. I wrote it, asked two senior agents to break it with their trickiest cases, revised it twice and ran a 15-minute walkthrough at the weekly meeting."
Result: "The old macros were retired, and repeat contacts on refunds dropped noticeably over the next month. My lead asked me to own the macro library after that."
4. A tight deadline
Situation: "Our auditor moved the year-end fieldwork forward by ten days."
Task: "As the staff accountant, I had to have the reconciliations for 22 balance sheet accounts ready."
Action: "I ranked the accounts by risk and size and did the top eight first, because those were the ones the auditors would sample. For the rest I built a simple checklist so a colleague could prepare drafts that I reviewed. I flagged two accounts on day one where I knew supporting documents would be slow and chased them early."
Result: "All 22 were ready a day early, and the auditors raised no findings on them. We kept the risk ranking for the next year's close."
5. A customer problem
Situation: "A long-standing client called because a delivery had arrived with the wrong parts for the second time in a month."
Task: "I was their account manager, and they were openly talking about switching suppliers."
Action: "I let him finish, repeated the order numbers back so he knew I had the facts, and said what I could do that day: a replacement shipped overnight at our cost. Then I went to the warehouse lead, found that both orders had been picked from a bin with a mislabeled shelf tag, and got it relabeled. I called the client back the next morning with the cause, not just an apology."
Result: "They stayed and renewed that year. The warehouse added a label check to their weekly routine."
6. A data-driven decision
Situation: "Our mobile app had a new onboarding flow that the team believed was better."
Task: "I was the data analyst asked to confirm it before the full rollout."
Action: "I compared the two flows over three weeks. The new flow had more sign-ups, but when I followed users for seven days, fewer of them made a first purchase. I segmented by traffic source and found the drop came almost entirely from paid social users skipping a step that set their preferences. I presented both numbers side by side and recommended keeping the new flow but restoring that step."
Result: "The team shipped the hybrid. First purchases recovered to the old level while sign-ups stayed higher. I learned to always ask which number we actually care about before I start counting."
Your STAR worksheet
Fill this in for six to eight stories, one per competency. Write in bullets, not full sentences: you want to remember the story, not recite a script.
Story name (2 to 4 words): Competencies it shows: (conflict / failure / leadership / pressure / customer / data / other) SITUATION (1 to 2 sentences) Where, when, my role: What made it hard: TASK (1 sentence) What I was responsible for: What was at stake: ACTION (3 to 5 bullets, all "I") 1. 2. 3. 4. RESULT (1 to 2 sentences) What changed (number, date or concrete outcome): What I learned or do differently now: Likely follow-ups and my short answers: - What would you do differently? - What did the other person say? - How did you measure that?
Mistakes that sink STAR answers
- Hypotheticals. "I would talk to them" answers a different question. The interviewer asked what you did.
- A result with no result. "It went well" tells them nothing. Give a number, a date, a decision that was made, or what the other person did next.
- Five-minute stories. If your Situation needs more than two sentences, cut context the interviewer does not need to judge your actions.
- The same story for everything. Reusing one big project for every question looks thin. Spread your stories across roles and years.
- Polished but empty. Memorized lines sound memorized. Know the bullets and say them in your own words each time.
STAR is the backbone of other common answers too. A good reply to "What is your greatest weakness?" often ends with a short STAR example of how you work on it, see our weakness guide. For a full week of practice built around your story bank, follow the behavioral interview prep plan, and use the behavioral question list to check which competencies you still have no story for.
Rehearse out loud, not in your head
A story that reads well on paper often runs to four minutes when spoken. Time yourself. Record one answer on your phone and listen for "we", for a missing result, and for the moment you lose the thread. In NORDON's Practice mode you answer questions out loud and get a score from 1 to 10 with what worked, what to improve and a stronger version built only from what you said and your own documents, which is a quick way to find the weak part of each story.
Try it in NORDON
Practice your STAR stories out loud
In Practice, NORDON asks questions based on the role and job ad, scores each spoken answer from 1 to 10 and gives you a stronger version to rehearse, using only what you said and your own documents.
Questions
How long should a STAR answer be?
Aim for about 90 seconds to 2 minutes. Most of that time should go to the Action. If you pass three minutes, cut background from the Situation.
How many STAR stories do I need?
Six to eight solid stories cover most behavioral interviews, because one story can show more than one competency. Make sure you have at least one failure and one conflict, since those come up constantly.
What if my result was not a success?
Say so plainly, then explain what you learned and what you do differently now. A clear miss with a real lesson often scores better than a vague success.
Is CAR or SOAR better than STAR?
They are the same idea with different labels. CAR merges Situation and Task; SOAR adds Obstacles. Use whichever helps you remember to give context briefly and spend most of the time on your actions.