Selection criteria · APS · Government
How to Structure a STAR Response for Public Sector Jobs
The framework, the proportions, the common mistakes, and a full worked example. STAR is the structure inside every credible selection criteria response — and most candidates get the proportions wrong before they even start writing.
In thirty seconds
- STAR (Situation, Task, Action, Result) is the structure that holds together almost every credible selection criteria response in Australian government recruitment.
- The proportions matter: roughly 15% Situation, 10% Task, 50% Action, 25% Result. Most candidates over-write the Situation and under-write the Action.
- "I" not "we" — assessors need to see your contribution, not your team's.
- The Result must be specific and measurable where possible. "Successful outcome" doesn't count.
- STAR isn't the only acceptable structure — CAR and CAO are commonly used in shorter responses where Situation and Task collapse together.
Selection criteria responses live and die on structure. Public sector hiring panels read hundreds of applications a year, and the candidates whose responses follow a clear, predictable structure consistently rank higher than candidates with the same underlying experience but worse organisation. The structure that nearly every successful response uses is STAR.
STAR isn't a magic formula — it's a way of forcing your example into the shape an assessor needs in order to score you fairly. They need context (where and when), accountability (what was your role), evidence (what you specifically did), and outcome (what changed). STAR delivers all four in roughly the right proportion. Get the proportions wrong and even strong examples score weakly.
The proportions matter most
Before any of the letters, this is the single most important thing about STAR: each section has a target word share, and the Action takes the most space. Most candidates get this backwards — they over-write the Situation (the setup) and under-write the Action (the actual evidence). The result is a response that reads like a story about a project rather than a demonstration of capability.
Target proportions for a STAR response
For a 250-word response, that's roughly 38 words on Situation, 25 on Task, 125 on Action, and 62 on Result. For a 500-word response, double everything. Use it as a guide, not a strict rule — but if your Situation is running past 25% of your word budget, you're spending too long on setup.
Each component, in detail
Situation · ~15%
Set the scene briefly and concretely
Two to three sentences. Give the assessor enough context to understand the example, and stop. Where were you, when, what was the broader environment, and what was the challenge or opportunity that triggered the example?
- Name the agency, branch, or organisation
- Give the timeframe (year or rough period)
- Indicate the scale or significance briefly (project value, team size, jurisdictional reach)
- Identify the challenge or opportunity that the rest of the response addresses
The trap to avoid: over-Situation. Candidates spend half their response setting up the context because the context feels important and the action feels obvious. The assessor doesn't need a full project briefing — they need just enough to understand the next three sections.
Task · ~10%
Define your specific responsibility
One to two sentences. The point of Task is to distinguish your personal accountability from the broader team objective. What were you specifically responsible for delivering?
- Use first person: "I was responsible for..." or "My role was to..."
- Name the deliverable, decision, or outcome you were accountable for
- If you led a team or coordinated stakeholders, name that explicitly
Some candidates merge Task into Situation and that's fine — what matters is that the assessor can clearly identify your accountability before reading your Action.
Action · ~50%
Detail what you did, in steps
This is the heart of the response and where most of your word budget should go. Walk the assessor through what you did, in roughly chronological order, with enough detail that they can see your judgement and approach — not just the outputs.
- First person verbs throughout: "I designed," "I led," "I negotiated," "I drafted"
- Three to six concrete steps that show your approach (not just "consulted stakeholders" — which stakeholders, on what, with what tools)
- Reference the policy frameworks, methodologies, or governance structures you used
- Name the decisions you made and why — judgement under uncertainty is what assessors are looking for
- If you collaborated, be explicit about your contribution within the collaboration
The most common Action mistake: vague verbs that don't show what you actually did. "Worked with stakeholders to develop the policy" is duty-list language. "Convened five stakeholder workshops, drafted three policy options informed by the workshop input, and presented the preferred option to the Assistant Secretary" is what panels score.
Result · ~25%
Show what changed because of your work
Two to four sentences. The Result is the part that converts your activity into evidence of capability. Without a credible Result, the response describes effort rather than impact.
- Quantify where you can — cost savings, time reductions, compliance outcomes, service improvements
- Name the decision, document, or action that came out of your work
- Reference recognition where genuine — awards, ministerial acknowledgments, panel feedback
- If the result was mixed, name the lesson learned — assessors value reflective practice
The metric trap is real here too. AI-inflated round percentages on every Result ("achieved 47% efficiency gain," "improved engagement by 35%") read as suspicious if they don't fit the seniority of the role. Real, defensible numbers always beat impressive-sounding fake ones — see the metric mirage for more.
A full worked example
Here's a complete STAR response for a fictional APS6 candidate addressing the capability "Achieves Results." About 320 words, with proportions roughly hitting the 15/10/50/25 target.
Capability: Achieves Results
Demonstrates the ability to plan, deliver, and report on outcomes that contribute to broader strategic objectives.
Situation
In 2023, while seconded to the Department of Education's National School Reform Branch, I was part of a small team responsible for delivering the Commonwealth's annual implementation report to all state and territory education ministers. The report was 13 weeks behind schedule when I joined, with significant gaps in jurisdictional data and an unresolved methodological dispute between Commonwealth and state analysts.
Task
I was tasked with leading the recovery of the report — completing the data collection, resolving the methodology disagreement, and producing a final document the Branch Head could clear for ministerial circulation within six weeks.
Action
I began by mapping the data gaps against jurisdictional contacts and identified that four of the eight outstanding submissions sat with state analysts who had been unresponsive to email. I shifted the engagement model to weekly 30-minute videoconferences, which moved three of the four submissions inside two weeks. To resolve the methodology dispute, I drafted a one-page options paper presenting three approaches with their respective trade-offs, circulated it to the disputing parties before our next working group meeting, and chaired the meeting toward a decision rather than a continued debate. I worked with the Branch's communications adviser to restructure the report's executive summary around three clear ministerial decision points, then led two rounds of internal clearance with portfolio policy advisers and the Branch Head's office.
Result
The report was cleared and circulated to ministers five weeks after I took on the recovery — one week ahead of the revised schedule. All eight jurisdictions submitted data, including the previously unresponsive state. The Branch Head's clearance email noted that the executive summary structure was "the clearest version of this report we've produced." The methodology approach I drafted has been adopted as standard for the 2024 and 2025 reports.
What makes this work: the Action is doing the heavy lifting. Each sentence in the Action shows judgement (mapping gaps, shifting engagement model, drafting options paper, chairing toward a decision). The Result is specific (5 weeks, all 8 jurisdictions, a quotable Branch Head comment, durable adoption). The Situation and Task are tight enough to set the scene without burning word budget.
The Action is where you score. The Situation tells the assessor what happened. The Action tells them what kind of public servant you are.
Common pitfalls
- Use "I" throughout — your specific contribution
- Spend the most words on Action
- Quantify the Result with real, defensible numbers
- Reference policy, governance, or methodology where relevant
- Name decisions and the reasoning behind them
- Match the seniority of the example to the level of the role
- Keep the language active, professional, and specific
- Use "we" — assessors can't score what your team did
- Spend half the response on the Situation
- End with vague results ("successful outcome," "positive feedback")
- Use buzzwords ("synergy," "stakeholder leveraging")
- Use the same example for every criterion
- Inflate metrics that don't fit your seniority
- Forget to name the agency or context
STAR variants — when to use each
STAR is the most common structure but not the only one. Several closely-related variants are widely used in APS and broader government recruitment, and you should match the variant to the response length and context.
Pick one and use it consistently across all your responses for a single application. Mixing structures within a pitch or set of criteria responses reads as disorganised — the assessor notices, even if they couldn't articulate why.
How STAR fits into the bigger application
STAR responses don't sit in isolation. They feed into three different application formats, and the context shapes how you write them:
- Individual selection criteria responses. Each criterion gets its own STAR response, typically 250–500 words. This is the older format, still common at state government and local council levels.
- Two-page pitches. Multiple capabilities are addressed across the body paragraphs of a single document. STAR examples are woven into prose rather than separated by headings. See how to write a 2-page pitch for APS roles for the full template.
- Behavioural interviews. The same STAR examples you've prepared for written responses become the spine of your interview answers. Practising them out loud is non-negotiable.
The strongest applications use the same STAR examples consistently across all three formats — written response, pitch paragraph, and interview answer — calibrated to the length and tone of each. That consistency is what panels reward; the candidate clearly knows their evidence cold.
The mindset behind a strong STAR response
The best STAR responses don't read as if the writer is recounting a story. They read as if the writer is presenting evidence — for an assessor's specific question — drawn from a clear example. The framework is just scaffolding; what matters is that every sentence either provides context, demonstrates capability, or evidences impact.
Candidates who internalise this stop writing about projects and start writing about themselves. The example becomes a vehicle for showing what kind of public servant they are: the judgement they bring, the decisions they make, the standards they hold their work to. That's what panels are reading for, and STAR is what makes it visible.
Read more
Senior writers who know the public sector
We write STAR responses, selection criteria, and APS pitches by hand
A senior writer with years of APS-specific experience interviews you for an hour, surfaces the right examples for each capability, and writes structured STAR responses calibrated to the role's level — APS, EL, or SES. Every response in your own voice, with the proportions right and the action front and centre. Federal, state, and local government across all major Australian jurisdictions. View our selection criteria service →
