If you're applying for an Australian Public Service (APS) role, selection criteria are the gatekeeper between your application and the shortlist. Unlike private sector resumes where a polished CV might suffice, government applications demand structured, evidence-based responses that directly address each criterion.
This guide breaks down exactly how to write selection criteria responses that panels actually want to read — with real examples, common mistakes to avoid, and a framework you can use for any APS level.
What Are Selection Criteria and Why Do They Matter?
Selection criteria are the specific skills, qualifications, and attributes an agency requires for a role. They're listed in the job advertisement and form the basis of how your application is assessed.
In the APS, applications are typically scored against each criterion by a panel of three assessors. Each criterion is usually rated on a scale of 1-5, and your response needs to demonstrate that you meet or exceed the requirement.
The reality: Most applications are filtered out at this stage. A well-written selection criteria response is the single highest-leverage thing you can do to land an interview.
The STAR Method: Your Framework for Every Response
The STAR method is the gold standard for structuring selection criteria responses. It stands for:
- Situation — Set the scene. Where were you working? What was the context?
- Task — What was your specific responsibility or challenge?
- Action — What did you actually do? Be specific and use "I" not "we".
- Result — What was the outcome? Quantify where possible.
Why STAR Works
APS panels are trained to look for evidence-based responses. They want to see that you've actually done the work, not just that you understand the theory. STAR forces you to provide concrete examples rather than vague claims.
STAR Example: Stakeholder Engagement
Criterion: "Demonstrated ability to build and maintain effective relationships with a diverse range of stakeholders."
Weak response: "I have strong stakeholder engagement skills and enjoy working with different groups to achieve outcomes."
Strong response (STAR):
Situation: While working as a Policy Officer at Services Australia, I was tasked with coordinating a cross-agency consultation on the new digital service delivery framework. The stakeholder group included representatives from six agencies, two industry bodies, and a community advisory panel.
Task: I needed to ensure all stakeholders felt heard while keeping the consultation on track against a tight four-week deadline.
Action: I developed a structured consultation plan with clear agendas for each meeting, created a shared document for stakeholders to submit written feedback between sessions, and held individual check-in calls with the three most vocal stakeholders to address their concerns privately. When two agencies had conflicting priorities, I facilitated a joint workshop to find common ground.
Result: The consultation was completed on time with 100% stakeholder participation. The final framework received endorsement from all six agencies, and the approach I developed was subsequently adopted as a template for future cross-agency consultations.
How to Write Each Section
Situation: Set the Scene (2-3 sentences)
Keep this brief. The panel doesn't need your life story — they need enough context to understand your example.
Do:
- Name the organisation and your role
- Provide enough context for the example to make sense
- Keep it relevant to the criterion
Don't:
- Write a paragraph about the organisation's history
- Include irrelevant details about your career path
- Use vague language like "in a previous role"
Task: Define Your Responsibility (1-2 sentences)
This is often the shortest section. Make it clear what was specifically yours to own.
Do:
- Use "I was responsible for..." or "My task was to..."
- Be specific about your scope
- Distinguish your role from the team's role
Don't:
- Confuse team achievements with personal responsibility
- Leave it ambiguous about what you specifically did
Action: Show Your Work (3-5 sentences)
This is the meat of your response. This is where you demonstrate capability.
Do:
- Use active verbs: "I developed," "I coordinated," "I implemented"
- Describe your thought process, not just the steps
- Show problem-solving and initiative
- Mention tools, frameworks, or methodologies you used
Don't:
- Use "we" when describing your personal contributions
- List actions without explaining why you chose them
- Skip the details — panels want to see how you think
Result: Close Strong (1-2 sentences)
Quantify wherever possible. Numbers are persuasive.
Do:
- Include metrics: time saved, money saved, percentage improvement
- Mention positive feedback or recognition
- Connect the outcome to the criterion
Don't:
- End with "it was successful" without evidence
- Fabricate or exaggerate results
- Leave out the result entirely (a common mistake)
Common Mistakes That Get Applications Binned
1. Being Too Generic
The problem: "I have excellent communication skills and can work effectively with diverse stakeholders."
Why it fails: This could be written by anyone. It provides no evidence.
The fix: Always include a specific example with context, actions, and results.
2. Writing a Resume Instead of a Response
The problem: "I have 5 years of experience in policy development, including 3 years at the Department of Health where I worked on the National Preventive Health Strategy."
Why it fails: This lists experience but doesn't demonstrate capability against the criterion.
The fix: Focus on what you did and achieved, not where you worked.
3. Using "We" Too Much
The problem: "We developed a new reporting framework that improved efficiency by 30%."
Why it fails: The panel can't assess your individual contribution.
The fix: Use "I" for your actions. You can acknowledge the team, but make your role clear.
4. Ignoring the Criterion Keywords
The problem: A criterion asks for "experience in stakeholder engagement" and you write about project management.
Why it fails: Panels score against the specific criterion. If you don't address it, you score zero.
The fix: Mirror the language of the criterion in your response. If it says "stakeholder engagement," use that exact phrase.
5. Writing Too Much or Too Little
The problem: 200-word responses lack depth; 800-word responses lose the panel's attention.
The sweet spot: 300-500 words per criterion for most APS applications. Check the application instructions — some specify word limits.
APS Level-Specific Tips
APS 3-4 (Entry Level)
At this level, panels are looking for potential and foundational skills. You don't need extensive experience — you need to show you can learn, follow direction, and deliver quality work.
Best examples to use:
- University projects or assignments
- Part-time or casual work
- Volunteer experience
- Internships
Language to use: "I demonstrated..." "I learned..." "I contributed..."
APS 5-6 (Mid Level)
At this level, you need to show independent judgment and some leadership capability. Panels want to see you can manage your own workload and contribute to team outcomes.
Best examples to use:
- Work projects you led or contributed to significantly
- Process improvements you initiated
- Training or mentoring you provided to others
Language to use: "I initiated..." "I coordinated..." "I recommended..."
EL1-EL2 (Executive Level)
At this level, you need strategic thinking and leadership evidence. Panels want to see you can influence decisions, manage complex stakeholder relationships, and drive organisational outcomes.
Best examples to use:
- Strategic initiatives you led
- Complex negotiations or consultations
- Organisational change you drove
- Budget or resource management
Language to use: "I led..." "I influenced..." "I shaped..." "I delivered..."
How Govy Makes This Easier
Writing selection criteria responses from scratch is time-consuming. Most people spend 2-3 hours per application, and that's before you factor in tailoring each response to the specific role.
Govy's AI-powered tools can help you:
- Generate draft responses based on your resume and the job description
- Structure your examples using the STAR method automatically
- Tailor your language to match the APS level and agency
- Save time so you can apply to more roles with better quality
The best part? You can try it free. No credit card required.
Quick Reference Checklist
Before submitting your selection criteria responses, run through this checklist:
- Each response uses the STAR framework
- You've used "I" not "we" for your contributions
- Results are quantified where possible
- You've mirrored the language of each criterion
- Responses are 300-500 words (unless otherwise specified)
- Each example is specific and evidence-based
- You've proofread for spelling and grammar
- The examples are relevant to the criterion being assessed
- You've shown your thinking process, not just the outcome
- Each response demonstrates capability at the level being recruited
Final Thoughts
Selection criteria responses are a skill, not a talent. The more you practice, the better you get at identifying strong examples and structuring them effectively. Every application you write builds your bank of examples for future roles.
Remember: panels read dozens of applications. The ones that stand out are specific, well-structured, and demonstrate genuine capability. Use STAR, quantify your results, and always tie your examples back to the criterion.
Your next APS role is one well-written application away.