Practical guidance for ICT careers in government
What our consultants tell candidates every day — distilled into guidance you can act on before your next application.
Six areas that decide most ICT applications
Writing an ICT CV for government
Lead with capability statements, clearance level and program outcomes rather than tool lists. Name the agency, the program and the measurable result you contributed to.
Understanding security clearances
Baseline, NV1, NV2 and PV differ in depth of vetting and revalidation cycle. Always state your current level, sponsor and expiry — it changes which roles you can start immediately.
Preparing for panel interviews
Panels score against published criteria. Structure each answer around the situation, your specific contribution and the measurable outcome, then link it back to the criterion.
Contract versus permanent
Contract offers higher day rates, breadth of exposure and flexibility. Permanent offers leave, progression and long-term program ownership. We'll model both against your goals.
Addressing selection criteria
Where a brief lists criteria, respond to each one explicitly and concisely. Evidence beats adjectives — one concrete example per criterion is worth a page of description.
Starting strong in an agency
Learn the governance model, the assurance gates and who signs off. Delivery in government is as much about stakeholder cadence as it is about technical execution.
What a strong government ICT CV includes
- Two to three pages, reverse chronological, with a short capability summary up front
- Clearance level (if any) stated near the top
- Australian citizenship or work rights clearly noted
- Each engagement listed with agency, program, dates and your specific responsibilities
- Outcomes quantified — systems migrated, incidents reduced, releases delivered
- Certifications and frameworks relevant to the role, not an exhaustive list
Have a consultant review your CV
Send it through and we'll give you honest, specific feedback — whether or not we have a role for you today.