STAR method: how interviewers rate your answer, with examples
The STAR method from the interviewer's side: where it comes from, how answers are rated, the behavioral questions 177 real job postings point to, example answers and resume bullets.
"Tell me about a time you disagreed with a colleague." You know the answer should follow STAR: Situation, Task, Action, Result. Then you get there, and either you spend a minute on background or you skip to a happy ending nobody can check.
Most STAR guides explain the method from the candidate's chair. This one starts from the other chair. It covers where the method comes from, what the interviewer notes while you talk, and how a published rating scale turns your story into a score. Then it shows which behavioral questions a job posting will produce, based on a count of 177 real postings, with example answers and how to turn the same story into a resume bullet.
What the interviewer is writing down
STAR was built for interviewers, not candidates. DDI, the assessment firm, states on its Targeted Selection page that it "created the STAR method to help interviewers collect complete information from candidates". In its version, the interviewer listens for situations or tasks, the actions taken and the results. DDI treats situation and task as one step.
The interviewer has a gap to fill in each column. If you never say what you did, the Action column stays empty and you get a follow-up question, or a low score.
Public guidance says the same thing in different words:
- The US Office of Personnel Management's Structured Interview Guide tells question writers that each question "should be written to elicit specific details about a situation, task, or context, the actions the person took or did not take, and the impact of these actions". The questions are written to pull a STAR answer out of you, even if you have never heard of STAR.
- The UK Civil Service's candidate guidance recommends STAR by name and asks you to prepare examples of "the behaviours outlined in the job advert".
- Amazon's interview page asks for context, task, actions and outcome, then adds that STAR is "not the only way" to tell the story. It also asks you to say "I" instead of "we".
DDI lists what STAR helps an interviewer catch. Talking about what you "would do" instead of what you did. Answers that "sound good but lack substance". And taking credit for other people's work. Those three are the answers that score badly, whatever structure you use.
How a STAR answer gets rated
Advice pages disagree about which part matters most. The Muse quotes an HR professional calling the result the most important part, while MIT's career office gives 60% of the answer to the action. A published rating scale gives a more useful answer.
The OPM guide gives agencies a five-level proficiency scale for rating answers. Two things move a candidate up the scale. One is how hard the situation was. The other is how much guidance the candidate needed:
| Level | How hard the situation was | How much guidance was needed |
|---|---|---|
| 5, Expert | "exceptionally difficult situations" | serves as "a key resource and advises others" |
| 3, Intermediate | "difficult situations" | "occasional guidance" |
| 1, Awareness | "the simplest situations" | "close and extensive guidance" |
The guide's worked example for interpersonal skills makes it concrete. A level 1 behavior is to refer employees "to the appropriate staff member to resolve their issues". A level 3 behavior is to restore "a working relationship between angry co-workers who have opposing views". Both deal with a problem. Only one shows the candidate handling it.
This is one public employer's 2008 guide, and its interviewers use the examples "as a general guide (not an absolute)". Your interviewer may score differently or not score at all. Still, the scale tells you what a strong answer contains, and that changes how you write each part:
- Situation sets the ceiling. Say in one sentence what made it hard: a deadline, a client threatening to leave, no authority over the people involved. A situation with no difficulty in it caps your answer at the bottom of the scale.
- Action shows the guidance level. Name the decisions you made yourself ("I decided to", "before anyone asked, I"). "My manager told me to" places you lower.
- Result proves the action worked, but it does not have to be a win. Amazon's page says "not every story has to be a success", as long as you say what you learned.
The four parts, with a word budget
Most guides give a time range for a STAR answer, 1.5 to 2 minutes on Indeed's STAR page. Time is hard to feel while you are talking. Words are easy to count while you prepare.
Yuan, Liberman and Cieri (Interspeech 2006) measured thousands of recorded English phone calls between strangers. The average speaking rate per conversation topic ran from 152 to nearly 170 words per minute. At that pace, 2 minutes is about 300 to 340 words, and 90 seconds is about 230 to 255. Aim for 150 to 250 words written out. You will add a few words when you say it aloud, and an answer that ends before 90 seconds leaves time for the follow-up questions.
The template to fill in about 200 words in total
Where you were, when, and what made it hard. One constraint is enough.
"In my second year at …, our team had … weeks to … and …"
What was yours to do, and why it fell to you.
"It was my job to …, because …"
Two or three steps you took, in order, with the reason for each. Say "I", and name any decision you made without being told.
"First I … because … Then I decided to … instead of …"
What changed, with a number if you have one, and what you do differently since.
"We went from … to … in … Since then I …"
The difficulty in the Situation and the decisions in the Action are what move the rating.
The usual advice still holds, so here it is in brief. Prepare five or six stories, not one per question, because one good story can answer three questions. Write each one out once, then rehearse from three lines of notes so you do not recite. If an answer runs long, cut background, not actions. And when you finish, stop. Amazon's page suggests you "pause after your answer and ask if your interviewer would like more context".
Which behavioral questions your posting will produce
Every guide tells you to read the job description. We wanted to know what that reading actually finds. So on 1 October 2026, we pulled the requirements sections of 177 job postings from 22 US tech employers' public Greenhouse job boards. The postings spanned nine role families, from sales and marketing to engineering, design, data and recruiting. Then we counted the requirement lines that describe a behavior rather than a tool, a degree or a number of years.
168 / 177
median 3 of 8 requirement lines
postings listed at least one behavior in their requirements, such as communicating, influencing without authority or owning a problem. Each of those lines is a behavioral question waiting to be asked.
Source: HiredFolio count of 177 Greenhouse postings, 1 October 2026
To repeat the count, take the requirements and qualifications sections only, search each line with one regular expression per competency, and check a sample by hand. We read 100 lines. The pattern matching is not perfect in either direction. About one matched line in six was not really a behavior, such as an office-attendance line that mentions "collaboration". About one unmatched line in six was. So treat the per-competency shares below as approximate. The headline figure (168 of 177 postings) holds either way. These are US tech employers on one day, not the whole job market.
The OPM guide tells question writers to use superlatives ("most, last, worst, least") so the candidate describes one real incident. Apply that rule to the competencies that came up most often, and you get the questions to prepare for:
| Competency in the requirements | Share of postings | The question it becomes |
|---|---|---|
| Communication | 68% | "Tell me about the last time you had to explain something complex to someone outside your field." |
| Collaboration across teams | 59% | "Describe the most difficult project you ran with another team." |
| Influencing stakeholders | 55% | "Tell me about a time you changed a decision you didn't own." |
| Ownership, initiative | 47% | "Tell me about the last problem you fixed that wasn't your job to fix." |
| Problem solving, judgment | 42% | "What's the hardest call you made with incomplete information?" |
| Ambiguity, change | 35% | "Tell me about the least defined project you've worked on." |
| Prioritizing, deadlines | 30% | "Describe the worst week you had for competing deadlines." |
To do this on the posting in front of you:
- Copy the requirements section, not the whole ad.
- Mark every line that describes a behavior ("influence without authority", "thrive in ambiguity", "communicate clearly with executives"). Skip the tools and the years.
- Rewrite each marked line as "Tell me about the last / most / worst time you…" and attach one of your stories to it. If two lines share a story, good. You need fewer stories.
Example answers by competency
The answers below are examples written for this article. The people and numbers are invented to show the shape. Each runs 150 to 220 words, between one minute and 90 seconds aloud.
Influencing without authority
"Tell me about a time you changed a decision you didn't own."
I was a program manager on a payments product. Two weeks before launch, the sales director wanted to open it to all customers on day one. Support had two people trained on it.
The launch plan was mine, but the decision was his, and I had no authority over sales.
I didn't argue in the launch meeting. I pulled the support tickets from our beta and found that one in five beta customers had opened a ticket in their first week. I applied that rate to the full customer list and showed the director what it meant: about 300 tickets in week one, for two trained people. Then I offered him a version of what he wanted. Every customer could see the product on day one, and we would switch it on in three waves over two weeks, his biggest accounts first.
He took the waves. Support handled the launch without a backlog, and his top accounts were live in the first wave, which he used in his quarterly review. Since then I bring the number to the first conversation instead of the second.
The difficulty is stated up front (no authority, a director, two weeks). The action has a decision in it (not arguing in the meeting, offering waves). The result includes what changed in how the candidate works.
Explaining something complex
"Tell me about the last time you had to explain something complex to someone outside your field."
Last spring I was the data analyst for our retention team. Finance had cut the marketing budget based on a dashboard that showed email campaigns bringing in almost nothing.
The dashboard was mine. The numbers were right, but they only counted the last click before a purchase, and the finance team didn't know that.
I asked for twenty minutes with the finance lead. Instead of explaining attribution models, I showed her five real customer journeys, printed on one page, each one starting with an email and ending with a click on a search ad. Then I showed the same month counted two ways. I left out the methodology unless she asked, and she asked about one thing, which I answered with one more journey.
Finance restored half the budget for a three-month test, and the dashboard now shows both counts side by side with a one-line note. I've reused the five-journeys page twice since.
Owning a mistake
"Tell me about the worst mistake you made at work."
In my first year as a recruiting coordinator, I sent an offer letter with last year's salary band to a senior engineer. He accepted it the same evening.
I found the error the next morning, before anyone else had noticed. Fixing it was my job, and so was telling people.
I told the hiring manager and my lead within the hour, with the gap in dollars and two options already written up. We agreed to honor the correct, higher band, so the fix cost us money but not the candidate's trust. I called him myself to explain the change before the corrected letter arrived. Then I looked at why it happened: the template pulled the band from a spreadsheet nobody had updated. I moved the bands into the offer tool and added a check that blocks a letter if the band is more than six months old.
He started on time. The check caught two more stale bands that quarter, before any letter went out.
Working without a clear brief
"Tell me about the least defined project you've worked on."
Our CEO asked marketing for "something for small businesses" after a board meeting. There was no budget line, no product change and no owner.
I was a product marketing manager, and I volunteered to own it, mostly so it wouldn't turn into three half-projects.
I wrote down what I didn't know and picked the question that mattered most: did small businesses already use us? I asked sales operations for accounts under twenty seats and found about 400, with a shorter sales cycle than our average. I interviewed eight of them in two weeks. Six said the same thing: they had found us through an accountant. So I proposed one test instead of a campaign, a referral page for accountants, and wrote a one-page brief with a single success measure.
The CEO approved the test in one meeting. In its first quarter it brought in 60 new small accounts, and it became a regular program. When I get a vague request now, I start with the one fact that would change the plan.
Competing deadlines
"Describe the worst week you had for competing deadlines."
I was a support team lead when a product outage landed in the same week as our quarterly audit, and one of my four agents was out sick.
I had to keep response times inside our contract and deliver the audit sample by Friday.
On Monday morning I sorted the open tickets by contract tier and found that 40 of them belonged to customers with a four-hour response clause. Those went to the two most experienced agents and nothing else. I wrote one status reply for the outage tickets so the third agent could close the duplicates fast. Then I called the audit lead and asked which part of the sample she needed first. She needed the escalations by Wednesday, the rest could wait to Monday, so I did the escalations in the evenings.
We missed no contract deadline that week, and the audit got its escalations on Wednesday. I now ask "which part do you need first" before I assume a deadline covers everything.
A weak answer, rewritten
Here is a common first draft of the same competing-deadlines story:
"We had a really busy week with an outage and an audit at the same time. It was a lot of pressure, but I'm good at staying calm and organized. We all pulled together, worked late, and got everything done in the end. The customers were happy and the audit went fine."
It reads fine and scores low. The difficulty is a mood ("a lot of pressure"), not a fact. The actions belong to "we". "Staying calm and organized" is a claim about yourself, which is the answer DDI describes as sounding good but lacking substance. And "everything done" can't be checked. The rewrite above keeps the same events and adds three things: a constraint with a number, two decisions with their reasons, and a result someone could verify.
The result line is often the quickest fix:
Example one result sentence rewritten
Can't be checked
The customers were happy and the audit went fine.
Can be checked
We missed no contract deadline that week, and the audit got its escalations on Wednesday.
If you have no number, describe the state before and after: "the report went from three days to the morning it was due", "the client renewed". Counts of time, money, volume, errors or people all work. A number you can't defend in a follow-up question is worse than none.
Follow-up questions to prepare for
A structured interview plans its follow-ups too. The OPM guide lists example probes for each part of a behavioral answer, and they are worth rehearsing:
- On the situation. "What factors led up to the situation?" and "Could you or anyone else have done something to prevent the situation?"
- On the action. "What is the first thing you did?" and "What was the most important factor you considered in taking action?"
- On the outcome. "Is there anything you would have said and/or done differently?"
The prevention question is the one candidates miss. If the problem was partly your fault, say so in the Situation, before the interviewer asks. And keep one honest answer ready for "what would you do differently". A story with nothing to improve sounds rehearsed.
Salary questions follow a different logic. For those, see how to negotiate salary in an interview.
From STAR answer to resume bullet
The same story makes a resume bullet once you compress it. Drop most of the Situation, keep one clause of context, lead with the Action verb, and end on the Result:
Example the influencing story as one bullet
Duty, no proof
Responsible for launch planning and coordination with sales and support.
STAR, compressed
Led stakeholder management for a payments launch: used beta ticket data to move sales to a three-wave rollout, launch handled with no support backlog.
Watch the word form. Some keyword filters match words literally, and ours does. We ran a short resume through HiredFolio's keyword matcher, the one behind our resume scan. It read "Negotiated renewals with 14 enterprise accounts. Mentored two junior engineers. Prioritized the backlog with product." Then we checked it against keywords a posting might use:
| Keyword in the posting | Found in that resume? |
|---|---|
| negotiation | no |
| mentoring | no |
| prioritization | no |
| negotiation, after adding "contract negotiation" to the first bullet | yes |
A strong resume bullet starts with a past-tense verb ("negotiated"), while a requirements list names the skill as a noun ("negotiation"). Our matcher treats those as different words. So write the bullet with the verb, and use the posting's noun once in the same line, as the example above does with "stakeholder management". For the rest of the resume, see how to write an effective resume.
Preparing STAR answers for a saved job in HiredFolio
HiredFolio keeps each job's saved description in the job's page, next to the resumes you tailored for it. On that page, "Prepare for the interview" reads the saved description and a resume you choose. It returns the questions most likely for that role, eight by default, with a STAR answer built only from what the resume contains. When the resume has no evidence for a question, it says so and leaves that answer as a prompt for you to fill in, rather than inventing a story you would have to defend.
It costs one AI action and needs a saved job description to run. Treat the answers as notes to rewrite in your own words, then run them through the word budget and the rating logic above.
Save a job and prepare for its interview in HiredFolio
Key takeaways before your next interview
Turn each behavior in the posting's requirements into a "last, most or worst time" question, and attach one story to each.
Write each story at 150 to 250 words, with what made it hard in the first sentence and your own decisions in the action.
Rehearse the follow-ups, especially "could it have been prevented" and "what would you do differently".
STAR covers the example questions. For the rest of the interview: prepare the whole interview.
Read next
- Why do you want to work here? How to answer with what the job posting doesn't say
'How to answer "why do you want to work here": find company details others miss, see a worked example from an annual report, and read five sample answers.'
- Why should we hire you? How to answer, with 5 example answers
'How to answer "why should we hire you": three proofs from the job posting, a 150-word budget, and example answers based on real job postings.'
- What are your salary expectations? How to answer on the form and the call
'How to answer "what are your salary expectations" on an application form and a recruiter screen, with scripts, the state laws that apply, and a count of 243 real application forms.'