STAR Method Answers: 20 Examples by Role and Question

The STAR method is a way to answer a behavioural interview question as a short story in four parts: the Situation, the Task you were responsible for, the Action you took and the Result. Spend most of the answer on the action, and end with a result you can measure or a lesson you learned. Below are 20 sample STAR answers to questions interviewers really ask, for 16 roles from software engineer to nurse.

The examples are ours, written to show the structure: the people, numbers and details are invented, so replace them with your own. We make YoodaAI (about us), an interview practice and live interview assistant, and each question comes from one of our interview question pages by role.

How a STAR answer is built

Shares suggested by the University of Washington's Career & Internship Center.

The UK's National Careers Service adds "what you learned from the experience" to the result, and says your examples can come from work, home or volunteering (National Careers Service). Amazon, whose interviews are built on behavioural questions, calls the STAR method "the cornerstone" of them and suggests answers of about two to three minutes each (Amazon).

Disagreement and difficult people

1. "Tell me about a time you disagreed with a technical decision."

Sample answer for a software engineer

• Situation: My team planned to move our reporting jobs to a new message queue two weeks before our busiest sales period.
• Task: I owned those jobs, and I thought the timing put the peak at risk.
• Action: Rather than argue in stand-up, I ran the migration against a copy of last year's peak traffic and found two jobs that timed out. I took the results to the tech lead and suggested moving the low-risk jobs now and the rest after the peak.
• Result: We split the migration, the peak ran without incidents, and the rest moved three weeks later. I learned to bring evidence to a disagreement, not just an opinion.

Why it works: it disagrees with data and ends in a compromise everyone could accept.

2. "Tell me about a time you disagreed with a doctor about a patient's care."

Sample answer for a nurse

• Situation: On a night shift, a patient recovering from surgery had falling blood pressure and was more confused than earlier.
• Task: The doctor had asked me by phone to recheck him in four hours. I believed he needed to be seen sooner.
• Action: I repeated his observations, which had worsened, and called back using SBAR, saying clearly that I was worried and wanted a review within 30 minutes. When no one came, I escalated to the nurse in charge, following our escalation policy.
• Result: He was reviewed within 20 minutes and treated for an early infection that night. We discussed the case at the morning debrief.

Why it works: it keeps the patient at the centre and disagrees through the proper channels.

3. "Tell me about a time you managed a difficult stakeholder."

Sample answer for a project manager

• Situation: Halfway through an office move, the head of sales asked for floor plan changes in almost every weekly meeting.
• Task: I had to keep the move on date and on budget without losing the support of the biggest team moving.
• Action: I met him one to one and found the real issue: his team hadn't been asked about seating. I ran a 30-minute session with three of his team leads, gathered their needs in one list, and agreed that later changes would go through a short change request showing cost and delay.
• Result: The plan was signed off a week later, only two change requests came in after that, and the move happened on the planned weekend.

Why it works: it finds the cause behind the behaviour instead of fighting the behaviour.

4. "Tell me about a time you had to defend a design to stakeholders."

Sample answer for a UX designer

• Situation: I redesigned the checkout for a subscription app and removed an upsell step that marketing wanted to keep.
• Task: I needed marketing's agreement before launch.
• Action: I showed recordings of five usability sessions where people abandoned at the upsell. Then, instead of a debate, I proposed a two-week A/B test with revenue per visitor as the main measure, so marketing's goal was built into it.
• Result: Completed checkouts rose 9% with no fall in revenue per visitor, and marketing agreed to ship it. We now agree the success measure before every test.

Why it works: it answers the other side's concern instead of dismissing it.

Mistakes and failures

5. "Tell me about a time you made a mistake with a customer."

Sample answer for a customer service representative

• Situation: A customer called about a double charge, and I promised her a refund within 24 hours.
• Task: I then realised refunds like hers took five working days, so my promise was wrong.
• Action: I called her back that afternoon, before she found out the hard way, explained my mistake and the real timeline, and asked my team lead to approve a goodwill credit. I also added a note on refund times to our team's shared answers.
• Result: She thanked us for the call and stayed a customer, and the note is still in use. I check the process before I promise a date.

