How to Address Selection Criteria: STAR Examples for Australian Government Roles

What are selection criteria really assessing in government roles?

Selection criteria are the employer’s proof points that map to the capability framework for the role’s level. In the APS and most state and territory jurisdictions, those frameworks describe behaviours expected at each band—from entry level through to executive. The panel reads your responses to test not just whether you’ve done similar work, but whether you demonstrate the level of judgement, complexity and impact required now. That’s why generic duties or task lists rarely score well; assessors are looking for evidence of outcomes, influence and risk management at the advertised level.

Always start with the job pack. Decode the role by highlighting the verbs in each criterion, the stakeholders, the systems mentioned and any reference to work level standards. Then match your best evidence to those expectations. For any government job application Australia, assume your responses may be used to shape interview questions—so clarity, accuracy and alignment to the brief matter.

• Scan the position description for level cues (e.g., “operates with limited supervision” versus “leads through ambiguity”).
• Note repeated themes—these are your non‑negotiables to address explicitly.
• Prioritise examples with measurable outcomes, stakeholder complexity or risk managed at the advertised level.

How do you use STAR to structure a standout response?

STAR keeps you disciplined and easy to assess: Situation (brief context), Task (your responsibility), Action (what you did and how), Result (outcomes and what changed). Written well, STAR helps panels see your judgement and impact without making them hunt for it. Use first‑person active voice, and favour concrete verbs over broad claims. If the application limits characters or words, compress Situation and Task to a short opening line so you can allocate space to Action and Result, which is where scoring happens.

Before you write, pick one compelling story per criterion. If you need two, make each do a different job—one showing stakeholder influence, one showing delivery under pressure, for example. Close with a reflective line that links the result to the advertised role, signalling that you understand the operating context and can transfer the skill.

• Lead with a one‑line context: when, where, why it mattered.
• Spell out your personal contribution—avoid “we” unless you clarify your role.
• Quantify outcomes credibly (percentages, volumes, timeframes).
• Name the stakeholders and systems where appropriate, without breaching confidentiality.
• Finish with a link to the criterion: “This demonstrates…” to make the assessor’s job easy.

Which selection criteria examples work for common APS and state roles?

Below are concise STAR‑based selection criteria examples you can adapt. They illustrate level‑appropriate behaviours across popular capabilities. Replace organisation names and sensitive data with descriptors that protect confidentiality.

Communicates with influence (APS6 Policy Officer): Situation and Task: As the policy lead on a cross‑agency data‑sharing pilot, I had to secure agreement from three agencies with differing risk appetites. Action: I mapped each agency’s priority and risk thresholds, drafted a plain‑English issues brief with two options and convened a workshop to test assumptions. I pre‑briefed senior advisers to identify likely objections and prepared mitigation statements aligned to legislation and policy. Result: The group endorsed a single approach with staged safeguards; the Deputy Secretary approved the pilot on time. Stakeholder feedback noted the clarity of the brief and the practicality of the risk treatments.

Achieves results (APS5 Project Officer): Situation and Task: Our grants team faced a processing backlog ahead of a published milestone. I was responsible for clearing low‑risk applications within quality standards. Action: I built a triage spreadsheet to flag complete files, created two templated email responses to reduce rework, and negotiated with my team leader to batch approvals daily. I also cross‑trained a colleague on the triage process. Result: We cleared the low‑risk queue three days before the milestone with no increase in quality exceptions and improved applicant satisfaction based on fewer follow‑up calls.

Shapes strategic thinking (EL1 Manager): Situation and Task: My branch had fragmented reporting on program outcomes, making it hard for executives to direct investment. I needed to create a unified outcomes framework and secure adoption. Action: I led a short discovery, interviewing internal owners, reviewing contracts and mapping indicators to the portfolio’s purpose. I socialised a draft framework with Directors, incorporated their use‑cases, and built a light governance cycle with quarterly reviews. I secured a senior sponsor and ran two training sessions for analysts. Result: The framework was endorsed at the branch leadership meeting and is now used to prioritise initiatives; it informed a budget bid that re‑allocated funding towards the highest‑impact activities.

Supports productive working relationships (State Government, AO6): Situation and Task: A new ICT release risked disrupting frontline services in regional offices. I had to align ICT, operations and vendor timelines. Action: I created a weekly cross‑functional huddle, produced a one‑page readiness dashboard and negotiated a revised vendor deployment window to avoid school holiday peaks. I also arranged targeted training for regional champions. Result: The cutover occurred with minimal incident reports; post‑implementation review praised the early engagement and clear roles.

Delivers client service (Local Government, Customer Service Team Leader): Situation and Task: Complaints about wait times had risen. I was tasked with improving first‑contact resolution. Action: I analysed call drivers, updated the knowledge base and introduced a “warm transfer” protocol with specialist teams. I coached staff on probing questions and set up a daily stand‑up to share learnings. Result: First‑contact resolution improved across the quarter and average handling time stabilised without reducing quality scores.

