Every interview guide on the internet tells you to use the STAR method. Situation, Task, Action, Result. It is good advice, and it is not enough. STAR tells you how to organise an answer. It does not tell you what makes an answer worth listening to.

Here is what actually happens in the room. The interviewer has asked twelve people the same question this week. By the fourth candidate, every answer sounds the same: a mild problem, a sensible action, a tidy result. Nobody is lying. Everybody is forgettable.

The problem with a perfect story

Most candidates choose the example that makes them look best. That is the instinct, and it is the wrong one. A story where everything went well tells the interviewer almost nothing, because success is over-determined. You cannot separate your contribution from luck, from a good team, from a problem that was never hard.

What an interviewer is actually trying to work out is narrower than you think. They want to know how you behave when the situation is ambiguous, when you do not have authority, and when the first thing you tried did not work. Those three conditions are where real work lives. A story without any of them is a story about a task, not about you.

Choose the moment where you were uncertain

When you are asked to describe a time you solved a difficult problem, resist the urge to pick the biggest problem. Pick the one where you genuinely did not know what to do for a while.

Then say so. “For about two days I was working from the assumption that the delay was on the supplier side. It was not. I had misread the shipment dates.” That sentence does more for you than three paragraphs of competence. It tells the interviewer you can notice you are wrong, which is a much rarer skill than being right.

The risk people fear here is that admitting a mistake makes them look weak. In practice the opposite happens, on one condition: the story has to end with what changed. Not “I learned to double-check”, which is a non-answer. Something specific, like “I now confirm dates against the carrier’s system rather than the booking email, because the two disagree more often than you would expect.”

Give the number that costs you something

Results are where most answers go soft. “It improved efficiency.” “The client was happy.” “We hit the deadline.” None of these can be checked, and interviewers know it.

A number is better, but only if it is honest about scale. If you reduced processing time from forty minutes to twenty-five on a task that runs twice a week, say that. It is a small, true, verifiable result, and it is far more persuasive than an unquantified claim of transformation. Candidates who inflate get caught by the follow-up question, and the follow-up question is where interviews are actually decided.

Answer the question they asked second

Almost every behavioural question has a hidden second half. “Tell me about a time you disagreed with your manager” is not really about the disagreement. It is about whether you can hold a position without becoming a problem, and whether you can lose gracefully.

So the answer needs both halves. What you argued, and how you behaved once the decision went the other way. Candidates who only tell the first half sound combative. Candidates who only tell the second half sound like they have no views. The interviewer is listening for someone who has opinions and can still be managed.

Prepare fewer stories, not more

The common advice is to prepare an example for every competency on the job description. This produces a candidate who is rehearsing rather than thinking, and it shows.

Prepare four or five real situations from the last two years and know them properly. What you actually did, what you got wrong, what the numbers were, what you would do differently. Almost any behavioural question can be answered from a well-understood story, because the interviewer is not grading the scenario. They are grading how you think about it.

Four stories you can discuss under pressure beat twelve you can only recite.

One last thing

The best answers usually include a moment where the candidate stops and says “actually, let me correct something I just said.” That is not a stumble. That is someone doing the work in front of you, which is the only real evidence anyone has that you can do the work at all.

Rehearse the structure. Do not rehearse the words.