Career Guide HQ

The STAR Method: How to Answer Behavioral Questions (+ Examples)

Table of contents

By the end of this guide you will be able to spot a behavioural question from its opening words, structure an answer in four parts with the right amount of time on each, and pull the right story out of your head under pressure.

It covers what STAR is and when it applies, how much of the answer each part should take, one worked example, seven more from different industries, a table of common questions and the competency each one tests, and the five mistakes that make a good story land badly.

What it is and when to use it

STAR stands for Situation, Task, Action, Result. It is a way of structuring an answer about something you have actually done, and employers use it as part of structured interviewing to judge candidates by how they respond to behavioural and situational questions (Wikipedia; Indeed).

You need it the moment a question asks for a specific past event rather than an opinion. The signal phrases barely change between employers or countries. Listen for "Tell me about a time when…", "Give me an example of…" and "Describe a situation where you had to…" (Indeed; University of Washington Career & Internship Center), along with "Can you share a situation when…" and "What do you do when…" (Educative). These questions usually map straight onto a competency named in the job description (Indeed).

STAR is the wrong tool for questions about what you know, why you want the job, or what your salary expectations are. For hypothetical questions — "What would you do if…" — you can still borrow the shape: describe the closest real situation you have handled, then say what you would carry across.

Most interviewers will not name the method. They simply expect a story with a beginning, your own actions in the middle, and an ending.

Each part, explained

PartWhat goes inRough share of the answer
SituationWhere you were, when, your role, and the one problem or opportunity that matters. Just enough background for the story to make sense.About 20% (MIT Career Advising & Professional Development, 2023)
TaskWhat you specifically were responsible for, and what would count as success. One or two sentences.About 10% (MIT, 2023)
ActionThe steps you took, in order, and why you chose them. This is the part the interviewer is scoring.About 60% (MIT, 2023)
ResultWhat changed, how you know, and anything that stuck afterwards.About 10% (MIT, 2023)

The shape matters more than the exact percentages: the context should take the least time and your own actions should take the bulk of the response (ORAU/ORISE).

Say "I", not "we". When you describe the actions taken, use "I" and keep the focus on you rather than the team (UW–Madison SuccessWorks). BetterUp (2025) makes the same point and adds that the outcome should be a positive, measurable one where possible. "We rolled out the new system" tells the interviewer nothing about your contribution; "I wrote the migration checklist and trained the four counter staff" does.

If your work does not produce numbers, measure it another way: time saved, a backlog cleared, an error that stopped recurring, a customer retained, a process that was still being used after you left. Name the evidence, not just the adjective.

One worked example

The figures in this example are illustrative — use your own. The question is a standard one: "Tell me about a time when you worked as part of a team to successfully execute a project" (MIT Career Advising & Professional Development, 2023).

"Tell me about a time when you worked as part of a team to successfully execute a project."

Customer support specialist, business software company, team of six

Situation: Last spring my company moved every support ticket from a shared inbox to a proper helpdesk tool. Six of us handled around 300 tickets a week between us, and the switch was set for a single weekend.

Task: I was not the project lead — that was my manager — but I was the person on the team who knew the old inbox rules best, so I took responsibility for making sure nothing in flight got lost in the move.

Action: I exported the open tickets and sorted them into three groups: waiting on the customer, waiting on engineering, and ready to close. I closed 40 of them myself in the week before the move so there was less to migrate. For the rest, I wrote a one-line status note on each so whoever picked it up on Monday had the history. I also ran a 30-minute walkthrough for the two newest colleagues on the Friday, because I could see they were nervous about the new tool, and I sat with them on the Monday morning.

Result: We went live with no ticket lost and no customer asked to repeat their problem. First-response time was back to normal by the Wednesday instead of the two weeks my manager had budgeted for, and the status-note format I used became part of our standard handover.

Notice what the answer does not do: it does not explain the software, describe the company's history, or spend three sentences on how busy the team was. The setup is two sentences, the actions are specific and first person, and the result includes something that outlasted the project.

More examples

Seven answers from different industries. Read them for shape rather than content — the details are illustrative, and yours should be true.

Healthcare: "Tell me about a time you disagreed with a colleague."

Ward nurse, 28-bed medical unit, three years qualified

Situation: On a late shift, a colleague was preparing to discharge a patient who had been visibly unsteady during his mobility check that afternoon. The paperwork was already signed and the family had arrived.

Task: I was taking over his care overnight, so it was on me to raise it before he left, without turning it into an argument in front of the family.