Why it works: it owns the mistake early and fixes the cause, not just the case.

6. "Tell me about a time your numbers turned out to be wrong. What did you do?"

Sample answer for a data analyst

• Situation: My weekly report showed a 15% jump in sign-ups.
• Task: Two days later I found the jump came from test accounts that a product change had stopped filtering out.
• Action: I told my manager and the report's readers that morning, sent corrected figures with a one-line explanation, and added an automatic check that flags any week where test accounts rise above a threshold.
• Result: The real increase was 3%, and the decision it fed into used the right number. The check has caught the same problem twice since.

Why it works: speed, honesty and a fix that stops it happening again.

7. "Tell me about a campaign that failed and what you learned."

Sample answer for a marketing manager

• Situation: I ran a launch campaign for a budgeting app for students, built on short social media videos.
• Task: The goal was 5,000 sign-ups in a month on a $20,000 budget.
• Action: After a week we had 600 sign-ups. I paused two of the four ads, moved their budget to the best one, and interviewed five students who had signed up. They had heard about us from friends, so I added a referral reward for the last two weeks.
• Result: We reached 3,100 sign-ups, short of the goal, but the referrals brought a third of them at under half the cost, and every launch since has used them. I learned to test a channel before committing the budget.

Why it works: it admits the miss and shows the change it led to.

8. "Tell me about a deal you lost. What would you do differently?"

Sample answer for a sales representative

• Situation: I spent three months on a deal with a logistics company and reached the final stage against one competitor.
• Task: I owned the proposal and the relationship with their operations director.
• Action: My final presentation focused on our features. After we lost, I asked for a debrief, and the director told me finance had chosen the competitor because its pricing fitted their budget cycle. I had never met finance.
• Result: I changed how I qualify deals: I now ask who signs off the budget in the first meeting and meet them before the proposal. Two of my next three large deals involved finance from the start, and both closed.

Why it works: it takes responsibility and proves the lesson stuck.

9. "Tell me about a time you missed a deadline. What happened?"

Sample answer for a software engineer

• Situation: I promised a data export feature in two weeks for a customer's quarter-end.
• Task: It was my estimate and my feature.
• Action: By day six I could see the export would be far slower on the customer's data than in testing. I told my manager that day, not at the deadline, offered a smaller version we could ship on time, a scheduled overnight export, and set out what the full version would need.
• Result: The customer had the overnight export for quarter-end and the full feature a week later. I now test estimates against realistic data before I commit.

Why it works: it raises the problem early and still delivers something useful.

Pressure and deadlines

10. "Tell me about a time you cut scope to hit a date."

Sample answer for a product manager

• Situation: We had promised a new invoicing feature for a trade show, and six weeks out, engineering estimated eight weeks of work.
• Task: I had to decide what we would show.
• Action: I compared each part of the feature with what the customers we would meet there had asked for, and cut three parts, including custom templates, that few of them needed. I told sales exactly what would be ready, so nobody promised what we couldn't demo.
• Result: We shipped on time, the demo produced 40 qualified leads, and the templates followed six weeks later.

Why it works: the cut is based on customer evidence, and everyone knew about it in advance.

11. "Tell me about a time you had to fix a production bug quickly."

Sample answer for a frontend developer

• Situation: On a Friday afternoon, our checkout page stopped loading for Safari users after a release.
• Task: I was on call and owned the checkout front end.
• Action: I confirmed the error, rolled the release back within 15 minutes, then found the cause: a newer JavaScript feature our build wasn't converting for older Safari versions. I fixed the build settings, added Safari to our automated browser tests and redeployed on Monday.
• Result: Checkout was down for Safari users for about 20 minutes instead of a weekend, and that kind of bug hasn't reached production since.

Why it works: it stops the damage first, then fixes the cause.

12. "Tell me about an outage you handled. What happened, and what changed afterwards?"

Sample answer for a DevOps engineer

