Every interview-prep book teaches STAR. Situation, Task, Action, Result. It's been recycled in every career guide since the 90s, and for good reason — it gives a stumbling answer a shape. But sit in on enough mock interviews and you start to notice: candidates who follow STAR religiously often sound worse than candidates who've never heard of it.
Not because STAR is wrong. Because STAR, taught literally, encourages people to front-load the boring part and bury the interesting one.
Why STAR feels rehearsed
Listen back to your last mock answer. There's a good chance it started something like: “So back in 2023, I was working at a B2B SaaS startup as a senior PM…”
Two full sentences in and the interviewer has heard zero information that distinguishes you from the previous five candidates. Experienced interviewers tune out for the first twenty seconds. They're waiting for you to get to the thing.
The problem isn't the framework. The problem is the order. STAR teaches you to start with context, but in conversation, context is what you give after the hook, not before it.
The fix: front-load the friction
Here's the small refinement we teach inside Lyra. We call it FSAR, but the order matters more than the acronym:
- Friction — the one-sentence version of what was hard, at stake, or unusual.
- Situation — just enough context for the friction to make sense.
- Action — what you specifically did, with concrete verbs and decisions.
- Result — including the second-order result: not just the metric, but what it taught you.
Start with the moment you'd describe to a friend at dinner — not the moment you'd put in a status update.— Maya Chen, lead persona designer
A worked example
Same story, two structures. Read them out loud — the difference is most obvious as speech.
Standard STAR · 38s
“I was working as a product manager at Acme, and we had a feature called Smart Search that engineering built over six months. My manager asked me to run an analysis. So what I did was pull the analytics data, talked to five customers, and put together a recommendation. The result was we ended up sunsetting the feature.”
FSAR · 36s
“We'd spent six months building a feature, and three weeks after launch I had to recommend killing it. Context — I'm a PM at Acme, and Smart Search was our big Q2 bet. The numbers were quietly catastrophic: 2% of users tried it, 0.3% came back. I interviewed five returners, found a use case we never designed for, and reframed the team around it. The pivot shipped in Q3 and is now our second-highest revenue feature.”
Pick any STAR answer you've rehearsed. Cross out the first two sentences. The third sentence is almost always your real opening.
What about the result?
A useful trick: treat Result as two beats, not one.
- The metric — what actually happened. A directional answer beats a fake-precise number the interviewer will doubt.
- The second-order result — what changed for you, your team, or your understanding. This is where seniority shows up.
Practice this exact structure with Lyra.
Upload your resume and Lyra will surface the behavioural stories worth refining first.
When not to use STAR
Three common questions where STAR is the wrong tool:
- “How do you typically handle X?” This asks about your approach, not an event.
- “Walk me through your resume.” Chronology is the framework here.
- “Tell me about a time you disagreed with your manager.” These conflict questions need a fourth beat: the repair.
Bottom line
STAR isn't broken. It's just been taught as a recipe when it should be taught as a starting shape. The structural refinement is small — move the hook to the front, treat Result as two beats — but the difference in how an answer lands is not small at all.
Next week we'll cover the conflict-question variant, where the missing beat is repair. In the meantime: record yourself answering a behavioural question, play it back at 1.25×. If the first ten seconds bore you, they're boring the interviewer.
Back to all articles