Action: I asked my colleague to step into the treatment room. I told her exactly what I had seen during the mobility check and showed her the two entries in the notes. Rather than overruling each other, I suggested we ask the registrar for a five-minute review. While that happened, I sat with the patient's daughter and explained the delay honestly.

Result: The registrar ordered a postural blood pressure check, which came back abnormal, and the discharge was deferred to the next morning with a physiotherapy review. My colleague and I agreed to raise mobility concerns at handover rather than at the door, and the ward sister added a prompt to the handover sheet.

Why it works: it disagrees with a person without attacking them, keeps the patient at the centre, and ends with a change that outlived the shift.

Construction: "Describe a situation where you had to meet a tight deadline."

Site supervisor, commercial fit-out contractor, 40 trades on site

Situation: Two weeks before a hotel handover, the client pulled the opening date forward by nine days and our internal doors were stuck with the supplier.

Task: I was responsible for the programme on floors three to six, so I had to find nine days without asking anyone to work unsafely.

Action: I resequenced the last three weeks so decorating and second-fix electrical ran floor by floor behind the carpet fitters instead of after them. I called the door supplier myself and got a partial delivery of the fire doors released first, since those blocked sign-off. I moved our 7am briefing from the site office to each floor so issues got raised where the work was, and I kept a single one-page list of blockers that the client's project manager could see daily.

Result: We handed over on the revised date with a snag list of 18 items, none of them fire-related, and only one Saturday worked. The client used the same floor-by-floor sequence on their next fit-out.

Why it works: the actions are decisions a supervisor actually makes, and the result includes both a number and a safety boundary that was not crossed.

Retail: "Give me an example of how you handled an unhappy customer."

Store manager, high-street homeware shop, team of nine

Situation: On a Saturday morning a customer whose sofa had been delivered damaged twice was shouting at one of my newest sales assistants in front of a full shop floor.

Task: I needed to take the heat off my assistant, get the customer's problem actually solved, and keep the rest of the floor running.

Action: I introduced myself, apologised for the two failed deliveries without blaming the depot, and walked the customer to the seating area away from the queue. I asked my assistant to cover the till instead of sending her out the back, so she did not feel she had done something wrong. I phoned the depot in front of the customer, confirmed a replacement and an exact delivery window, and arranged a collection of the damaged unit on the same visit.

Result: He accepted the new date and came back three weeks later to buy dining chairs. Afterwards I wrote a one-page card for the team on what they are allowed to promise on damaged deliveries, and the next two cases were resolved in store without a manager.

Why it works: it protects a junior colleague, fixes the underlying problem rather than offering a discount, and turns one incident into a standard.

Technology: "Tell me about a time you made a mistake."

Backend engineer, payments team, mid-sized software company

Situation: I shipped a configuration change on a Thursday evening that quietly disabled the retry logic on failed card payments.

Task: It was my change, so it was mine to find, fix and explain.

Action: When the overnight failure alert came in, I rolled the change back within about 20 minutes rather than trying to fix forward. I pulled the list of affected transactions, passed it to support with a suggested message so customers heard from us before they noticed, and wrote up what happened the same morning. In the review I said plainly that I had tested the change locally but not against the staging queue. I then added a staging check to the deploy checklist and wrote the integration test that would have caught it.

Result: Around 60 payments retried successfully once the rollback landed, none were lost, and the same class of failure has not recurred. The staging check is now part of the team's standard release process.

Why it works: it owns the error without drama, separates the fix from the prevention, and shows a change to the system rather than a promise to be more careful.

Education: "Tell me about a time you had to adapt to a change you did not choose."

Secondary maths teacher, Year 9, four classes

Situation: In January the department dropped setting and merged my top set with a middle set, so I had a class with a three-year spread in attainment and no extra staffing.

Task: I had to keep the stronger students moving without losing the ones who had been struggling with fractions since primary school.

Action: I ran a ten-minute diagnostic in the first lesson and grouped the class into three bands for practice work only, keeping whole-class teaching for the new content. I built each worksheet in three tiers from the same starting question so nobody could see who had which version. I used the first ten minutes of every lesson for retrieval practice on the weakest topics from the diagnostic, and I emailed six sets of parents with two specific things to practise at home.

Result: At the end-of-term assessment, eleven of the thirty students moved up a grade band and none dropped. My head of department asked me to share the three-tier worksheet template with the rest of the maths team.

Why it works: the actions are concrete teaching decisions, not attitudes, and the result covers both the class average and the students at risk.

Finance: "Give me an example of a time you persuaded someone more senior than you."

Financial analyst, manufacturing group, two-person reporting team

Situation: Our monthly forecast kept overstating gross margin because inbound freight invoices arrived a month late and were booked in the period they were received.