• Situation: Our main API went down for 40 minutes when a database ran out of disk space during a traffic spike.
• Task: I was the incident lead that night.
• Action: I opened a call, asked one person to handle customer updates so the engineers could focus, and we freed space by clearing old logs before enlarging the volume. Afterwards I ran a blameless review, which found our disk alert fired at 95%, too late to act.
• Result: We moved the alert to 75% with a forecast of when the disk would fill, and set log retention. We had no disk-related outages the following year, and the review format became the team's standard.

Why it works: calm coordination, an honest cause and a lasting change.

13. "Tell me about a time you handled a last-minute change."

Sample answer for an administrative assistant

• Situation: Two days before a board meeting, the venue cancelled because of a burst pipe.
• Task: I was responsible for the meeting's logistics for 14 people, three of them travelling from abroad.
• Action: Within two hours I had booked a room at a nearby hotel, phoned the three overseas attendees rather than relying on email, and updated the invitations, catering and directions. I also left a note at the old venue's reception in case anyone went there.
• Result: Everyone arrived on time, and the chair asked me to use my checklist for every board meeting after that.

Why it works: it is quick, thorough and communicates with the people most at risk first.

Influence and judgement

14. "Tell me about a time a stakeholder rejected your recommendation."

Sample answer for a business analyst

• Situation: I recommended automatic approval for purchase orders under $500.
• Task: The finance director rejected it because she was worried about fraud.
• Action: I asked what evidence would change her mind, then pulled two years of orders: under $500, the manual step had rejected 0.4% of requests, and none for fraud. I proposed a three-month pilot in one department with a weekly audit sample, so she kept control.
• Result: She approved the pilot, that department's average approval time fell from three days to the same day, and the change went company-wide after the audit found no issues.

Why it works: it treats the objection as a question to answer, not an obstacle.

15. "Tell me about a time you pushed back on a request you thought was wrong."

Sample answer for an accountant

• Situation: Near year-end, a sales manager asked me to record a large order as revenue before the goods had shipped.
• Task: Our revenue recognition policy didn't allow it, and I was preparing the year-end figures.
• Action: I explained the policy and the audit risk, showed him when the revenue could be recognised, and offered to include the signed order in the pipeline report so his results still showed it. I copied my financial controller so the decision was on record.
• Result: The revenue was recognised in January, the audit passed without adjustments, and he later asked me to brief his team on the rules.

Why it works: it is firm on the principle and helpful on the alternative.

16. "Tell me about a model you built that ended up in production."

Sample answer for a data scientist

• Situation: Our support team sorted about 2,000 tickets a day by hand into 12 categories.
• Task: I was asked whether a model could route them automatically.
• Action: I trained a text classifier on a year of labelled tickets. Instead of full automation, I set it to route only tickets it was at least 90% sure about and send the rest to people. Two support leads and I checked a sample every week for the first month.
• Result: The model routed about 60% of tickets, with error rates the team accepted, and saved around 25 hours of sorting a week. Keeping people on the uncertain cases is what earned the team's trust.

Why it works: it shows judgement about scope as well as technical skill.

Going further for the people you serve

17. "Tell me about a time you went beyond what was expected for a customer."

Sample answer for a customer service representative

• Situation: An elderly customer called because his new router wasn't working, and he relied on video calls to see his doctor.
• Task: My job was to troubleshoot by phone, but he couldn't follow the steps.
• Action: I arranged a call back with his daughter on the line, walked them through the setup slowly and stayed on until he made a test video call. I added a note so his next call would go to someone who knew the case.
• Result: His appointment went ahead that afternoon, and his daughter wrote in to thank the team.

Why it works: it is warm, but every sentence describes something concrete the candidate did.

18. "Tell me about a time you had to learn a new business area quickly."

Sample answer for a business analyst

• Situation: I moved from retail analytics to an insurance claims project two weeks before the requirements workshops.
• Task: I had to understand claims handling well enough to lead those workshops.
• Action: I read the claims procedures, shadowed two claims handlers for a day each and kept a glossary of unfamiliar terms, which a senior handler checked. I mapped the current process on one page and asked the team to correct it.
• Result: The workshops ran on schedule, the team used my map as the project's baseline, and the glossary now goes to every new joiner.

