What Is the STAR Format and Why Does It Work?

STAR stands for Situation, Task, Action, Result. It's a framework for asking and evaluating competency-based, or behavioural, interview questions. The core premise is simple: the best available predictor of how someone will behave in a future role is how they have behaved in comparable situations in the past.

"Past behaviour is the best available predictor of future behaviour. STAR is the tool that surfaces it."

STAR works because it forces specificity. A vague question like "Are you good under pressure?" produces a vague answer like "Yes, I tend to stay calm." Neither tells you anything useful. A STAR question demands a real example from a real situation ”” and that's where genuine insight about how a person thinks, acts, and reflects actually lives.

ComponentWhat it coversWhat you're listening for
SituationThe context ”” when, where, what was happeningRelevance and complexity of the scenario
TaskTheir specific responsibility within that situationOwnership, scope, and accountability
ActionThe specific steps they personally tookDecision-making, skills, and approach
ResultThe outcome ”” what happened, what was learnedImpact, self-awareness, growth mindset
The most important letter is A. Candidates often spend 70% of their answer on Situation and Task ”” the context ”” and rush through what they actually did. Train yourself to probe the Action in depth. That's where the real evidence lives.

How to Ask STAR Questions as an Interviewer

STAR is a framework for structuring answers, but it starts with how you frame the question. Here's how to use it well:

Map questions to your competency framework

Every STAR question should be tied to a specific competency you're assessing. Don't ask STAR questions at random. Map them first: which four to six competencies matter most for this role? Write one or two questions per competency. Here are examples across the most common competencies:

CompetencyExample STAR question
Resilience"Tell me about a time you faced a significant setback at work. What happened and how did you respond?"
Leadership"Describe a situation where you had to lead a team through a period of uncertainty or change."
Problem-solving"Give me an example of a complex problem you had to solve with limited information or resources."
Communication"Tell me about a time you had to communicate difficult news to a stakeholder. How did you approach it?"
Collaboration"Describe a time when you had to work with someone whose approach was very different from your own."
Ownership"Tell me about a project you took from idea to completion. What was your role and what did you learn?"
Conflict resolution"Give me an example of a time you had a significant disagreement with a colleague or manager. What did you do?"

Ask the question, then be quiet

After asking a STAR question, stop talking. Don't fill the silence. Don't offer examples or suggestions. Let the candidate think. Interviewers who prompt too quickly are coaching rather than assessing ”” and coaching produces answers that reflect your leading rather than the candidate's genuine experience.

Probe when the answer is thin

Candidates frequently give partial STAR answers ”” strong on context, thin on specifics. Use targeted probes to draw out what you need:

  • On Situation: "Can you set the scene a bit more ”” how big was the team, what were the stakes?"
  • On Task: "What was your specific remit ”” as opposed to the rest of the team?"
  • On Action: "Walk me through exactly what you did, step by step." / "Why did you take that approach rather than the alternatives?"
  • On Result: "What was the measurable outcome?" / "What would have happened if you hadn't acted?"
  • On Reflection: "What would you do differently if you faced that situation again today?"

Watch for red flags in STAR answers

  • Saying "we" for everything in the Action section ”” never "I." This may indicate low individual ownership or discomfort taking personal credit. Probe: "What specifically did you do personally?"
  • Vague, hypothetical answers ”” "I would typically..." instead of a specific past example. Push back: "I'm looking for a particular time this happened. Can you think of a specific example?"
  • Results with no observable or measurable outcomes. Press for specifics: percentages, time saved, revenue, team size.
  • Inability to reflect critically on what went wrong or what they'd change. This can indicate low self-awareness, which compounds in every senior role.

Scoring STAR Answers Consistently

Without a scoring rubric, two interviewers hearing the same answer will evaluate it differently based on their own frame of reference, their own career history, and how they felt in the room that day. An anchored behavioural scale fixes this by defining what each score level means in observable terms.

Insufficient evidence

No specific example given, or example is entirely irrelevant to the competency. Candidate could not describe their individual contribution or outcome. Frequent use of "we" throughout the Action section.

Below expectation