Task: I had spotted the pattern, but the fix meant changing a process the finance director had signed off years earlier.

Action: Instead of raising it in the monthly meeting, I rebuilt the last six months with a freight accrual and put the two versions side by side on one page. I checked my logic with the management accountant first so I was not blindsided. Then I asked the FD for fifteen minutes, showed the comparison, and offered two options: a standard accrual based on a three-month average, or a request to the supplier for earlier invoicing.

Result: He took the accrual option and asked me to document it. Forecast-to-actual margin variance narrowed from around two percentage points to under half a point over the following quarter, and the accrual is now in the month-end checklist.

Why it works: it shows preparation before the conversation, gives the senior person a choice rather than a verdict, and measures the improvement.

Hospitality: "Tell me about a time you took the initiative without being asked."

Duty manager, 120-room city hotel, night shift

Situation: At 1am the only guest lift failed, with an engineer not available until 8am and a 60-person conference checking in from 7.

Task: Nobody senior was on site, so the decisions on the night were mine.

Action: I pulled the arrivals and in-house list and identified nine guests on floors five and six with mobility needs or young children, then moved the four who were still awake and willing to lower floors. I printed signs for the lift lobby on every floor and left a note under the doors of the upper-floor rooms so nobody discovered it in the morning. I briefed the breakfast team at 6am to offer floor service to the guests I could not move, and I moved conference registration from the first-floor suite to the lobby.

Result: Registration opened on time, one complaint was logged and resolved with an apology and a room move, and the general manager turned my night's notes into the hotel's standard lift-failure procedure.

Why it works: it shows judgement made alone, prioritises the guests most affected, and ends with a permanent process rather than a lucky escape.

Build your story bank

It is impossible to know exactly what an interviewer will ask, so prepare a few strong, versatile stories in advance that can be tweaked for different questions (The Muse). Six to eight is usually enough for a single interview.

The table below pairs common behavioural questions with the competency each one is testing. One of them — "Tell me about a time when you worked as part of a team to successfully execute a project" — is a standard sample question (MIT Career Advising & Professional Development, 2023).

QuestionCompetency it tests
Tell me about a time you worked as part of a team to execute a project.Collaboration: how you divide work, manage dependencies and share credit.
Describe a situation where you had to meet a tight deadline.Prioritisation and composure under time pressure.
Tell me about a time you disagreed with your manager.Upward influence and professional disagreement.
Give me an example of a mistake you made and what you did next.Accountability and learning from failure.
Tell me about a difficult customer, client or stakeholder you handled.Service recovery and emotional control.
Describe a time you had to learn something quickly.Learning agility and self-direction.
Tell me about a time you led people who did not report to you.Influence without authority.
Give me an example of when you had to deliver bad news.Communication judgement and honesty.
Describe a time you improved a process or fixed something inefficient.Initiative and analytical thinking.
Tell me about a time your priorities changed at short notice.Adaptability and resilience.

Write each story once, in the four parts, and then tag it with the two or three competencies it can serve. A story about running a project can demonstrate leadership, problem-solving or teamwork depending on which parts you emphasise (The Interview Guys). Before an interview, read the job description and mark which of your tagged stories covers each requirement. Any requirement with no story next to it is the gap to work on.

Common mistakes

  • Spending half the answer on the setup. The interviewer does not need your company's history, the org chart or the backstory of the person who annoyed you. The context should take the least time and your own actions should take the bulk of the response (ORAU/ORISE). Fix: cap the Situation and Task at three sentences and start the next sentence with "So I…".
  • Saying "we" all the way through. If every sentence is "we decided" and "we delivered", the interviewer cannot score you, only your former team. Use "I" and keep the focus on yourself rather than the team (UW–Madison SuccessWorks). Fix: rehearse the Action out loud and rewrite any sentence that does not begin with something you personally did.
  • Stopping at the Action with no Result. Answers that trail off after the steps leave the interviewer to guess whether it worked. The outcome should be positive and measurable where possible (BetterUp, 2025). Fix: end every story with one sentence containing a number, a timeframe or something that was still in use afterwards.
  • Telling a good story that answers a different question. If you are asked about conflict and you tell your favourite project story, it reads as evasion or as not listening. Fix: repeat the competency back in your first sentence — "The clearest example of disagreeing with a manager was…" — so you commit to the right story before you start.
  • Inflating or inventing the example. Focus on actual behaviours and emotions rather than bending the truth, because a dishonest answer comes across as disingenuous and may not match your application materials (MIT Career Advising & Professional Development, 2023). Fix: pick real stories you can survive three follow-up questions about, including "what would you do differently?"

