If you've applied for a government or corporate role in Australia, you've written to the key selection criteria — those "Demonstrated ability to…" statements that decide who gets an interview. What surprises many candidates is that the criteria don't disappear once you're in the room. The interview is the criteria, spoken aloud.

Handle that link well and the interview feels like a conversation you've already rehearsed. Miss it, and you can talk for an hour without ever answering the question being asked.

The panel is scoring against a rubric

Behind the friendly conversation, most panels are marking each answer against the criteria — often on a simple scale. That has two implications:

  • Every question maps to a criterion, even when it doesn't sound like it.
  • The panel can only score what you explicitly say. They don't award marks for what they assume you meant.

So your job is to make the scoring easy. Say the thing.

A simple way to structure each answer

For any behavioural question, use a criterion-led version of STAR:

  1. Name the capability the question is testing ("This is really about stakeholder management…").
  2. Give one specific example — a single, real situation, not a general habit.
  3. Show the actions that map to the criterion's language.
  4. State the result, and where you can, quantify it.

Read the criterion back to the panel in your own words before you answer. It signals you understand exactly what they're assessing — and it buys you three seconds to think.

Match their language, not your own

Selection criteria are written in a particular dialect — "engage stakeholders," "manage competing priorities," "achieve results in a complex environment." When your answer uses the same words, the panel's pen moves. When you translate everything into your own phrasing, they have to do the mapping for you — and busy panels don't always bother.

This isn't about parroting. It's about meeting them where the rubric is.

Prepare criteria, not questions

You can't predict the exact questions. You can predict the criteria — they're published in the role description. Build two strong examples per criterion before the interview, and you'll have an answer ready no matter how the question is worded.

The written application got you into the room. The interview is where you prove those criteria were true.