What interviewers note in each part of a STAR answer, the questions that call for one, a 6–8 story bank, and one answer rewritten from weak to strong.
STAR interview questions are behavioral questions, usually starting "Tell me about a time…", that ask for one real example from your past. You answer with the Situation, your Task, the Actions you took and the Result, keeping the setup short, spending most of your time on what you personally did, and ending with the outcome and what you learned. You do not need thirty rehearsed answers. You need six to eight true stories that each cover several skills, told in a shape the interviewer can write down.
STAR is one tool inside a wider behavioral round; our guide to behavioral interview questions and how answers are scored explains the question families and how answers are rated.
Why interviewers want a STAR answer
STAR is not just candidate advice; it is also how some interviewers write their questions. The U.S. Office of Personnel Management's training deck on structured interviews tells the people writing questions to "use the STAR Model", so that each question draws out a situation or task, the action taken and the result. Behavioral questions themselves rest on the premise, in OPM's words, that the best predictor of future behavior on the job is past behavior under similar circumstances.
Amazon's interview-loop page walks candidates through the same four parts, but calls STAR one way to structure an answer rather than the only way. What the interviewer needs is the information, not the labels: the context, what you did and how it turned out.
How an interviewer listens to each part
OPM tells interviewers to take detailed notes that summarise what candidates actually said, then rate each answer against example responses written for each proficiency level. Google's re:Work guide describes rubrics showing what a poor, borderline, solid and outstanding answer would cover, with notes kept for review throughout the hiring process. From a recruiter's side of the table, the consequence is simple: the notes travel to the hiring decision, so every part of your answer should give the interviewer a line worth writing.
Situation and Task: context, then your job in it
The interviewer needs enough context to judge how hard the problem was, then needs to know which part of it was yours. OPM's example probes here are "Who was involved?" and "What factors led up to this situation?", and two or three sentences usually answer both. Long backstories cost you time you need for the Action; OPM's deck even says the panel chair may need to make polite, tactful interruptions if a candidate is talking too much. A vague task is a quieter problem: if the interviewer cannot tell what you were responsible for, they cannot tell whether you went beyond it.
Action: the part that gets scored
MIT's career office says the Action is going to be the longest part of your response, and this is where the competency shows. The interviewer is listening for decisions and the reasons behind them. OPM tells interviewers to seek clarification when candidates say "we did…" or "our group…", with probes as plain as "What was your role?" Every "we" invites a follow-up that uses time you could have spent on detail, so say what the team did in one clause and then say what you did.
Result: outcome, then what you learned
The interviewer wants to know whether your actions worked. Amazon's page says that if you have numbers or specific outcomes to back it up, "even better", though a concrete before-and-after works too. OPM's result probes are "What was the outcome?" and "Is there anything you would have done differently?", and the second is worth answering before it is asked, because one honest sentence about what you would change shows judgment.
One answer, told badly and then well
The question is "Tell me about a time something you were responsible for started to slip." Both answers are illustrative, written for this guide about the same invented experience.
The weak version: "So at my last job we had this weekly sales report that was always late. It was kind of a mess because the data came from different regions and everyone had their own spreadsheets. We talked about it a lot in team meetings and eventually we set up a shared template, and things got a lot better. I think it taught me a lot about communication and teamwork."
An interviewer can write down roughly "Report late. Shared template. Got better." We never learn whether the report was this person's job, every action is "we", "a lot better" is not an outcome anyone can rate, and the last line names two skills without showing either.
The strong version: "In my first year as a sales analyst, I owned the weekly regional sales report that leadership reviewed every Monday. It depended on spreadsheets from three regional managers, and for about a month it had gone out late because their files arrived in different formats. My job was to get it out on time without asking the regions for much more work. I spent twenty minutes with each manager to see how they built their file and found that two of them were retyping figures our CRM already held. I built a template that pulled those figures automatically and left three fields to fill in by hand. The third manager did not want to change, so instead of escalating I filled in the template from his existing file for two weeks, and after that he switched on his own. The report went out on time every Monday for the rest of the quarter, and my manager asked me to use the template for the monthly report too. Looking back, I would have talked to the managers in the first week rather than the fourth, because I spent three weeks fixing formatting by hand before asking why it kept happening."
Almost every sentence gives the interviewer something to write: the task is explicit and owned, and the actions are decisions with reasons: diagnose before fixing, cut other people's work rather than add to it, and handle resistance without going over someone's head. The result is concrete without a percentage, and the last sentence answers the "done differently" probe in advance. The same story also answers questions about improving a process or persuading someone who disagreed, with the emphasis moved, which is the idea behind a story bank.
The questions that call for a STAR answer
Behavioral questions come in endless wordings but probe a short list of competencies. OPM notes that structured interviews typically assess four to six, and names teamwork, oral communication, interpersonal skills, conflict management and influencing or negotiating as ones the format suits well. Where a question below comes from an employer's own page we say so; the rest are common wordings, not attributed to any company.
Problem solving and judgment
Amazon lists "Tell me about a time you faced a problem with multiple possible solutions. How did you decide what to do, and what was the outcome?" and "How have you used data to develop a strategy or make a decision?" among the questions you might be asked. Both test how you reach a decision, so the strongest answers name the option you rejected or the evidence you trusted, and why.
Ownership and failure
Amazon also lists "Describe a time when you took a risk, made a mistake, or failed. What happened, and what did you learn from it?" and says plainly that not every story has to be a success. The interviewer is checking whether you own the mistake and whether the lesson changed what you did next. For talking about your own shortcomings more broadly, see our guide to strengths and weaknesses questions.
Leadership and influence
"Share an example of when you took the lead on a project" is another Amazon example, and Google's re:Work guide uses "Tell me about a time your behavior had a positive impact on your team", with follow-ups on your primary goal, how teammates responded and your plan going forward. Neither needs a job title, only a moment where you moved people who did not report to you.
Teamwork, conflict and pressure
OPM's own example question is "Describe a situation in which you dealt with individuals who were difficult, hostile, or distressed. Who was involved, what specific actions did you take, and what were the results?", which spells out the parts of a STAR answer inside the question. Common variants include "Tell me about a disagreement with a coworker" and "Tell me about a time you had several urgent tasks at once." For conflict, interviewers listen for whether you understood the other person's position; for pressure, the trap is describing how busy you were instead of how you decided what came first.
How to build a story bank of 6–8 stories
If a structured interview typically assesses four to six competencies, as OPM's deck says, six to eight well-chosen stories give you coverage with a spare for follow-ups. MIT's career office makes the same point with a tutoring example, showing one experience answering questions on leadership, creativity, adaptability, overcoming a challenge, collaboration and communication. Here is how we suggest building the bank.
- List ten to fifteen experiences from work, study, volunteering or side projects where you made a decision that mattered, without judging them yet.
- Read the job description and note the four to six competencies it keeps returning to, since those are what an interview for that role is likely to test.
- Pick the six to eight experiences that cover those competencies between them, including at least one failure, one disagreement and one time you led without authority.
- Write each story as short notes under the four STAR headings, plus the one sentence you would say about what you would do differently.
- Tag each story with every competency it can answer, the way the sales-report story covers process improvement, persuasion and ownership.
Keep notes rather than scripts. Amazon's page says it does not expect perfect answers or rehearsed scripts, and that it is the interviewer's job to guide the conversation and get the details they need. We suggest aiming for roughly two minutes for most answers, and Amazon offers a useful check on the day: pause after your answer and ask whether the interviewer would like more context.
When the question is not really a STAR question
Some behavioral-sounding questions are hypothetical, such as "What would you do if a colleague kept missing deadlines?" Both re:Work and OPM treat these situational questions separately, and OPM's probes for them ask what you would do first and what factors would change your approach. Answer with your first step and your reasoning, then add a short real example if you have one, so the interviewer gets both the plan and the evidence.
If you are early in your career, use school, volunteering or a part-time job; Amazon's description of the Situation step itself mentions where you were "working (or studying or volunteering)". In one-way recorded interviews no one is on the other end to ask a follow-up, so the answer must be complete first time; our Target virtual interview guide covers that setting, and our guides to Amazon's STAR questions and Google's behavioral interview show how individual employers frame their questions.
Practise out loud, with follow-ups
Spoken stories drift, with the Situation swelling and the Result shrinking, so record one attempt at each and listen for how long the setup took and how often you said "we". The most useful thing a practice partner can do is ask the question and then use OPM's probes, "What was your role?", "What was the outcome?" and "Is there anything you would have done differently?", until every story survives them unprompted.
Verve AI's AI Mock Interview gives you spoken repetition when no partner is free, and you can put OPM's probes to yourself after each answer. An AI recruiter asks questions one at a time from a behavioral bank of 200 questions tailored to your interview profile, and afterwards you get "a detailed performance report with personalized feedback and scoring" based on your responses.
FAQ
How long should a STAR answer be?
Long enough to cover all four parts with Action as the largest, and short enough to leave time for follow-ups. We suggest roughly two minutes for most answers, as a guideline rather than a rule. If you are unsure, Amazon's advice is to pause and ask whether the interviewer would like more context.
How many STAR stories should I prepare?
Six to eight strong stories are enough for most interviews. OPM's training material says structured interviews typically assess four to six competencies, and one good story can answer questions on several of them. Include a failure, a disagreement and a time you led without authority.
Can I use the same story for different questions?
Yes, as long as you shift the emphasis to match the question. One experience can answer a process-improvement question by stressing the fix, and a persuasion question by stressing how you won over a reluctant colleague. Tagging each story with every competency it covers, as described above, makes the switch easy in the moment.
What if I don't have a work example?
Use school, volunteering, a part-time job or a personal project, which Amazon's own description of the Situation step allows for. Interviewers are assessing how you behaved, not where it happened. If you have no real example, say so and explain how you would handle it, rather than inventing one.
Sources
- STAR Model used to write structured interview questions (Situation or Task, Action, Result); past behavior as the best predictor of future behavior; structured interviews typically assess 4–6 competencies, with teamwork, oral communication, interpersonal skills, conflict management and influencing/negotiating listed; example difficult-individuals question; probe guidance including seeking clarification on "we did…"; example Situation/Task, Action and Result probes; situational question probes; detailed notes summarising responses; rating against example responses per proficiency level; chair may interrupt a candidate talking too much (OPM training deck, PDF): https://www.opm.gov/policy-data-oversight/assessment-and-selection/structured-interviews/structured-interviews.pdf
- OPM STAR description for writing structured interview questions: https://www.opm.gov/frequently-asked-questions/assessment-policy-faq/structured-interviews/how-do-i-create-structured-interview-questions/
- Behavioral vs hypothetical questions, example question with follow-ups, rubrics for poor/borderline/solid/outstanding answers, detailed notes reviewed through the hiring process (Google re:Work, updated March 2026): https://rework.withgoogle.com/intl/en/guides/a-guide-to-structured-interviewing-for-better-hiring-practices
- Amazon's STAR description, STAR as one way but not the only way, example behavioral questions, numbers or specific outcomes "even better", not every story has to be a success, no rehearsed scripts expected, pause and ask if the interviewer wants more context, "working (or studying or volunteering)": https://amazon.jobs/en-gb/landing_pages/in-person-interview
- Action as the longest part of a STAR answer; one tutoring experience covering leadership, creativity, adaptability, overcoming a challenge, collaboration and communication (MIT CAPD): https://capd.mit.edu/resources/career-toolkit-interviewing/
- AI Mock Interview: AI recruiter asks questions one at a time, behavioral question bank of 200 questions tailored to the interview profile, "a detailed performance report with personalized feedback and scoring": https://docs.vervecopilot.com/features/mock-interview
Ryan
CEO of Verve AI








