STAR — Situation, Task, Action, Result — is the scaffold that turns an interview anecdote into evidence the room can grade. A behavioral interviewer is not collecting stories. They are collecting a structured signal about what you actually did, in language they can compare to other candidates. STAR is the shape that signal arrives in.

When to use STAR

Use STAR for every behavioral prompt. Hiring training drills interviewers to look for the four pieces, so a STAR answer is the format they are listening for whether or not they name it.

Behavioral prompts (“tell me about a time you…”)
Conflict, leadership, or influence prompts
“Walk me through a project” prompts
Cross-functional collaboration prompts
Failure or mistake prompts

How to use it

Situation (15–20 seconds): set the scene. Name the role, the team, the timeline, and the constraint. Two sentences, no more.
Task (10–15 seconds): name the specific outcome the room is grading you on. Make it falsifiable — a number, a deadline, a stakeholder.
Action (60–70 seconds): this is the answer. Walk through what you did, in first person, in chronological order. Use “I” for your moves and “we” for the team’s moves; the interviewer is grading you, not the team. The Action step should carry about sixty percent of the airtime.
Result (10–15 seconds): close with what changed and how you know. Numbers if you have them, named outcomes if you do not. Acknowledge what did not work if the answer is honest.

Example

Them

Tell me about a time you had to give someone hard feedback.

On your HUD

In my last role, a senior engineer’s code reviews had become a bottleneck — average review latency was around five business days, and three product launches had slipped because of it.
I was the team lead on those launches, so I owned the date slip even though the reviews were not mine.
I sat with him for an hour and walked through three recent PRs where the comments had blocked work for over a week. I asked what was driving the depth of the review, and he named a quality concern from a previous role he was trying to prevent here. We agreed on a same-day turnaround for non-architectural changes, and on a one-page reviewer guide he could write once instead of relitigating per-PR.
Review latency dropped to under one business day in the next sprint and has stayed there. The doc he wrote became the team’s review guide.

What Kennan would surface in this moment, in the same first-person bullet format as the in-app HUD.

Common pitfalls

Front-loading the Situation. If you spend 90 seconds on context, the interviewer is hearing context, not action. Compress the setup to two sentences.
Drifting into “we.” Interviewers are grading you, not the team. Reserve “we” for collective outcomes and use “I” for your moves.
No Result. An answer that ends in the Action step reads as “I did a thing” rather than “I changed an outcome.” If you do not know the outcome, name what you would measure.

Where it comes from

DDI (1974) · Janz, J. Applied Psychology (1982) · McDaniel et al. meta-analysis (1994)

In your next meeting

Kennan watches for the conversational pattern this framework addresses and surfaces a first-person line you can read off your HUD, in the same shape as the example above. Frameworks are receipts; the user-facing output is a sentence, not a citation.