Hybrid Roles and ACS Skills Assessment: How Much of Your Work Must Match the Occupation?
A hybrid ICT role is not a defect in an ACS application. It is a classification problem that has to be solved with evidence.
Modern jobs combine functions that ANZSCO separates: a Product Owner may also perform business analysis; a DevOps engineer may write application code; a BI specialist may analyse data and design systems; a project lead may still make technical decisions. ACS does not solve that ambiguity by reading the employer title. Its current assessment process examines whether employment episodes are at the appropriate professional level and closely related to the nominated occupation. For the underlying rule, see ACS IT occupations and ANZSCO codes.
Consider a solutions lead whose time is split between approving integration designs and coordinating a delivery team. The decisive evidence is not a self-estimated percentage of ‘technical’ time; it is which decisions the lead personally made, what specifications or deployments resulted, and whether that responsibility persisted through each employment period. A reference should describe the change in duties when the person moved from hands-on implementation to managing other engineers, rather than silently treating the whole tenure as one occupation.
The key point is that ACS does not publish a universal rule saying that 51%, 60% or 70% of a hybrid job must match. Creating a percentage and presenting it as an ACS threshold would be false precision.
For the broader classification method, use ACS occupation mapping by actual duties when job titles are ambiguous.
Use four dimensions instead
A reference that survives a changing job title
Ask the employer to describe each distinct period of work, particularly where a promotion changed the balance between engineering, analysis and management. The ACS employment-reference rules require accurate dates and responsibilities; a single undifferentiated reference for six years can erase the shift that matters most. Instead of asking the employer to write the chosen occupation into the letter, collect a dated responsibility table and confirm it against project allocations. A candidate might have two years of hands-on development followed by three years of delivery leadership. That history can support a different conclusion from a current title that happens to contain the word ‘engineer’.
| Dimension | Question to answer | Why it matters |
|---|---|---|
| Frequency | How often is the duty actually performed? | Separates recurring work from occasional exposure. |
| Responsibility | Do you own the decision/output or only assist? | Shows professional accountability, not proximity. |
| Output | What does the work produce or change? | Reveals the professional function underneath the title. |
| Evidence | What document or project can prove it? | Prevents a plausible story from becoming an unsupported claim. |
Build a representative duty ledger
The reporting-line test for hybrid technology roles
A hybrid title should be decomposed into deliverables before an occupation is selected. Imagine a lead who runs sprint planning on Monday, designs a customer onboarding workflow on Tuesday, writes an API integration on Wednesday and reviews delivery milestones on Friday. The fact that all four activities appear in the same position description does not make them equivalent professional responsibilities. Ask who accepts the output, what judgement the employee exercised, which artefact survives the meeting and which tasks the employer would still require if the product were cancelled. The ACS assessment process puts the emphasis on actual, occupation-related work rather than a fashionable label. A monthly task inventory supported by tickets and approved specifications is much more persuasive than estimating percentages from memory.
Take a representative month or project phase and list the major activities. Do not begin with ANZSCO wording. Use the language the employer and team would recognise. Then record frequency, level of ownership, output and the occupation signal created by that work.
| Duty | Frequency | Responsibility | Possible occupation signal |
|---|---|---|---|
| Requirements workshops and functional specifications | Weekly | Leads analysis and owns specifications | ICT Business Analyst |
| SQL analysis and decision dashboards | Weekly | Produces analysis and interprets findings | Data Analyst |
| Sprint coordination | Daily | Coordinates work but does not own full project governance | Supporting / delivery duty |
| System integration design | Monthly | Evaluates constraints and recommends system changes | Systems / software signal |
The table is not an ACS form and it does not create a mathematical test. Its value is diagnostic: it exposes whether the secondary function is substantive or merely visible.
Three hybrid-role traps
Choosing an assessment strategy, not a flattering description
The borderline case: who owns the acceptance criteria?
A hybrid analyst-developer may gather requirements and also build the solution. If that person writes the specifications, chooses the data model, implements the service and performs deployment reviews, the role cannot be classified by counting meetings. Ask which decisions recur, which were delegated and how responsibility is evaluated in performance reviews. A practical approach is to select three representative months—one normal month, one high-pressure release and one maintenance-heavy month—and inspect actual work records. If the candidate’s responsibility changed during a product launch, describe that fluctuation instead of inventing a single permanent ratio. Evidence drawn only from an exceptional incident can overrepresent one occupation.
A second challenge occurs when employers use one generic title across an entire technical team. A ‘Technical Consultant’ may be assigned requirements design for two clients and infrastructure operations for a third. The safe account separates client engagements and explains why their deliverables fit the nominated occupation. Avoid presenting an attractive job profile that cannot be reconciled with employer letters or timesheets. When the work is genuinely multidisciplinary, the article’s practical message is not that one occupation magically covers every task. It is that assessment should begin with documented professional outputs, supported by independent evidence about what the individual personally did.
Before paying for an assessment, compare the current job with the candidate’s earlier relevant employment and qualification evidence. The ACS qualifications guidance addresses education separately from work duties, while the ACS policy hub governs how an outcome can be challenged. Build a shortlist of plausible occupations, then reject each one using its weakest evidence rather than selling its strongest anecdote. If no occupation can be supported consistently across duties, references and projects, obtain clarification from the employer while the facts are accessible. The aim is a coherent record of real work, not the highest-sounding occupation code.
Trap 1: one visible duty dominates the narrative
A developer who facilitates a quarterly workshop is not automatically an ICT Business Analyst. A Business Analyst who writes a few SQL queries is not automatically a Data Analyst. Occasional tasks can be real without defining the occupation.
Trap 2: the reference tries to satisfy every code
References written to mention every plausible occupation usually become vague. They accumulate keywords but lose the professional centre of the role. Describe the work first; then test which occupation the work supports.
Trap 3: a promotion changes the title but not the function
Hybrid careers often evolve. Map each employment period separately. If the person moved from analysis into project accountability, or from coding into DevOps/platform ownership, the chronology may justify a different occupation signal later in the career.
How this interacts with the three-occupation option
When breadth obscures professional depth
A broad portfolio can look impressive while hiding that the applicant contributed only briefly to each discipline. Separate ownership from participation. A Product Owner who signs off acceptance criteria is not necessarily the engineer responsible for implementing them; an engineer who attends discovery meetings is not necessarily the business analyst who creates the requirements model. Check the ACS experience criteria and distinguish independent decision-making from support, coordination and oversight. The evidence should identify difficult decisions, their consequences and the professional techniques applied. A meaningful description explains how the candidate resolved competing technical constraints, not simply that the team delivered a successful platform.
ACS currently allows an applicant to choose up to three occupations for assessment. That is an option, not a target. The hybrid-role method on this page comes first: only nominate an additional occupation when a substantial and separately provable duty pattern supports it.
RPL applicants need the same story across evidence types
For RPL, the project reports can show different dimensions of a hybrid career, but they should not contradict the employment evidence. The reports must also remain the applicant’s own work. A project can show analysis, architecture, development or delivery depth; it should not be rewritten to manufacture an occupation that the employment history does not support.
A defensible hybrid-role decision
- Remove the job title and technology brands.
- List recurring duties and outputs in ordinary workplace language.
- Mark frequency and personal responsibility.
- Map each employment period, not only the current role.
- Compare the dominant professional function with current ACS occupation descriptions.
- Choose additional occupations only where the evidence can independently defend them.
Hybrid work is normal. The goal is not to make the career look simpler than it was. The goal is to make the mix measurable enough that the nominated occupation is an evidence-led classification rather than a title-led guess.
