Writing your application

Your written application is your chance to show the selection panel why you are suitable for the role. It should be tailored to the job, easy to read and focused on evidence. Most APS applications ask for some combination of a CV, short pitch, statement of claims, responses to selection criteria, answers to questions and referee details.

A strong application does not need to describe your whole career. It should use the most relevant examples to show how your skills, experience and potential match the job. Choose examples that show what you personally did, how you worked with others, what decisions you made and what outcome you achieved.

Tailor your CV

Your CV should make it easy for the panel to see your relevant experience. Include your work history, qualifications, training, key achievements and any licences, clearances or technical skills required for the role. Use plain language and where possible explain Defence roles in terms a civilian recruiter can understand.

For each recent role, focus on responsibilities and achievements that relate to the job ad. For example, describe the size of the team you led, the budget or resources you managed, the systems you used, the stakeholders you worked with, the risks you managed and the outcomes you delivered.

Write a clear pitch or statement of claims

A pitch, statement of claims or selection criteria response should explain why you are a strong match for the role. Start by identifying the main capabilities, duties and behaviours the job ad is asking for. Then choose examples that directly show those qualities.

Use headings if they help the reader follow your response. Keep sentences short and avoid long background descriptions. The panel is looking for evidence that you can do the job, not a full posting history.

Use the STAR method

The STAR method can help you structure clear examples:

• Situation: briefly explain the context.

• Task: describe your responsibility or role.

• Action: explain what you did, including decisions, communication and problem solving.

• Result: show the outcome, impact or lesson learned.

Where possible, include evidence such as timeframes, numbers, improvements, risks reduced, feedback received or services delivered. Results do not always need to be large or dramatic. They should show the difference your actions made.

Translate Defence language

Assume the panel may not know Defence terminology. Explain acronyms, rank responsibilities, unit structures, operational settings and technical terms where they are relevant. Replace internal language with clear descriptions of the work you did and why it mattered.

Choose strong examples

Good examples are recent, relevant and specific. They should show how you acted, not just what the team or unit achieved. If you use a Defence example, explain the context clearly enough for someone outside Defence to understand the challenge and your contribution.

• Use examples that match the duties and capabilities in the job ad.

• Show your personal contribution, not only the team outcome.

• Explain the level of responsibility, complexity and risk.

• Include outcomes, evidence or impact where possible.

• Avoid unexplained acronyms, Defence jargon and assumed knowledge.

Referees

Choose referees who can comment on the skills and behaviours needed for the role. They might be a current or former supervisor, manager, senior colleague or project lead. Ask permission before listing someone and provide them with the job ad, your application and the key examples you used.

Final check before submitting

• Have I answered what the job ad asks for?

• Have I stayed within the word or page limit?

• Have I used plain language and explained Defence terms?

• Have I shown outcomes and evidence?

• Have I checked spelling, grammar, document names and upload requirements?

• Have I submitted before the closing time?