Behavioural Interviews: Using STAR Without Sounding Like a Robot

What a behavioural interview is actually doing

Behavioural questions start with a recognisable stem. Tell me about a time when. Describe a situation where. Give me an example of.

The premise is that past behaviour predicts future behaviour better than hypothetical answers do, which is broadly supported and is why the format has spread everywhere.

What matters for you as a candidate is the mechanics. At most structured employers the interviewer is not forming a general impression. They are scoring you against a defined list of competencies, often with a form in front of them, and they need specific evidence to justify a mark. An answer that leaves them nothing to write down scores badly however pleasant the conversation was.

STAR, and why it goes wrong

Situation, task, action, result. It is the standard structure and it is genuinely useful, because it stops people missing the parts interviewers need.

It goes wrong when candidates treat it as a script and announce the sections aloud. "So the situation was, and then my task was" makes an answer sound processed, and it wastes time on the least valuable parts.

The proportions are the thing nobody tells you. Situation and task together should be about twenty percent of the answer, just enough context to follow. Action should be roughly sixty percent, because that is the only part that is about you. Result gets the remaining twenty.

Most candidates invert this, spending ninety seconds explaining the company's org structure before reaching anything they did.

The action step is the whole answer

When interviewers say a candidate was vague, this is almost always the section they mean.

The trap is describing what happened rather than what you did. "The team worked through the weekend and we got it shipped" describes an event. It contains no information about you.

Say what you decided, what you chose not to do, who you spoke to, and what you did when the first approach failed. Decisions are the evidence. A description of activity is not.

Use "I" for your own actions and "we" only where the collective is genuinely accurate. Candidates over-correct toward "we" out of modesty and make themselves unscoreable, because the interviewer cannot tell which part was theirs.

One clear takeaway: if an interviewer cannot tell what you personally decided, they cannot give you the mark.

Results, including when the result was bad

End with what happened, with a number where you honestly have one and a plain description where you do not.

Do not invent a percentage. Interviewers ask how it was measured, and a vague answer to that question undoes the story.

Not every example needs a triumphant ending. Questions about failure, conflict and mistakes explicitly want the opposite, and a candidate who turns every answer into a success is either unlucky in their choice of examples or not being straight. Where the result was poor, say what you learned in a way that is specific enough to be checkable.

The follow-up is where the assessment really happens

Good interviewers do not accept the first answer. They probe.

What would you do differently. What was the hardest part. Who disagreed with you. What did your manager think. How did you know it worked.

This is deliberate. A rehearsed or borrowed story survives the first telling and falls apart under three follow-ups, because the candidate has not lived the detail. A real story gets richer, because there is always more of it.

Which is the practical argument against memorising answers. Prepare the material and know it deeply enough to go sideways, rather than preparing a paragraph you can only deliver in one direction.

Building a set of examples that covers the ground

Interviewers reuse a small set of competencies, so a modest number of examples covers most questions.

Prepare six to eight, aiming to cover: delivering under pressure, disagreeing with someone, a failure that was partly yours, changing your mind, improving something unprompted, persuading someone who did not report to you, and handling an unclear or shifting brief.

Write each as notes rather than prose. Situation in one line, then bullet points for what you did, then the outcome and what you would change.

Chase the detail while you prepare, because the specifics are what you will have forgotten. System names, timeframes, who else was involved, what went wrong first. Recovering that detail is the real work, and it is what makes the answer sound like a memory rather than a claim.

Matching examples to the role

The same story can be told to emphasise different things, and choosing which is part of preparation.

Read the job description for the competencies it implies. A posting emphasising stakeholder management wants your persuasion and conflict examples. One emphasising delivery wants pressure and prioritisation. One for a leadership role wants examples where the work happened through other people.

Where you are early in your career and short of workplace examples, university projects, part-time work and volunteering all count, provided the situation was genuinely difficult. Interviewers are assessing behaviour, not employment status.

Our career guides set out what each role's interviews concentrate on, which is a faster way to choose examples than guessing.

Competency frameworks, and reading them off the posting

Structured employers usually score against a published set of competencies, and a surprising amount of that is visible before you walk in.

Large organisations, particularly in the public sector, financial services and consultancies, often name their framework in the job advert or on their careers site. Where they do, the interview will follow it closely and each competency will get its own question.

Where they do not, the job description still leaks it. The behaviours listed under requirements, the ones written as qualities rather than skills, are usually the competencies in disguise. Collaboration, resilience, customer focus, commercial judgment.

Map one prepared example against each before the interview. If a competency has no example, that is the gap to fix now rather than discover on the day.

Video interviews and one-way recordings

Behavioural questions increasingly arrive as a recorded one-way interview, where you read a question on screen and record an answer with no interviewer present.

These are harder than they look, and mostly for mechanical reasons. There is no interviewer reacting, so you lose the signals that normally tell you to wrap up. There is often a time limit and sometimes only one take.

Prepare differently. Have your notes on paper beside the camera rather than on screen, so your eyes stay roughly in the right place. Answer to the lens, not to your own image. Keep answers tighter than you would live, because there is no interviewer to interrupt a digression.

Where a practice question is offered, use it properly rather than skipping through. It is the only chance to hear what you actually sound like on the recording.

Mistakes that cost marks quietly

• Answers that run past four minutes. The interviewer stops absorbing and starts waiting. Two minutes is the target.
• Reusing one story for every question. It signals a thin career even when the career is not thin.
• Hypotheticals instead of examples. "I would usually approach that by" is not an answer to "tell me about a time".
• Blaming. Conflict examples where the other person was simply wrong tell the interviewer how you will describe your future colleagues.
• Choosing an example that is too small. A minor inconvenience presented as a challenge suggests you have not faced a real one.

Practising in a way that transfers

Reading your notes creates a false sense of readiness. Saying a story out loud is a different skill and it is the one being tested.

Say each example aloud once, timed. Then have someone ask you follow-ups you have not anticipated, because handling the probe is what you are actually training for. Our interview prep tool produces role-specific questions when there is nobody to practise with.

Questions people ask

What is the STAR method?

Situation, task, action, result. It is a structure for behavioural answers, best used as a memory aid rather than recited aloud, with the action step taking most of the time.

How long should a behavioural answer be?

About two minutes. Longer than four and the interviewer has stopped listening, usually because the setup was too long.

Should I say I or we?

I for your own decisions and actions, we only where the collective is genuinely accurate. Over-using we makes your contribution impossible to score.

How many examples should I prepare?

Six to eight covering different competencies. Interviewers reuse a small set of themes, so a modest number of well-known examples covers most questions.

What if I have no work examples yet?

Use university projects, part-time jobs or volunteering. What is being assessed is the behaviour, and a genuinely difficult situation qualifies regardless of where it happened.

Related reading

• Cover Letters: When They Matter and What to Write
• AI Resume Builders: What They Fix and What They Cannot