Frequently asked questions

How long should a STAR answer be?

Aim for one to two minutes: be brief in the setup and give just enough background for the story to make sense (Duke University Career Hub, 2022). More broadly, interview answers should generally run between 30 seconds and four minutes, and using STAR helps keep them at four minutes or lower (Indeed). If you are unsure, time yourself reading a story aloud at a normal pace. Most people find that one to two minutes is roughly 150 to 250 spoken words, which is enough for two sentences of setup, four or five actions and one clear result. Pause at the end rather than adding more — the interviewer will ask for detail if they want it.

Can I use the same story for more than one question?

Yes, within reason. The same STAR story can serve several questions as long as you adapt it each time, because a story about leading a project could demonstrate leadership, problem-solving or teamwork depending on which aspects you emphasise (The Interview Guys). What changes is the Task framing and which actions you dwell on. What does not change is the truth of the story. Try not to use one story more than twice in the same interview, though — a third outing makes it look as though you have had one good week at work. That is the argument for preparing six to eight stories rather than two.

What if I genuinely do not have an example?

Say so, then offer the nearest real thing. If you do not have work experience to draw on, use academic projects, volunteer work, extracurricular activities or personal initiatives, since the skills and behaviours demonstrated matter more than the setting (The Interview Guys). If you are new to the workforce, internships, volunteering and group projects from school all count, and some employers will explicitly ask for a non-work example (Indeed). A usable answer sounds like: "I have not managed a budget in a paid role, but I was treasurer for a student society — can I use that?" What does not work is silence, or inventing something. If the situation truly has never come up, say what you would do and what you would base that on.

What if the result was not a success?

Use it, but finish the story properly. Failure questions are asked precisely to see whether you can be accountable, so a sanitised answer defeats the purpose. Describe the outcome honestly, then add what you changed as a result and what evidence you have that the change stuck — a new checklist, a different escalation habit, a second attempt that went better. Keep the blame off named colleagues. The one result to avoid is a story where nothing changed and you learned nothing, because that is the only version that actually counts against you.

Is it acceptable to prepare answers word for word?

Prepare the structure, not the script. Choose a few strong, versatile stories in advance and be ready to tweak them for various questions (The Muse), but memorising sentences makes you sound recited and leaves you stranded when the question is phrased differently. A workable middle ground is to write each story out in full once, then reduce it to five or six bullet points: the setting, the task, three or four actions, the result. Practise from the bullets. If you are interviewing remotely, keeping those bullets on a single page beside you is usually fine — just do not read from them.

What is STARR, and do I need it?

STARR adds a fifth element, reflection, to situation, task, action and result (Indeed UK). The reflection is one line on what you learned or would do differently. You do not need to announce it as a separate method, and most interviewers will not ask for it by name, but adding a short reflective sentence is useful for failure questions, conflict questions and anything to do with feedback. Keep it to a single sentence. If your reflection is longer than your result, the answer has tipped into self-analysis and away from evidence.

Should I tell the interviewer I am using STAR?

No need. STAR is one method of structured employment interviewing used by employers to evaluate how candidates respond to behavioural and situational questions (Wikipedia), so the structure is what they are listening for, not the label. Naming it can make an answer sound like a technique being performed. The exception is when you need a moment to think: "Let me pick the clearest example" buys you the same few seconds and sounds natural. Signposting within the answer — "so my job in that was…", "what I did was…", "in the end…" — gives the interviewer the structure without the acronym.

Sources

  1. WikipediaSituation, task, action, result
  2. IndeedHow To Use the STAR Interview Response Technique
  3. Indeed10 Behavioral Interview Questions (With Sample Answers)
  4. University of Washington Career & Internship CenterSTAR Method of Interviewing
  5. MIT Career Advising & Professional DevelopmentUsing the STAR method for your next behavioral interview (worksheet included)2023-08-30
  6. UW–Madison SuccessWorksThe Star Method
  7. BetterUp30 Star Method Interview Questions & Tips to Ace Your Interview2025-04-09
  8. Duke University Career HubSTAR Method for Responding to Interview Questions2022-10-27
  9. IndeedHow Long Should Interview Answers Be? (Examples and Tips)
  10. The Interview GuysThe STAR Method: Your Complete Guide to Answering Behavioral Interview Questions
  11. The MuseSTAR Method: How to Use This Technique to Ace Your Next Job Interview
  12. Indeed (UK)How to use the STARR method in interview responses
  13. EducativeRecognizing Behavioral Interview Questions (Grokking the Behavioral Interview)
  14. ORAU/ORISEUsing the STAR method to ace interviews