Applies regulatory knowledge and judgement (Compliance Officer): Situation and Task: A regulated business submitted incomplete reports repeatedly. I needed to secure compliance while maintaining a constructive relationship. Action: I conducted a targeted engagement, explaining obligations and offering a clear rectification plan with deadlines. I coordinated with legal to ensure our correspondence was accurate, and I documented all decisions in the case management system. Result: The entity returned to full compliance within the agreed timeframe. The internal audit later referenced the file as a model of proportionate, well‑documented regulation.

Analyses and presents evidence (Graduate Analyst): Situation and Task: Our branch needed a short paper on a new policy proposal’s likely impacts. Action: I cleaned and merged two administrative datasets, applied a simple comparative analysis, and created a chart suite with clear caveats. I wrote a two‑page brief with options and risks, checked by a senior analyst. Result: The Division Head used the paper in a stakeholder roundtable; it shaped the decision to pilot before broader rollout.

If you are writing multiple responses for the same role, vary your evidence and avoid re‑using the same story across criteria. In most cases, depth beats breadth. One well‑chosen example that shows complexity, your judgement under constraint and a tangible result is stronger than three light anecdotes stitched together.

• Prefer recent examples at or above the role’s level; if older, show why they’re still relevant.
• If you lack public sector experience, use transferable examples from regulated industries, NGOs or large corporates.
• Name relevant frameworks or systems (e.g., risk frameworks, case systems) to anchor your credibility.

How do you tailor one story to different criteria without bending the truth?

Panels value consistency. It’s acceptable to reuse a strong scenario if you change the lens to match the criterion. The trick is to rotate emphasis so you’re not simply repeating the same response. Keep the core facts identical, but re‑weight the Action and Result to foreground the capability in question.

For instance, take a cross‑agency project. For “Communicates with influence,” emphasise how you framed options, handled objections and obtained buy‑in. For “Achieves results,” focus on planning, execution, risk management and delivery to time/quality. For “Supports productive working relationships,” highlight collaboration, conflict resolution and how you enabled others. Use a one‑sentence reflection at the end to link the outcome explicitly to the criterion.

• Use the same Situation/Task opening, then swap in different Action verbs aligned to the criterion.
• Change the metrics: for influence, cite approvals; for delivery, cite milestones; for relationships, cite stakeholder feedback.
• Keep dates, scope and risks consistent across versions to maintain credibility.

How do you evidence impact while protecting confidentiality?

Government work often involves sensitive information. You can still provide robust evidence without breaching confidentiality. Focus on scale, direction of change and decision points rather than naming restricted data or individuals. Where necessary, anonymise parties (e.g., “a large agency,” “a regulated utility”) and aggregate numbers.

Use verifiable, sensible quantification. If you can’t give exact figures, provide conservative ranges, timeframes or categories. Describe the baseline and the after state so the panel can see the delta your actions created. If work is ongoing, explain intermediate results or adoption milestones and what you will measure next.

• Replace specifics with safe descriptors (e.g., “sensitive client unit,” “classified dataset”).
• Use percentages, ranges or relative terms when exact numbers are restricted.
• Mention governance touchpoints you achieved (endorsement, sign‑off, audit clearance).
• Document tools and artefacts you produced (briefs, frameworks, dashboards, SOPs).

How should you prepare for interview probes on your written criteria?

Your written responses are the starting point for behavioural questions. Expect the panel to drill into what you did, why you chose that approach, what you’d do differently and how you handled risk and stakeholders. Preparation is about depth, not scripts: know your evidence so well you can flex it under questioning without contradicting yourself.

Build a small bank of stories per capability and practise out loud. Refresh the context, the decision you made, the alternatives you rejected and the measurable result. Bring a concise copy of your key STARs to the interview to anchor your memory if permitted. Be ready to provide a second example if the panel asks “another time you…” and to connect your evidence to the agency’s current priorities as described in the job pack.

• Re‑read your application and annotate each example with risks managed and options considered.
• Practise 90‑second and 3‑minute versions of each STAR for time‑boxed questions.
• Prepare a brief “so what” statement linking each story to the role’s level and criteria.
• If a question is unclear, ask to restate it—panels value clarity more than speed.

What mistakes sink otherwise-strong criteria responses—and how do you fix them?

Most weak responses fall into a few patterns: generic statements about being a “team player,” long descriptions of tasks with little about judgement or results, excessive jargon, and unsubstantiated claims. Another frequent issue is mis‑levelling—examples pitched below the advertised level, which suggests you may need more support than the role allows.

The fix is simple, if not always easy: choose better evidence and make it easy to assess. Trim background, expand decisions and outcomes, and translate technical detail into the business or community value it delivered. Mirror the language of the criterion without copying it, and conclude each response with an explicit line that ties your result to the capability the panel is assessing.

• Cut setup to two or three lines; spend most of your word count on Action and Result.
• Replace superlatives with specifics—names of stakeholders, artifacts delivered, approvals secured.
• Sense‑check level: are you setting direction (EL), optimising delivery (APS6), or executing with initiative (APS5)?
• Follow all instructions exactly—format, file type, and any page or word limits.