STAR Method Mistakes: 10 Common Mistakes Candidates Make
By Rehearsa Team · 2026-07-29
The STAR method is the most reliable framework for answering behavioural interview questions — but only when you use it well. Most candidates know the acronym (Situation, Task, Action, Result) yet still lose points because of the same small execution mistakes made under pressure.
We reviewed thousands of practice sessions on Rehearsa and pulled the ten mistakes that come up again and again. Fix these and your answers will immediately feel sharper, more credible, and easier for an interviewer to score.
1. Spending 80% of the answer on Situation
This is the number one STAR mistake. Candidates set the scene for 90 seconds — company history, team structure, quarter of the year — then rush the Action and Result in ten.
Interviewers do not score context. They score what you did and what happened because of it.
Fix: Cap your Situation and Task at 20–25% of the answer. Two or three sentences is usually enough. If a hiring manager needs more context, they will ask. The Action should always be the longest section.
2. Saying "we" instead of "I"
"We shipped the release, we hit the numbers, we handled the escalation." The interviewer cannot tell what you actually did.
STAR answers must isolate your individual contribution, even when the work was collaborative. Team context is fine — team credit for your own decisions is not.
Fix: Every Action sentence should start with "I." I proposed…, I built…, I facilitated…, I decided to… Use "we" only for the surrounding context, then switch back to "I" the moment you describe what you personally did.
3. Skipping the Result — or making it vague
"…and it went really well" is not a Result. Neither is "the client was happy" or "we improved things a lot." Vague results are the single biggest reason strong stories score as average.
Fix: Close with a number, a comparison, or a concrete outcome. Percentage change, dollar impact, time saved, users affected, error rate reduced, retention delta, promotion earned, feedback received. If you truly have no metric, use a before/after ("Before, tickets took 4 days. After, they were closed same-day").
4. Picking a story that does not match the question
The STAR structure is only useful if the story actually demonstrates the competency being asked about. Candidates often reach for their favourite story regardless of whether it fits, which reads as generic.
A "handling conflict" question needs a story where there was real disagreement — not a story where you led a project that happened to have a difficult stakeholder.
Fix: Before you start speaking, silently name the competency the question is testing (leadership, conflict, failure, ambiguity, prioritisation, influence, resilience). Choose the story that most cleanly demonstrates that competency, even if it is not your most impressive achievement.
5. Rambling through Action steps with no structure
Once candidates reach the Action section, many just narrate what happened in chronological order for a full minute. The interviewer loses the thread and cannot remember what you did by the time you finish.
Fix: Break your Action into three clear steps — "First I… then I… finally I…" Three is the magic number. It is enough to show depth of thinking without becoming a monologue, and it gives the interviewer discrete moments to note down.
6. Choosing a story with no real challenge
STAR stories need tension. If the Situation is "we needed to launch a feature" and the Action is "so I launched it," there is nothing to score. The interviewer is looking for how you behave when things are difficult — not when they are easy.
Fix: Pick stories with a genuine obstacle: a tight deadline, conflicting stakeholders, a missing skill, a failed first attempt, an ambiguous brief, a resource constraint. If there was no obstacle, it is not a behavioural story.
7. Memorising a script word-for-word
Rehearsed answers sound rehearsed. When you memorise a paragraph, one forgotten line derails the whole thing, and the delivery goes flat because you are reciting instead of thinking.
Fix: Memorise the structure and the anchor points — the specific numbers, the three Action steps, the final result. Deliver everything in between in your own words each time. Practising the same story five times out loud with different phrasing beats memorising it once.
8. Using a story that is too old or too small
A story from a university group project when you have five years of professional experience signals that you have not done anything comparable at work. A story about organising a rota when the question is about leading through change signals that you have not led through change.
Fix: Prefer stories from the last 12–24 months, and match the scope of the story to the seniority of the role. Senior roles need stories about cross-team influence, ambiguity, and business impact — not individual task execution.
9. Failing to reflect at the end
Strong candidates finish a STAR answer with one short sentence of reflection: what they learned, what they would do differently, or how they have applied it since. This turns a good story into evidence of self-awareness — one of the highest-signal traits in senior hiring.
Fix: Add a single reflective closing line. "The main thing I took from that was…" or "Since then, I always…" One sentence. Not a second story.
10. Ignoring the follow-up
STAR answers almost always trigger follow-up questions. "Why did you pick that approach?" "What would you do differently?" "How did the team react?" Candidates who deliver a polished answer and then fumble the follow-ups undo the credibility they just built.
Fix: For every story you prepare, write three likely follow-ups and rehearse a 20-second answer to each. Interviewers use follow-ups to test whether the story is real. Being ready for them is what separates a memorised answer from a lived one.
Quick self-check before your next interview
Run every prepared STAR story through this list:
- Situation + Task under 25% of the answer
- Action uses "I" and is broken into three clear steps
- Result includes a number, comparison, or concrete outcome
- Story matches the competency being asked about
- There is a real obstacle in the middle
- One-sentence reflection at the end
- You have three follow-up answers ready
If a story fails any of these, rework it before you sit down in front of a hiring manager.
Practice the fix, not just the theory
Reading about STAR mistakes is easy. Catching yourself making them in real time — under pressure, on camera, with a question you did not expect — is what actually changes your interview performance.
That is exactly what Rehearsa is built for. Every practice session records your answers, scores them against a behavioural rubric, and shows you where the Situation ran too long, where you slipped into "we," and where the Result went vague. Fix those three things and most candidates jump a full grade in a single week.