Why it works: it shows a method for learning, checked with the experts.

19. "Describe a lesson that went really well. Why did it work?"

Sample answer for a teacher

• Situation: My class of 13-year-olds found fractions hard, and many had given up on them.
• Task: I wanted a lesson where every student succeeded early and was then stretched.
• Action: I built it around scaling a recipe for different numbers of people, starting with problems everyone could solve and adding harder versions students could choose. I checked understanding on mini whiteboards every ten minutes and paired confident students with those who were stuck.
• Result: In the exit quiz, 26 of 28 students got the core questions right, against about half in the previous test, and the class asked for more lessons like it.

Why it works: it explains why the lesson worked, with evidence of learning.

20. "Tell me about the biggest deal you closed."

Sample answer for a sales representative

• Situation: A regional hospital group was reviewing its staff scheduling software supplier.
• Task: I led the deal from the first meeting to the contract, against two larger competitors.
• Action: Instead of a standard demo, I asked to spend half a day with two ward managers and built the demo around their real rota problems. I brought our implementation lead in early to answer IT's questions and offered a rollout starting with one hospital.
• Result: We won a three-year contract worth $480,000, the largest on my team that year, and the phased rollout became our standard offer for hospital groups.

Why it works: the win comes from understanding the customer, not from the pitch.

How to write your own STAR answers

1. Start from the job description. It lists the skills the employer wants, and each one is a likely question. The National Careers Service suggests using STAR to show you meet them.
2. Collect a small set of stories you can reuse. One good story about a disagreement can also answer questions about influence, communication or a difficult colleague.
3. Write the result first. If you can't name a result or a lesson, pick a different story.
4. Say "I", not "we". Amazon's guide asks for "I" statements, and the University of Washington says to focus on the actions you took yourself, even in a team.
5. Rehearse out loud, not word for word. The National Careers Service warns against sounding too rehearsed and says to be ready for follow-up questions about your examples.

Common STAR mistakes

• A long situation and a short action. The action is the part being assessed.
• No result. A story that stops at what you did leaves the interviewer to guess whether it worked.
• "We did" from start to finish. It hides what you contributed.
• A hypothetical answer. "I would…" doesn't answer "Tell me about a time…". Use a real example.
• A story you can't defend. Follow-up questions ask for the detail only you have, which is where invented answers, or answers written by AI, tend to fall apart.

Practise your STAR answers

Reading examples helps, but saying your own stories out loud is what makes them come out clearly on the day. YoodaAI's interview practice is a spoken mock interview for your role and level: an AI interviewer asks behavioural or situational questions and follows up when a story is missing a number or your own part. The report at the end scores you out of 100 and gives a stronger answer to each question to compare with yours. The first 10-minute interview is free.

During a real interview, a live assistant can't tell your stories for you. YoodaAI is told never to invent employers, projects or numbers you haven't mentioned, so the stories have to come from your own preparation.

Frequently asked questions

What does STAR stand for?

Situation, Task, Action and Result. The National Careers Service includes what you learned from the experience in the result.

How long should a STAR answer be?

About two to three minutes, according to Amazon's interview guide. The National Careers Service says to keep examples short and to the point, and the University of Washington suggests spending about 60% of the answer on the action.

Can I use STAR if I don't have much work experience?

Yes. The National Careers Service says your examples can come from work, home or volunteering. Studies, part-time jobs, clubs and personal projects all have situations, tasks, actions and results.

Can I use STAR for "what would you do" questions?

Yes. Say what you would do, then back it up with a real example: "I'd start by…, and when something similar happened in my last job, I…". A past example is more convincing than a hypothetical one.

The short version

• STAR is Situation, Task, Action, Result. Spend most of the answer on the action, and say "I".
• End with a number or a lesson, and keep each story to about two to three minutes.
• Build a small set of reusable stories from the job description, and be ready for follow-up questions.
• Practise them out loud for free, or read the interview questions for your role.