Job Profile Template for Government ICT Roles
Fill this job profile template for Australian Government ICT roles, then map role, clearance, location and timing to BuyICT evidence.
A detailed ICT job title can still be a poor description of the work. The Australian Bureau of Statistics distinguishes occupations by skill level and skill specialisation, including the knowledge, tools, materials and services involved, rather than the employer's preferred title. For Australian Government ICT recruitment, a profile built around Azure or Python alone leaves too much unanswered.
A useful job profile template connects an outcome, delivery conditions and candidate evidence to a specific opportunity. Build one profile per live BuyICT role, with each field traceable to the notice. Then record permission for the particular disclosure before anyone shares a CV.
Table of Contents
- Fillable Government ICT Job Profile Template
- Walk Role Clearance Location and Timing on One Notice
- How to Classify the Role and Weight Each Skill
- Record Consent Before a CV Is Shared
- Check the Profile on One Live Notice
Fillable Government ICT Job Profile Template
- Field — What to write — Example entry — Check against the notice
- Role and outcome — Outcome the person delivers, not a product brand — Run a secure cloud platform for a service team — Role wording in the notice
- Occupation family — One recognised APS digital family — Cloud engineer — Role family and key skills in the notice
- Clearance — Baseline, NV1 or NV2, and whether it must already be held — NV1, must already be held — Clearance stated in the notice
- Location — Delivery state, and whether the ACT is the only site — ACT only — Delivery location stated in the notice
- Timing — Notice close, start window and engagement length — Closing date, start window, term length — Closing time and engagement dates
- Work pattern — Headcount, full or part time, and on-site days — One role, full time, on-site days as stated — Headcount and working arrangement
- Mandatory capabilities — Skills needed to deliver, each with a currency window — Infrastructure as code, used within the last two years — Skills listed in the notice
- Evidence examples — Production system, scale, security obligation or stakeholder outcome — Pipeline supporting a production service at stated scale — Duties a CV can be scored against
These are illustrative entries, not requirements from an actual opportunity. Replace them with the notice's wording, and label any recruiter-proposed currency window for confirmation rather than presenting it as a buyer requirement.
Complete the delivery fields first
Start with role and outcome. For a government software engineer role, describe the service or software the person must deliver. Put .NET/C#, Java or Python in the capability field only when the notice connects that technology to the work.
Next, select the occupation family. The APS Data, Digital and Cyber Workforce Plan lists enterprise architects, cyber security analysts, IT and data architects, DevOps engineers, and business and systems analysts among its ten most in-demand roles. It also identifies Digital and ICT, together with Portfolio, Program and Project Management, as two of the three most significant critical-skills shortages across APS agencies.
Use those distinctions to separate architecture, implementation, analysis and delivery management. Other relevant families include software engineer, cloud engineer, data analyst and data engineer. Don't put unrelated responsibilities into a broad ICT consultant category just because they share a technology stack.
Complete clearance, location and timing directly from the notice. Keep the required clearance separate from whether the candidate holds it. Record an engagement's initial term separately from any extension options, so the profile doesn't imply that optional work is guaranteed.
Make capabilities assessable
For work pattern, capture the requested headcount, full-time or part-time arrangement, and attendance expectations. Don't translate flexible working into remote working unless the notice says that.
For mandatory capabilities, name the activity and the required recency. Infrastructure as code is more useful when paired with the environment, delivery responsibility and an agreed currency window. If the notice gives no window, record that it isn't specified and seek clarification where recency affects assessment.
Finish with evidence examples. Ask for a production deployment, the candidate's responsibility, the operating scale and the result. A finished profile should let the recruiter tick every row against the notice, rather than infer suitability from a collection of product names.
Practical rule: Keep the notice reference and exact supporting passage beside each field. If you can't locate the support, mark the field unconfirmed.
Walk Role Clearance Location and Timing on One Notice
Open the notice and its attachments beside the profile. Use the current notice as the reference, not an old agency advertisement or a candidate's recollection of a similar engagement.
Use this sequence to extract the delivery conditions before screening CVs.
Extract the visible fields
- Role. Write the outcome the buyer describes, then name a single occupation family. If the notice requests separate architect, developer and delivery-manager positions, create separate profiles. If it combines those duties in one position, preserve that scope and flag the combination for clarification rather than rewriting it.
- Clearance. Copy the named level, whether Baseline, NV1 or NV2, and the wording about when it must be held. A missing clearance field is unknown, not Baseline. Use our guide to security clearance jobs in Australia for related employment context, but don't substitute general guidance for the opportunity's conditions.
- Location. Record the permitted state or territory, delivery site and attendance conditions. Mark ACT only only when the notice allows no alternative.
The APS Data, Digital and Cyber Workforce Plan 2025–30 records 7,876 current APS ICT and digital employees, with 58.3% in the ACT; it also reports that 87% of ICT and digital vacancies include the ACT, while 40% advertise the ACT as the only location. These are the plan's published figures, so confirm the current edition before reusing them.
For matching, the implication is straightforward. A Sydney-based candidate who won't attend Canberra isn't ready for an ACT-only engagement, however closely their technical experience aligns.
- Timing. Capture the closing date and time, expected start window and engagement length. Preserve the notice's time zone. Keep candidate availability in a separate field so you can compare it with the requested start rather than overwrite it.
- Final check. Read the extracted conditions together. Resolve contradictions between the notice and agency ad before treating them as the same actionable role.
Repeat the check without inventing a live opportunity
Say an open notice requests a cloud engineer to operate a secure platform, requires an existing NV1 clearance, specifies ACT-only delivery and gives a start window. Copy those conditions into the profile, then compare the candidate's confirmed circumstances.
A candidate who meets the technical duties but can't start within that window needs clarification, not a higher skills score. Record the outstanding issue and hold the submission until the buyer's requirement or the candidate's availability is confirmed.
A strong technical match doesn't cancel an unmet delivery condition.
We match tender-panel agency ads to each BuyICT opportunity using evidence on role, clearance, location and timing. Use the same evidence when reviewing the connection yourself, especially when an ad summarises rather than reproduces the notice.
Use the walkthrough alongside the notice, pausing to record each field.
How to Classify the Role and Weight Each Skill
Classification and technical suitability answer different questions. Classification describes the responsibility and work context; technical assessment establishes whether the candidate can deliver the required work. A long technology list answers neither question reliably.
The Australian Public Service Work Level Standards describe classification characteristics including leadership and accountability, management diversity, stakeholder management and job context. Use them to calibrate the duties, not to assign seniority from a title such as lead or principal.
For labour-hire work, distinguish an explicit APS-equivalent requirement from your own analytical mapping. Don't turn a contractor role into an APS employment classification unless the notice establishes that relationship.
Map duties before adding requirements
Write each duty as an observable result. An architecture duty might require the person to document a target state, resolve integration trade-offs and obtain stakeholder agreement. Listing Microsoft Azure, Kubernetes and Microsoft 365 doesn't show who makes decisions or carries accountability.
Use a classification worksheet with these checks:
- Outcome-based duty. State the result and the system, service or programme affected.
- Level characteristic. Identify the leadership, judgement, stakeholder interaction or work context the duty requires.
- Essential requirement. Explain what the person must already be able to do.
- Observable evidence. Name an acceptable delivery example, decision record or production responsibility.
- Necessity check. Remove criteria that don't support the actual duties.
The APS merit principle requires assessment against work-related qualities genuinely needed for the role. Apply that discipline to both classification-specific and technical requirements: an architect should demonstrate accountable design decisions, not merely familiarity with cloud products.
A generic certification or a round number of years can obscure that distinction. Retain either when the notice requires it, but don't add it as a convenient substitute for assessing complexity, independence or delivery responsibility.
This diagram separates the classification decision from the capability assessment.
Weight the capability rather than the keyword
Jobs and Skills Australia's recruitment trends in the IT industry reports an average recruitment-difficulty rate of 44% for ICT Professionals over 2020–21 to 2025–26, with employers more often identifying insufficient technical skills than too few applicants. That distinction supports assessing demonstrated capability rather than expanding the applicant list.
Use the following weighting rules as an assessment method, not as permission to override explicit mandatory conditions.
- Requirement — How to treat it — Weight in a match
- Scarce skill the duty cannot start without — Mandatory, with a stated currency window — Heavy
- Clearance the notice says must already be held — Gate, not a preference — Heavy
- Adjacent tool or language — Trainable if production evidence is close — Light
- Named product when the duty is the outcome — Desirable wording, not a fail — None
- Round years of experience or a generic certificate — Keep only if a duty needs it — None
A gate must remain a gate. A weighted technical score mustn't compensate for a clearance condition that the notice makes mandatory. Likewise, a named product stays mandatory when the buyer explicitly requires it, even if your preferred assessment would accept alternatives.
For trainable requirements, consider adjacent evidence carefully. A candidate's production deployment experience may justify further assessment even when their CV names a different pipeline tool. It doesn't establish competence automatically.
Distinguish a capability gap from a wording gap
Ask the candidate what they delivered, what they personally did, which constraints applied and when they last performed the work. Record the answer beside the criterion, along with the assessment method. Use evidence missing when you haven't established capability, rather than recording capability absent.
For candidates who need help presenting genuine experience clearly, GetTheCall's guide to match your resume to the job description provides a practical companion to the assessment. The objective is accurate alignment, not inserting unsupported keywords.
Our guide to skills-based hiring provides related context for evaluating delivery evidence. Keep the profile's decision trail specific enough that another recruiter can understand why a capability was accepted, rejected or left unresolved.
Apply the same standard to emerging AI requirements. Include artificial intelligence or machine learning only where the notice's outcomes require them, and specify the relevant implementation, evaluation or operational evidence. Review the profile whenever scope, technology, clearance or location changes.
Record Consent Before a CV Is Shared
A completed employer profile isn't permission to disclose a candidate's information. Recruitment involves personal information, and a CV shared for a particular opportunity shouldn't become an unrestricted asset for unrelated submissions.
The Office of the Australian Information Commissioner's consent guidance explains that express consent is generally required for handling sensitive information, that consent must be specific and informed, and that people can withdraw it. An organisation can't rely on withdrawn consent for subsequent use or disclosure.
Attach a role-specific consent block
Keep the following metadata beside the candidate-to-role record. An email can support the record, but the recruiter making the submission needs a visible approval status.
- Consent field — What to record
- Candidate and role — Candidate identifier, notice reference and position
- Intended recipient — Named panel supplier or clearly explained recipient category
- Disclosure purpose — Assessment or representation for the specified opportunity
- Information to disclose — CV version, supporting statement and other agreed material
- Sensitive-information handling — What will be included, why it's needed and who may receive it
- Consent date — When and how the candidate gave informed approval
- Expiry or review date — When approval must be checked again
- Withdrawal status — Active, withdrawn or awaiting clarification
- Responsible recruiter — Person accountable for checking approval
- Audit note — Evidence connecting the approval to this role and purpose
Clearance information also deserves controlled handling. Record only what the recipient needs, and don't assume every clearance-related detail is legally classified as sensitive information. Ask for appropriate privacy advice if the information or intended disclosure raises uncertainty.
The date and review fields are operational safeguards, not a universal statutory expiry period. Set them to support the actual recruitment purpose and your organisation's privacy obligations.
Don't reuse an ambiguous approval
Suppose a candidate approves a CV submission to a panel supplier for a cloud role. A later cybersecurity opportunity with another supplier introduces a different role and recipient. Record the new purpose and date, and obtain approval that covers that disclosure rather than assuming the earlier checkbox extends to it.
If the candidate withdraws consent, stop further disclosure that relied on it. Handle retention, deletion and any other legal obligations separately; withdrawing consent doesn't by itself answer every records-management question.
Submission control: Make consent status visible to the person sending the CV, not just the person who first contacted the candidate.
Use candidate management software practices that preserve this role-level audit trail. The practical test is whether another authorised recruiter can establish what the candidate approved without reconstructing a conversation from scattered messages.
Check the Profile on One Live Notice
Submit only when the profile passes the notice-level test. Choose an open BuyICT ICT labour-hire notice and assess the candidate against its current requirements. Don't treat a completed template, an attractive CV or a high automated score as approval to proceed.
Use a submit-or-stop checklist:
- Opportunity status. Confirm the notice remains open and that the submission route is correct.
- Delivery fit. Establish that the recorded role, clearance, location and timing align with the opportunity.
- Work-level fit. Check that the evidence demonstrates the required accountability and complexity, including any stated APS-equivalent level.
- Capability evidence. Confirm every must-have has supporting evidence and an explicit currency position.
- Representation approval. Verify that consent covers this recipient, information and purpose.
- Unresolved conditions. Hold the submission wherever a mandatory requirement remains unknown or unmet.
A currency position can record that the notice doesn't specify recency. It shouldn't manufacture a time limit merely to fill the cell. Similarly, if the notice doesn't state an APS level, document your work-level analysis without presenting it as the buyer's classification.
Use matching to inspect the evidence
To repeat the check on eRecruit, getting started takes three steps: sign up, upload a CV, and let the matcher do the rest. Upload a PDF or DOCX through the Resumes section. Select Personal for your own CV or Organisation when the CV should be available to your organisation's team.
Users upload CVs and see which candidates match each role, with the reasons why. Use the platform's search to compare the completed profile with open Australian Government ICT opportunities, then inspect those reasons against the source notice.
A user who uploads a resume is notified the moment a matched BuyICT opportunity goes live. That notification is a prompt to assess the opportunity, not permission to submit the candidate.
Resolve the mismatch before acting
If a result appears relevant but relies on a different location, clearance or start window, investigate the discrepancy. Correct an inaccurate profile, challenge an incorrect extraction or set aside an unsuitable opportunity. Don't alter a confirmed candidate constraint to preserve the match.
Keep a brief decision note with the notice reference and the outstanding question. A colleague should be able to distinguish ready to submit, awaiting clarification and not suitable without repeating the assessment.
The useful endpoint isn't a polished document stored in a folder. It's a defensible decision about a live government ICT role, supported by evidence and an authorised disclosure.
eRecruit.io is an Australian platform helping technology professionals, contractors, recruiters and businesses discover Australian Government ICT jobs, contracts, tenders and procurement opportunities. Visit erecruit, upload a CV and use the matching evidence to test this job profile template against an open opportunity before you prepare a submission.