Example provided but vague. Limited specificity on Actions taken. Outcome unclear or minimal. Little to no reflection on what they learned or would do differently.

Meets expectation

Clear, specific example. Individual Actions well-described. Positive outcome articulated. Basic level of reflection demonstrating awareness of their own impact.

Above expectation

Strong, relevant example with high-stakes context. Actions demonstrate clear judgement and initiative. Quantified or tangible outcome. Thoughtful reflection including acknowledgement of what was difficult.

Exceptional

Sophisticated example demonstrating significant impact, leadership, or complexity beyond the role level being hired for. Actions show strategic thinking. Outcome measurable and significant. Deep, nuanced reflection including honest acknowledgement of what could have been done better.

Aim for evidence, not performance. A polished, articulate answer that contains no specifics is less valuable than a halting, unpolished answer with clear concrete examples. Confidence in delivery is not a competency ”” unless you're hiring a presenter.

Common STAR Interview Mistakes

Even experienced interviewers make these consistently. Here are the ones most worth eliminating:

#MistakeWhat to do instead
1Asking hypothetical questions. "What would you do if..." is not a STAR question.Reframe: "Tell me about a time when you actually faced..."
2Accepting vague answers. "I dealt with a difficult colleague" is not a STAR answer.Probe for specifics every single time ”” no exceptions.
3Over-weighting the Situation. Candidates give five minutes of context and thirty seconds of Action.Redirect actively: "I'd like to focus more on what you personally did."
4Scoring after group discussion. The first strong opinion anchors everyone else.Write individual scores before any discussion begins.
5Forgetting the reflection. "What would you do differently?" is skipped when time is tight.Treat it as mandatory ”” it's often the most diagnostic part of the answer.

Building STAR Into Your Hiring Process

STAR is most powerful when it's embedded in a system, not used ad hoc by individual interviewers who've read a blog post about it. Here's how to operationalise it:

Map your competency framework per role level

Define four to six core competencies for each role family. These become the foundation for your STAR question bank. Be specific ”” "communication" is too broad. "Communicating complex technical information to non-technical stakeholders" is assessable.

Build a question bank, not a question list

For each competency, write two or three alternative STAR questions. Interviewers can choose one, but they all assess the same thing. This allows natural conversation while maintaining structure ”” the best of both.

Assign competencies to interviewers

In a multi-stage process, each interviewer owns specific competencies. No overlap. No blind spots. A candidate shouldn't answer the same question three times, and no competency should go unassessed.

Use a digital scorecard

After each interview, every interviewer completes a scorecard: competency, score (1”“5), and verbatim evidence ”” a direct quote or specific example from what the candidate said. Gut feel doesn't go on the scorecard. Evidence does.

Run a structured debrief

Share scores independently first. Then discuss divergence. A candidate who scores 5 from one interviewer and 2 from another has given different signals to different people ”” that's worth understanding before you make a decision. Make the hire or no-hire call based on the evidence, not the energy in the room.

Stafflon tip: Stafflon's recruitment module includes built-in interview scorecards, so every interviewer records STAR evidence and scores in real time ”” and you get an automatic, auditable hiring record for every candidate, without any extra admin.

References

  1. Schmidt, F. L., & Hunter, J. E. (1998). The validity and utility of selection methods in personnel psychology: Practical and theoretical implications of 85 years of research findings. Psychological Bulletin, 124(2), 262”“274. https://psycnet.apa.org/doi/10.1037/0033-2909.124.2.262
  2. Campion, M. A., Campion, J. E., & Hudson, J. P. (1994). Structured interviewing: A note on incremental validity and alternative question types. Journal of Applied Psychology, 79(6), 998”“1002. https://psycnet.apa.org/doi/10.1037/0021-9010.79.6.998

Make structured interviews part of your standard process.

Stafflon's recruitment module includes interview scheduling, scorecards, and candidate tracking ”” so your hiring process is consistent every time, for every role.

Start Free Trial →

Stafflon HR Team

Interview Techniques, Stafflon

The Stafflon HR team writes practical, evidence-based guides for HR managers, people leads, and founders building their people operations. Our content is grounded in established research and the day-to-day realities of running HR at fast-growing companies.