Why do interviewers ask behavioural questions?
Because how you handled a real situation is better evidence than how you say you would handle a hypothetical one.
“Tell me about a time you...” questions exist because of a simple premise: how you handled real situations in the past is better evidence than how you claim you’d handle hypothetical ones. Anyone can say they work well under pressure. A behavioural question forces you to prove it with a specific story — and the story reveals things a self-assessment never will: what you actually did, how you made decisions, whether you take ownership, and whether you learned anything.
Understanding this changes how you prepare. The interviewer isn’t hunting for the “right” answer to “tell me about a conflict with a colleague” — they’re listening for evidence. Specifically:
- Was this a real situation? Real stories have texture: names of roles, constraints, awkward details. Invented or heavily borrowed stories are smooth and generic, and experienced interviewers can usually tell.
- What did you do? Not your team — you. Answers that stay in “we” the whole way through leave the interviewer with no evidence about the person in the chair.
- Did your actions make sense? The reasoning matters as much as the action. “I escalated early because the deadline was at risk” shows judgement; “I worked really hard” shows nothing.
- What happened? An outcome, ideally concrete. Stories that trail off before the result feel unfinished because they are.
What is the STAR method, and how long should each part be?
Situation, Task, Action, Result: a sentence or two of context, most of the answer on your own actions, and a result to end on.
STAR — Situation, Task, Action, Result — is the standard structure for behavioural answers. It’s not a magic formula; it’s just the shape of a complete story told efficiently. Most STAR advice fails people in two ways: it doesn’t explain the proportions, and it doesn’t explain what belongs in each part.
- Situation — one or two sentences. The minimum context for the story to make sense: where you were, what was at stake. This is the part people overbuild. If you’re forty-five seconds in and still setting the scene, the interviewer has stopped listening.
- Task — one sentence. What you specifically were responsible for. This is where the story shifts from “we” to “I”.
- Action — the bulk of the answer. The decisions you made, in order, with the reasoning behind the important ones. This is what’s being assessed. Two or three specific decisions beat ten vague activities.
- Result — two or three sentences. What happened, with something measurable or observable if you have it, plus what you took from it. Ending on the result gives your answer a natural full stop — which is also the cure for trailing off or rambling into a second example.
As a rough guide, a well-proportioned STAR answer runs 60 to 120 seconds: about a quarter on situation and task, over half on action, and the remainder on result. If your situation is longer than your action, the answer is upside down.
How do I make a behavioural answer specific?
Replace every adjective about yourself with a decision you made or a result someone could check.
The single biggest upgrade available to most behavioural answers is replacing adjectives with evidence. Adjectives are claims about yourself: “I’m proactive”, “I’m a strong communicator”, “it was very successful”. They cost nothing to say, so they carry no weight. Specifics — numbers, decisions, consequences — are verifiable, so they carry all of it.
The test: could the sentence appear word-for-word in anyone else’s answer? “I’m a great team player” could. “I noticed our two newest members were duplicating work, so I set up a shared tracker and a ten-minute Monday check-in” could not. The second sentence is evidence; the first is decoration. When you review a practice answer — and a transcript makes this brutally easy — highlight every adjective you used about yourself and ask what evidence, if any, sits behind it. Then say the evidence and cut the adjective.
The same applies to results. “It went really well” is a shrug. “We delivered a week early and the client renewed” is an ending. If you don’t have numbers, use observable outcomes: the process was adopted by the other teams, the customer complaint was withdrawn, the event ran again the next year. And if the honest result was mixed — the project still failed, but you salvaged the client relationship — say so. Interviewers trust candidates who report mixed results far more than candidates whose every story ends in triumph.
What does a good behavioural answer look like?
The same story told with a timeline, your own decisions and a checkable result; two before-and-after examples follow.
“So in one of my group projects there was a person who wasn’t really pulling their weight, which was frustrating for everyone. I’m a pretty good communicator so I tried to sort it out and keep everyone motivated, and in the end we got the project done and it all worked out really well. It taught me a lot about teamwork.”
“In a four-person uni project last semester, one member had missed our first two internal deadlines, and we had three weeks left. I was coordinating the group, so I messaged him directly rather than raising it in front of everyone — it turned out he was juggling extra shifts and was embarrassed to say so. We moved his sections to the research tasks he could do on his own schedule, and I set up a shared doc so progress was visible without anyone chasing. He delivered his sections, we submitted on time, and the group gave the same peer-review marks across the board. What I took from it: address the person before the problem, and privately first.”
Notice what changed. The vague frustration became a concrete situation with a timeline. “I’m a pretty good communicator” disappeared — replaced by the actual communication decisions, each with a reason. “It all worked out really well” became a specific, checkable result. The rebuilt answer is barely longer, but every sentence is doing work.
“I’m a bit of a perfectionist, so I don’t make many mistakes, but one time I sent an email with the wrong attachment. I apologised and sent the right one and was more careful after that.”
“In my retail job I once processed a week’s roster with the old award rates after a pay change — I’d copied the previous template without checking it. Two staff were underpaid. When the first one flagged it, I checked the whole roster rather than just her shifts, found the second error, told my manager what had happened before she heard it elsewhere, and had payroll fix both in the next run. Since then I’ve never reused a template without checking what changed — and that habit has caught two other people’s errors since.”
Mistake questions deserve special mention because the instinct is to minimise — to offer a non-mistake (“I’m a perfectionist...”) or a trivial one. That sounds evasive. The question is really asking: do you take ownership, and do you have a system now? A real mistake, owned quickly, fixed thoroughly, with a durable habit at the end, is one of the strongest answers you can give in an interview.
How do I get better at answering behavioural questions?
Rehearse the conditions: real examples, answered out loud on camera against the clock, with the transcript reviewed after each one.
Knowing STAR and performing it under pressure are different skills. In the room, with an interviewer watching, structure is the first thing to collapse — situations balloon, actions blur, results vanish. The fix is the same as for any performance skill: rehearse the conditions, not just the content.
- Prepare stories, not scripts. Six to eight real examples, bullet-pointed. Each should flex to cover several question phrasings.
- Answer out loud, on camera, against the clock. Aim for 60 to 120 seconds. Speaking an answer is a different act from thinking it, and the recording shows you what the interviewer would have seen.
- Review the transcript against the structure. Where did the situation sprawl? Is there an “I” in the action? Did you finish on a result? Fix one thing per rep.
This loop is what Veracue automates: it generates behavioural questions from a real job description, you answer on camera, and the feedback scores the substance of your answer first — including whether the STAR structure actually held — alongside pace, fillers and eye contact. Honest feedback, so you walk in prepared.
Two answers are free when you practise your interview on camera with Veracue; the Pro, Interview Sprint and Premium plans add more answers, formal interviews and the Veracue Challenge.
What does Veracue see in behavioural practice answers?
A consistent pattern: situations that take most of the answer, a “we” that never becomes “I”, results that trail off, and fillers clustering where the answer was least prepared.
Described in general terms, from the practice answers people record on Veracue. The situation takes most of the answer and the action is a sentence. “We” runs through the whole story, so the interviewer never learns what the person did. The result trails off, or arrives as “it went well”. Answers read from a generated script that was written without a real example of the person’s score low on specifics whatever the delivery, which is why Veracue asks for one real situation before it writes one. And the transcript shows filler words clustering at the start of the action, the point where the answer was least prepared. All of it moves with practice; none of it is a trait.
Where does this advice come from?
From the sources below, and from what practice answers on Veracue show.
- Situation, task, action, result, Wikipedia: the STAR structure and where it came from.
- Job interview, Wikipedia: structured and behavioural interviewing, and the research on how well each predicts performance.
- Filler (linguistics), Wikipedia: what filler words are and why speakers use them.
- Speech disfluency, Wikipedia: restarts, repetitions and filled pauses in ordinary speech.
- CareerBuilder / Harris Poll survey, February 2018, the hiring managers’ survey on interview mistakes our research page cites.