How to Answer Selection Criteria
Few parts of a job application cause more frustration than selection criteria. Updating a resume is one thing. Sitting down in front of a blank page and writing five or six separate responses about yourself, each one expected to prove you can do the job, is something else entirely. If you've ever stared at a criterion thinking "I honestly don't know what they want me to say here," you're not alone.
The good news is that selection criteria aren't as complicated as they first appear. Most people don't struggle because they lack the experience. They struggle because they misunderstand what the employer is actually asking for, and once that clicks, the rest tends to fall into place.
Reality Check
Selection criteria aren't asking you to rewrite your resume in paragraph form.
The panel already has your resume. What they want from your response is evidence: a specific, real example that proves you've actually demonstrated the capability they're asking about. A response that just summarises your background, without an example attached, rarely convinces anyone, no matter how qualified you genuinely are.
What employers are actually assessing
Many people treat selection criteria as an extra hurdle, designed to make the process harder than it needs to be. That's not quite what's happening. A panel already has your resume, so what they're actually trying to work out with these responses is whether you can do a specific thing in practice, not just whether you've held a job title that sounds relevant. When an employer asks for evidence of stakeholder management, problem solving, or communication, they want to see the skill in action, not a claim that you have it.
That's why a strong response reads less like a summary of your career and more like a short case study. The panel isn't looking for a list of things you're good at. They're looking for proof.
How STAR actually works
If you've researched selection criteria before, you've come across the STAR framework: Situation, Task, Action, Result. There's a good reason it gets recommended so often: it gives you a simple structure for telling a complete story, and it's what most Australian public sector guidance points to as well.
The mistake isn't ignoring STAR. Almost everyone's at least heard of it by now. The problem is usually how it's applied: spending three-quarters of the response setting the scene and leaving only a sentence or two for what you actually did. While there's no single official formula, a useful rough guide is to weight it heavily toward Action: around 10% Situation, 10% Task, 60% Action, and 20% Result. If your response spends more space describing the background than describing your own contribution, that's usually the first thing worth fixing.
Where responses tend to go wrong
Describing responsibilities instead of evidence. Imagine a criterion asking for strong communication skills. A weak response might say something like "I have excellent communication skills and regularly worked with internal and external stakeholders." There's nothing technically wrong with that sentence, but it doesn't actually prove anything. A stronger version might describe leading the rollout of a new system, coordinating five business units with competing priorities, running weekly stakeholder workshops, and delivering on schedule without disruption. The difference isn't length. It's that the second version gives the panel something they can actually assess.
Reusing the same example without changing the angle. There's nothing wrong with drawing on one strong project more than once, but telling the exact same story every time signals a narrow evidence base rather than broad capability. The same project can demonstrate leadership in one response and problem-solving in another, depending on which part of it you emphasise.
Skipping or generalising a criterion. If the application asks for five criteria, all five need a direct answer. A vague response, or one that talks around the topic without a concrete example, tends to score poorly even when the real experience is there, because the panel can only assess what's written down, not what they're left to assume.
Worrying too much about word count. If there's a stated limit, follow it. If there isn't, around 250 words per criterion is a reasonable target, enough to explain a specific example clearly without padding it out. The goal isn't to write more. It's to give the panel enough evidence to assess you with confidence.
What you can do next
Before submitting your responses, it's worth checking each one against a few honest questions: does this include a specific, real example rather than a general description of your experience? Is most of the response actually about what you did, not just the background? Have you stated a clear outcome? Have you answered every criterion the application asked for, without skipping or softening any of them?
If you're answering "not quite" to more than one of those, that's usually where a response is losing marks, and it's a presentation problem far more often than it's a genuine experience gap.
How Vistr helps
Strong selection criteria responses don't really start with writing. They start with knowing which parts of your experience are actually the strongest evidence for a given criterion, and that's often the hardest part to see clearly on your own.
Vistr's Job Match Analysis compares your resume against the job description first, highlighting where your experience already demonstrates the capabilities the employer is asking about. From there, the Selection Criteria Writer helps turn that evidence into structured responses, built around your real examples rather than a blank page or a generic template. Analyse first, then write, in that order.
