The STAR method interview technique is a way to answer "Tell me about a time when..." questions in four parts: the Situation, your Task, the Action you took, and the Result. Spend most of your answer on the action, keep the setup short, and end with a concrete outcome. Below are 10 complete sample answers for different jobs, a fill-in worksheet, and the mistakes that make STAR answers sound rehearsed.
This page is the answer library. If you are still figuring out what behavioral interviews test, how to pick competencies from a job posting, or how to build a story bank, start with our guide on how to prepare for a behavioral interview, then come back here to draft and pressure-test your answers.
STAR at a glance
The University of Washington Career & Internship Center suggests rough proportions for each part. Treat them as a guide, not a stopwatch.
| Part | What to say | Share of the answer | Common slip |
|---|---|---|---|
| Situation | Where you were, when, and what was going on, in one or two sentences | About 20% | Explaining the whole company history |
| Task | What you were responsible for or what had to change | About 10% | Merging it into the situation so your role is unclear |
| Action | The specific steps you took, in order, using "I" | About 60% | Saying "we" throughout, so the interviewer cannot tell what you did |
| Result | What happened, with a number or a visible change if you have one, and what you learned | About 10% | Stopping at the action, or claiming a result you cannot back up |
As a working target, aim for about one to two minutes per spoken answer, the range Strayer University's career center suggests. The U.S. Office of Personnel Management describes highly structured interviews that use a set lead question plus planned probes, and scores answers against benchmarks, so expect "What did you do next?" or "What would you change?" after your first answer.
10 STAR example answers across different jobs
These are clearly labeled samples. The names, numbers and details are invented to show the structure. Use them as patterns, never as scripts: an interviewer can tell when a story is not yours, and follow-up questions will expose it.
1. Entry-level or recent graduate: "Tell me about a time you worked with a difficult teammate."
Situation: In my final semester, I was one of four students on a market research project worth 30% of our grade, and one teammate had missed our first two meetings.
Task: I had volunteered to coordinate, so it was my job to get the project back on schedule without doing his share myself.
Action: I messaged him privately instead of in the group chat and asked what was getting in the way. He was working extra shifts. I offered him the survey analysis, which he could do on his own schedule, and moved our check-ins to a shared document with a dated task list so nobody needed to attend live meetings to stay current.
Result: He delivered his section two days before the deadline, and we earned an A-. I still use a written task list whenever a group has mismatched schedules.
2. Retail associate: "Describe a time you handled an upset customer."
Situation: During a holiday weekend, a customer came to my register angry because a gift she bought had a missing part and she had no receipt.
Task: Our policy allowed store credit without a receipt only with a manager override, and the line behind her was long.
Action: I apologized for the hassle, called a second cashier to take my line, and moved with her to the end of the counter. I looked up the item by its barcode to confirm we sold it, checked the shelf for an identical box, and asked my manager for the override with the facts already gathered so it took one minute instead of ten.
Result: She left with a complete replacement and thanked my manager on the way out. My manager later asked me to show two newer cashiers how I set up overrides.
3. Registered nurse: "Tell me about a time you caught an error."
Situation: On a med-surg night shift, I was reviewing new orders for a post-operative patient and saw two active orders for pain medication from different providers.
Task: I needed to make sure the patient was not double-dosed while still keeping their pain controlled.
Action: I held the second dose, checked the medication administration record to confirm what had been given, and paged the on-call provider with a short summary: the two orders, the last dose time, and the patient's current pain score. I documented the clarification and reported it through our unit's safety reporting system so the order set could be reviewed.
Result: The provider discontinued the duplicate order within 20 minutes, and the patient's pain stayed managed. The unit educator later used the case in a huddle about order reconciliation.
4. Registered nurse: "Describe a time you had to communicate bad news or difficult information."
Situation: A patient's adult daughter was frustrated that her father's discharge had been delayed a second day.
Task: I had to explain the delay honestly, within what I was allowed to share, and keep her trust in the care team.
Action: I confirmed her father had listed her as someone we could share information with, then sat down with her instead of talking in the doorway. I explained that his lab results needed to be rechecked before it was safe to go home, told her when the results were expected, and arranged for the physician to call her that afternoon.
Result: She said she felt informed rather than brushed off, and the discharge went smoothly the next morning.
5. Software engineer: "Tell me about a time something you built failed."
Situation: A caching change I shipped caused some users to see other users' stale dashboard data for about 15 minutes after a deploy.
Task: As the author, I owned the fix and the explanation to the team.
Action: I rolled back the change first, then confirmed in the logs that no personal data had been exposed, only aggregate counts. I wrote a test that reproduced the cache key collision, fixed the key to include the account ID, and wrote a short incident note covering what happened, the impact, and the new test.
Result: The fix shipped the next day with no repeat. The team added cache key review to our pull request checklist, which I drafted.
6. Software engineer: "Describe a time you disagreed with a technical decision."
Situation: Our team planned to build an internal search feature from scratch. I thought an existing open-source library would be faster and safer.
Task: I wanted the team to make the decision with evidence, not just my opinion.
Action: I asked my lead for two days to build a small prototype with the library and listed the trade-offs in a one-page comparison: build time, maintenance, licensing and performance on our largest data set. I presented both options at planning and said I would support whichever we chose.
Result: We adopted the library, and the feature shipped about three weeks earlier than the original estimate.
7. Manager: "Tell me about a time you managed an underperforming employee."
Situation: A team member who had been reliable for two years started missing deadlines, and two clients had noticed.
Task: I needed to protect the client work and find out what had changed before deciding on next steps.
Action: I met with him privately, described the specific missed dates without labels, and asked what was going on. He was struggling with a new reporting tool. I paired him with a colleague for two weeks, set weekly check-ins with clear deliverables, and temporarily moved one client to another account lead. I put the plan in writing.
Result: Within six weeks he was meeting deadlines again and took the client back. If the plan had not worked, the documentation would have supported a fair next step with HR.
8. Manager: "Describe a time you led a team through a change."
Situation: Our clinic's front desk moved from paper intake to a tablet check-in system, and several staff were worried about slowing down the morning rush.
Task: I was responsible for rollout and keeping wait times stable.
Action: I asked the two most skeptical staff members to test the system first and list problems. We fixed the three biggest issues with the vendor before launch, ran the new and old processes side by side for one week, and posted a one-page cheat sheet at each station.
Result: Average check-in time dropped within the first month by our own front-desk logs, and the two testers became the go-to trainers for new hires.
9. Career changer, teacher to project coordinator: "Tell me about a time you managed several deadlines at once."
Situation: As a seventh-grade teacher, I was asked to coordinate our school's science fair while teaching a full schedule.
Task: I had 140 student projects, 12 volunteer judges and a fixed date in six weeks.
Action: I built a shared spreadsheet with every deadline, owner and status, sent families a weekly two-line update, and set two internal checkpoints for project proposals and drafts. When five judges cancelled the week before, I recruited replacements from a local engineering firm through a parent contact.
Result: All 140 projects were judged on schedule. That spreadsheet is the same tracking approach I would use for project timelines in this role.
Notice the last sentence. Career changers should translate the result into the new job's language. Our guide to turning transferable skills into a career change shows how to do that across a whole application.
10. Any level: "Tell me about a mistake you made."
Situation: In my first month as an administrative assistant, I sent a meeting invitation for a client review to the wrong client contact.
Task: I had to fix it quickly and make sure it did not happen again.
Action: I told my manager within minutes rather than hoping nobody noticed, sent a short correction to the contact, and reissued the invitation to the right person. Then I started checking the recipient field against the client file before sending anything external.
Result: The contact replied that it was no problem, and I have not repeated the error. For mistake questions, the result is often what you changed, not a win.
STAR answer worksheet
Copy this into a document and fill in one row per story. Five to eight stories that cover different skills will handle most behavioral interviews. The free interview story workbench does the same thing in your browser if you prefer.
| Prompt | Your notes |
|---|---|
| Question or skill this answers (from the job posting) | |
| Situation: where, when, what was at stake (1 to 2 sentences) | |
| Task: what you specifically owned | |
| Action 1, 2, 3: verbs you did yourself, in order | |
| Result: number, date, or visible change you can prove | |
| What you learned or would do differently | |
| Likely follow-up question and your short answer | |
| Other questions this story can answer |
The last row saves work: one error-catching story can also cover attention to detail and speaking up.
STAR vs. CAR vs. SOAR
Career centers teach several versions of the same idea. None is "correct"; pick the one that keeps you focused on your own actions.
| Method | Stands for | Best for |
|---|---|---|
| STAR | Situation, Task, Action, Result | Most behavioral questions, especially when your role in a group needs explaining |
| CAR | Challenge, Action, Result (as taught by the University of Wisconsin-Superior career office) | Short answers, networking conversations and resume bullet points |
| SOAR | Situation, Obstacle, Action, Result (University of Oregon College of Design) | Stories where the obstacle is the interesting part, such as a blocked project |
| CARD | Challenge, Action, Result, Details (Strayer University Career Center) | Reminding yourself to add how many, how much, how long or how often |
In practice, CAR is STAR with the situation and task combined. If your setup tends to run long, CAR is a useful discipline.
Mistakes that weaken STAR answers, and fixes
- The team did everything. Fix: keep "we" for context and switch to "I" for every action step. The University of Oregon guidance makes the same point.
- No result. Fix: if you lack a number, name a visible change, such as a process adopted, a deadline met or feedback received.
- Inflated results. Fix: use only figures you could explain if asked how you measured them.
- The same story for every question. Fix: map each story to two or three skills, then use different stories in one interview.
- A hypothetical answer to a behavioral question. Fix: if asked "Tell me about a time," give a real example. If you truly have none, say so briefly, describe the closest experience, and explain what you would do.
- Memorized wording. Fix: memorize the four headline facts of each story, not the sentences.
When STAR is not the right tool
OPM distinguishes behavioral questions, which ask what you did, from situational questions, which ask what you would do. For "What would you do if..." questions, describe your approach step by step, then add one sentence of evidence: "I handled something similar last year, when..." For quick factual questions about schedules, certifications or salary, skip the story and answer directly. Our list of common interview questions and answers shows which questions call for a story.
Practice in three passes
- Write it. Fill the worksheet for five stories in bullet points, not paragraphs.
- Say it out loud and time it. If you pass two and a half minutes, cut the situation first.
- Get interrupted. Ask a friend to stop you after the action and ask "Why did you choose that?"
A strong STAR answer does not guarantee an offer. It makes your experience easier to evaluate, which is the part you control.