STAR Method Interview Questions

STAR - Situation, Task, Action, Result - is usually taught to candidates and rarely to the people interviewing them. This is the interviewer's version: what to ask, which step to probe, how to score what comes back, and when the format is the wrong tool.

What the STAR method actually is

STAR is a structure for behavioral answers: Situation, Task, Action, Result. The candidate sets the context, says what they were responsible for, describes what they personally did, and states how it turned out. It exists because unstructured behavioral questions produce stories with no locatable decision in them - a candidate can talk for four minutes about a project without ever saying what they did.

The structure is usually taught to candidates. It is less often taught to interviewers, which is where most of the value is: STAR is only useful if the interviewer probes each step, and the step most interviewers skip is Task. Without it you cannot tell whether the candidate led the work or watched it.

The step interviewers skip, and why it matters

Situation and Result are easy to give and hard to verify. Action is where candidates are most likely to slip into 'we'. Task - what specifically was this person accountable for - is the step that makes the Action checkable, and it is the one most panels never ask about.

A practical fix: after any answer, ask 'what part of that was yours?' and then 'what would have happened if you had not been there?'. Those two follow-ups do most of the work of the whole framework.

Ten STAR questions, and what to probe for

Question	Probe for
Tell me about a time you had to deliver something with less information than you needed.	What was unknown, and what they did to reduce the uncertainty before committing.
Describe a situation where you had to persuade someone senior to change course.	The actual argument used, not the outcome. Ask what the other person said back.
Walk me through a time you missed a target. What happened next?	When they knew, who they told, and what they changed. The Result here is the recovery.
Tell me about a moment you had to choose between speed and quality.	The specific trade-off and who else was consulted. Vague 'balanced both' answers are not answers.
Describe a time you inherited a mess.	How they triaged. The Task step is where weak answers collapse into describing the mess.
Tell me about a conflict with a colleague that affected the work.	Their own contribution to it. Ask what the colleague would say happened.
Give me an example of feedback that changed how you work.	The specific behavior change, and whether it lasted.
Describe the most complex thing you have had to explain to a non-expert.	The Action: what they actually said or drew, not that they 'simplified it'.
Tell me about a time you noticed a problem nobody else had noticed.	How they noticed, and what they did with it once they had.
Walk me through a decision you would make differently now.	Whether the new reasoning is genuinely better or just informed by the outcome.

Each of these is written to force a specific past event rather than a policy statement. The probe matters more than the question - a good question with no follow-up gives you a rehearsed story.

How to score a STAR answer

Score	What it looks like
Strong	Specific event, their own action clearly separable from the team's, a measurable or checkable result, and at least one thing they would do differently.
Mixed	Real event, but the action is described in the first person plural and the result is directional rather than concrete.
Weak	A policy or a hypothetical, or a story where the candidate is the only actor and nothing went wrong.

Score the evidence, not the delivery. A nervous candidate who names a specific decision and its consequence has told you more than a fluent one who narrates a project. The most common scoring error is rewarding narrative polish, which is a proxy for interview practice rather than for the job.

A worked example, scored

Step	What the candidate said	What it is worth
Situation	"We were three weeks from a launch and the analytics we were supposed to price against never arrived from the data team."	Fine, and cheap. Situations are the easiest part to give and tell you almost nothing on their own. Do not spend interview time here.
Task	"I owned the pricing recommendation. Two other people were working on the launch, but the number was mine to bring to the exec review."	This is the step that makes the rest checkable. Without it, every later 'we' is ambiguous. If a candidate skips it, ask directly: what part was yours?
Action	"I pulled six months of transaction data myself, sampled 200 accounts by hand to sanity-check the segments, and took a range to the review instead of a point estimate - with the assumptions written on the slide."	Strong. Specific, first-person, and it names a decision (a range, not a number) rather than an effort. The written assumptions are the detail that suggests it actually happened.
Result	"We shipped on the range. Two of the three segments landed inside it; the third was 20% off and we repriced it six weeks later."	Strong precisely because it is not clean. A candidate who volunteers the segment they got wrong is giving you a checkable result rather than a victory lap.

Question: "Tell me about a time you had to deliver something with less information than you needed." What follows is a real-shaped answer, broken into the four steps with what each one is worth.

Where STAR fails

It rewards preparation. Candidates who have practiced the format outperform candidates who have not, independent of ability - so treat fluency in the format as noise.
It suits some roles badly. For work that is continuous rather than project-shaped, candidates struggle to produce discrete Situations, and you end up penalizing the job rather than the person.
It collects successes by default. Ask explicitly for a failure, or you will hear ten wins and learn nothing about judgement under pressure.
It cannot detect a borrowed story. Nothing in the format distinguishes something the candidate did from something they watched a colleague do, which is why the Task probe matters.

Frequently Asked Questions

What does STAR stand for?

Situation, Task, Action, Result. The candidate sets the context, states what they were accountable for, describes what they personally did, and says how it turned out. Task is the step that makes the rest checkable, and it is the one most interviewers skip.

How many STAR questions fit in an hour?

Three or four with proper follow-ups. Each question needs two or three probes to get past the prepared version, which takes ten to twelve minutes. Ten shallow questions produce ten rehearsed stories.

Is STAR biased against candidates who have not practiced it?

Yes, and that is its main weakness. Fluency in the format tracks interview preparation rather than job ability. The correction is to score the evidence - specific action, checkable result - and explicitly ignore how neatly the story was packaged.

Does STAR work for junior candidates?

With adjustment. Allow situations from study, volunteering or side projects, and expect the Result step to be weaker because juniors rarely own outcomes. Weight Action and reasoning more heavily.

What should replace STAR when it does not fit?

For continuous rather than project-shaped work, ask about a typical week and probe the decisions inside it. For technical depth, a work-sample task shows more than any behavioral format.

Interview questions for other roles

Interview questions by role · Leadership interview questions · Build an interview scorecard