The structure is fine. The delivery is the problem.
STAR - Situation, Task, Action, Result - is solid advice for behavioral interviews. The problem is that a lot of people internalize it so rigidly that you can hear the seams. "The situation was... my task was... the action I took was..." The interviewer's eyes glaze over because it sounds like a form being filled out, not a person telling a story.
You want the structure without the scaffolding showing. Here is how.
Lead with the stakes, not the setup
A robotic STAR answer opens with dry context: "So, the situation was that I was working on a team of five engineers on a payments system." A human one opens with why it mattered: "We were two weeks from launch and discovered the payment flow double-charged customers under a specific race condition."
Same situation. The second version makes the interviewer lean in. Give the context, but frame it around what was at stake, not as a neutral status report.
Spend your time on the Action
The most common STAR mistake is even time across all four letters. Situation and Task should be quick - just enough to understand the stakes. The Action is the part the interviewer actually cares about, because it is the part that reveals what you do. That is where the detail goes.
And keep it "I," not "we." Teams ship things, but the interviewer is hiring you, not your team. "We decided" tells them nothing about your contribution. "I proposed we add idempotency keys, and when the lead pushed back on the timeline, I..." tells them exactly what you bring.
Make the Result concrete and honest
End with a result, and put a number on it if you honestly can. "We caught it before launch and added a regression test so it could not recur" is good. "It would have hit roughly 8% of transactions" is better. But do not invent precision you do not have - a vague honest result beats a specific fabricated one, and experienced interviewers can smell an inflated number.
Have your stories ready, not scripted
Prepare five or six real stories that each demonstrate something different - conflict, failure, leadership, a hard technical call, a tight deadline. Know them well enough to tell them naturally, not well enough to recite them word for word. The goal is a person recalling a real experience, not an actor delivering lines.
The difference between a memorized script and a well-known story is audible. Practice them out loud until they feel like things that happened to you, which they are, rather than answers you are performing.