Using STAR in Interview Questions

Behavioural interview questions are now standard practice across Australian recruitment — government, private sector, executive search, and graduate programs alike. They're built on a well-established premise: past behaviour is the strongest predictor of future performance. Researchers consistently find behavioural questions five times more predictive of job performance than traditional "tell me about yourself" or "what are your strengths" questions. That's why 87% of employers now use them.

STAR is the structure that lets you answer those questions well. It's not the only structure that works — but it's the one most interview panels in Australia are listening for, which means using it gives you the cleanest possible read on whether you've covered what they need to score.

This guide is the companion piece to how to structure a STAR response for public sector jobs — which covers written STAR responses for selection criteria. This one is about spoken STAR in live interviews. The structure is the same; the delivery is fundamentally different.

First, recognise when STAR applies

Humans are surprisingly limited in how we elicit information. There are essentially four ways an interviewer can ask you a question. STAR is the answer to one of them — and using STAR for the others will hurt your score.

The most common candidate mistake isn't getting STAR wrong — it's using STAR everywhere and turning every answer into a five-minute story. If the question is hypothetical, give your reasoning. If it's overview, give your worldview with brief examples. If it's binary, just answer it. Save STAR for behavioural questions where it's genuinely the right tool.

That said: many interviewers will ask hypothetical-sounding questions that are really looking for a STAR answer. "How do you handle conflict?" is technically overview, but most interviewers expect you to anchor your answer in a specific example anyway. When in doubt, lead with the framework ("In my experience, the approach that works best is X. For example, when I was at..."), and let the example do the work.

The framework, broken down for spoken delivery

Good vs bad: same question, two answers

The difference between a STAR answer that scores and one that doesn't is rarely about the underlying experience. It's about how the candidate organises and delivers it. Same question, two responses:

The strong answer isn't about a more impressive project. It's about specificity — named role, named company, named tactics, named outcomes. The weak answer leaves the interviewer with no evidence to score against.

The four spoken-STAR mistakes that cost interviews

Written STAR (selection criteria, pitches) and spoken STAR (interviews) share the same structure but have different failure modes. Four specific mistakes show up over and over in mock interviews:

• The runaway Situation. You start describing the context and don't stop. Three minutes in, you still haven't said what you did. The fix: practise saying the Situation in 20 seconds out loud. If it takes longer than that, your example is too complicated for the question.
• The "we" trap. Easier to slip into in speech than in writing. "We managed the project, we restructured the team, we negotiated with the supplier..." The interviewer can't score "we." They need to hear what you specifically did. Even when you led a team, name your decisions inside the team's work: "I decided to..." "I proposed..."
• The vanishing Result. Candidates run out of mental energy halfway through Action and trail off into "...so yeah, it worked out fine." A weak Result undoes a strong Action. Practise landing your Results with specific outcomes — even one quantified outcome, real and defensible, transforms how the answer reads.
• The freeze. You can't think of an example. Mind goes blank. The fix is preparation — see below.

Build a story bank before the interview

The single highest-leverage thing you can do for an interview is prepare 5 to 7 stories in advance — each one structured as a STAR, each one ready to deploy when the right question lands.

The capabilities to cover, broadly:

• A leadership story — when you led a team, made a difficult call, or stepped up under pressure
• A conflict story — when you handled disagreement well, with a peer, manager, or stakeholder
• A failure or learning story — when something didn't work, and what you took from it
• A tight deadline / pressure story — when constraints forced trade-offs
• A change or ambiguity story — when the situation shifted and you adapted
• A complex stakeholder story — when you navigated competing interests
• An achievement story — your strongest piece of work, ready to deploy when asked

The same story can do double or triple duty. Your "led a team through a tight deadline" example can answer questions about leadership, pressure, prioritisation, or stakeholder management — depending on which Action you emphasise. Build the bank, then practise reframing each story to fit different question types.

Practise out loud, not in your head

STAR sounds different when you say it than when you read it. The proportions you maintain on paper compress in your head and expand in your mouth — almost everyone goes longer when they speak than they planned to. The only way to fix it is to practise out loud.

What to actually do:

• Record yourself answering each question on your phone. Play it back. Time it. If you're over two and a half minutes, you've over-Situationed or over-Actioned. Cut.
• Practise with a real human if possible. Mock interviews with a colleague, partner, or career coach surface things you don't notice on your own — verbal tics, runaway sentences, the moments you stop making eye contact when you're improvising.
• Memorise the structure, not the script. Reciting memorised answers word-for-word reads as robotic and falls apart the moment the interviewer asks a follow-up. Know the story; vary the wording.
• Practise the awkward pause at the end. When you finish a STAR answer, the interviewer often stays silent for a few seconds while they finish writing. The silence feels longer than it is. Resist the urge to fill it. Let them ask the next question.

A note on AI interviews

The honest summary

STAR is a simple framework that becomes powerful when used deliberately. Most candidates know it exists; far fewer use it well. The candidates who do are usually the ones who've prepared a story bank, practised aloud, and learned to keep the Action front and centre while letting the Situation do less work.

The lesson that translates across every spoken-STAR situation: your job in an interview isn't to tell stories — it's to give the panel the evidence they need to score you against the role. STAR is just the scaffolding that makes the evidence visible. Build it deliberately, and the rest of the conversation gets easier.

Read more

---