The STAR method, with five examples that actually land

Every interview prep guide tells you to use STAR — Situation, Task, Action, Result. Almost none of them tell you how to keep it from sounding scripted. The frame is fine. The execution is where candidates lose the room.

The compression rule

A STAR answer should sit in 90–120 seconds. Situation and Task together get about thirty seconds of context — just enough for the interviewer to picture the scene. Action is the meat: sixty seconds, focused on what you did, not what the team did. Result is fifteen to thirty seconds, and it must include a number or a concrete outcome.

If you spend a minute on Situation, you will run out of time on Action, and the interviewer will not get the part they are actually evaluating.

Five worked examples

1. Conflict with a stakeholder

"We were three weeks from launch and our biggest enterprise customer asked for a feature that would have slipped the date by a month..."

2. A time you missed a goal

"In Q3 my team committed to shipping the new pricing flow before the sales kick-off. We missed by two weeks..."

3. Leading without authority

"A cross-functional working group had stalled because nobody owned the roadmap. I was not the most senior person in the room..."

4. Disagreeing with your manager

"My VP wanted to cut the onboarding redesign from the quarter. I disagreed because our activation rate had dropped four points in the previous month..."

5. A failure you learned from

"I shipped a billing migration without a feature flag, and we double-charged 312 customers..."

Each of these examples shares a property: the Action section starts with a verb in the first person. "I called", "I drafted", "I asked." That is the signal interviewers are listening for.