A Senior Process Engineer with fifteen years in petrochemical plants picks ANZSCO 233512 because a recruiter once labelled the role "mechanical," submits the CDR, and three months later opens an Additional Information Request instead of a positive outcome. The engineering was strong. The code was wrong. That is the trap with Engineers Australia ANZSCO codes: the code decides which competency standard your evidence is measured against, so the code you choose fixes your assessment category and the evidence bar your career episodes have to clear.
This guide covers the selection logic and the verification step, not the full catalogue. It walks the decision an overseas-trained engineer actually has to make: which category your code triggers, how to resolve a role that straddles two disciplines, and how to confirm the code is assessable before you write a word.
Why your ANZSCO code is the first CDR decision you cannot undo
ANZSCO is the six-digit occupation classification Engineers Australia uses to sort every migration skills assessment. It does more than label your file. The code selects the exact ruleset the assessor grades you under, which is why getting it wrong quietly redirects your whole submission toward criteria you never intended to answer.
How Engineers Australia sorts your application by ANZSCO code
When you start the online CDR application, you select one occupation from a dropdown. That single choice routes your file to one of three Stage 1 competency standards, and from that point your career episodes and summary statement are read only against the elements of that standard. Evidence that satisfies one category can fall short in another. The categories ask different things of you.
How the code split sets your assessment category
The code range does the routing, and the split is cleaner than most applicants expect:
Code range | Assessment category | What the standard expects |
|---|---|---|
233xxx (except 233914) | Professional Engineer | Complex problem-solving and design across an engineering discipline |
233914 | Applied engineering within an established body of knowledge | |
312xxx | Technical and support engineering under professional direction |
Read that table twice, because it is the whole game. A four-year professional engineering degree does not automatically place you in the Professional Engineer category. The code does. Choose a 312xxx code and you are assessed as an Engineering Associate regardless of your qualification level, and the outcome on your assessment letter reflects that lower category.
Engineers Australia ANZSCO codes for Professional Engineers (233xxx)
Most degree-qualified applicants belong somewhere in the 233 minor group, which the Australian Bureau of Statistics divides into seven unit groups. Your discipline points you to the right one.
Civil, structural, and geotechnical roles (2332)
Civil Engineer is 233211, the broad code for design and delivery of infrastructure and buildings. Structural Engineer (233214) and Geotechnical Engineer (233212) are the specialist codes. A common trap here is defaulting to 233211 when your episodes are almost entirely structural analysis and design. If structures is your primary function, 233214 is the honest match.
Mechanical, industrial, and production roles (2335)
Mechanical Engineer is 233512. It covers rotating equipment, HVAC, thermal systems, and plant machinery. Industrial Engineer (233511) and Production or Plant Engineer (233513) sit in the same unit group but reward evidence of process optimisation and manufacturing systems rather than mechanical design.
Electrical and electronics roles (2333 and 2334)
These two get confused constantly. Electrical Engineer is 233311, for power generation, distribution, and high-voltage systems. Electronics Engineer (233411) covers circuit design, embedded systems, and instrumentation. Grid and substation work falls under electrical. Signal and device-level work falls under electronics. Your career episodes decide it, not the letters on your business card.
Chemical, environmental, and mining roles (2331, 2336, and 2339)
Chemical Engineer (233111) and Materials Engineer (233112) form the 2331 group. Mining Engineer (233611) and Petroleum Engineer (233612) sit in 2336. Environmental Engineer is the outlier at 233915, inside the 2339 "Other Engineering Professionals" group, yet still assessed as a Professional Engineer. Being in the 2339 group does not by itself demote you to Technologist. Only one code in that group does that.
Where software and network engineers actually get assessed
Computer Network and Systems Engineer (263111) is assessed by the Australian Computer Society, not Engineers Australia. Software Engineer (261313) is also ACS territory. If your work is software development or network administration, Engineers Australia is usually the wrong door entirely. Telecommunications engineering roles are sometimes listed as Engineers Australia occupations rather than ACS ones, but confirm the exact code against EA's current occupation list before you rely on that. The single most expensive assumption an ICT-background engineer can make is that a 233 code will accept them.
Engineering Technologist and Engineering Associate codes
Two categories sit outside the Professional Engineer default, and each changes the evidence you have to produce.
Engineering Technologist: the single code 233914
Engineering Technologist has exactly one code: 233914. It lives inside the 233 range but triggers a distinct competency standard focused on applying established engineering methods rather than originating complex design. Applicants sometimes land here by accident, then wonder why their assessment sits a rung below their expectation. If your degree and work genuinely support Professional Engineer, choose a Professional Engineer code so your evidence is graded at the right level.
Engineering Associate codes (312xxx) and a different evidence bar
Engineering Associate codes fall in the 312 range: Civil Engineering Draftspersons and Technicians (3122), Electrical Engineering Draftspersons and Technicians (3123), and their mechanical and electronics equivalents. The Stage 1 standard here targets technical support and applied competencies under professional direction, so the evidence bar differs in kind, not just degree. Recent changes have tightened which qualifications are eligible for the Engineering Associate pathway; check EA's current requirements rather than an older blog before committing.
Choosing a code when your role spans two disciplines
Dual-discipline roles are where selection stops being a lookup and becomes a judgement call.
Match primary work function, not your job title
Return to the Senior Process Engineer from the opening. The title reads as mechanical to some recruiters and chemical to others, which is exactly why job title cannot resolve the question. The deciding factor is which discipline accounts for the majority of the work described across the three career episodes. Episodes dominated by reaction kinetics, separation processes, and mass balances point to 233111 (Chemical Engineer). Episodes dominated by pumps, compressors, piping mechanical design, and rotating equipment point to 233512 (Mechanical Engineer). Count the primary-function tasks episode by episode, then let the majority decide.
When your three career episodes sit in different groups
A simple mapping of primary work function to code group resolves most of these cases:
Structural or building design leads to 2332, usually 233214.
Infrastructure delivery and construction management lead to Civil, 233211.
Rotating equipment, HVAC, and plant machinery lead to Mechanical, 233512.
Power systems, grids, and control lead to Electrical, 233311.
Circuit, embedded, and instrumentation work leads to Electronics, 233411.
Process, reaction, and separation work leads to Chemical, 233111.
Software development or network administration leads to ACS codes, not Engineers Australia.
Maintenance, inspection, and technician support lead to the Engineering Associate 312xxx range.
Where your three episodes span groups, you still submit under one code. Pick the code that matches your strongest and most recent episodes, then make sure the summary statement maps that code's competency elements. You are not hiding the other disciplines; you are declaring where the centre of gravity sits.
Confirming your code is on the EA occupation list
A code that is technically correct in the ANZSCO dictionary is useless if Engineers Australia does not assess it. This check comes before writing, not after.
Cross-checking the migration skills assessment occupation list
Engineers Australia's CDR application presents a dropdown of roughly 31 assessed engineering occupations, and your target code has to appear there for the submission to proceed. Open the application, find your code in that list, and confirm the occupation name matches your intended role before you draft anything. This two-minute check saves weeks.
What to do if your code is not on the list
If your intended code is absent, do not force the nearest 233 code and hope. First confirm whether another authority assesses it, as with the ACS ICT codes above. If Engineers Australia genuinely is the right assessing body, re-examine your primary work function against the codes that are listed, because the correct EA-assessable code may be a neighbour you overlooked. A code that is not in the dropdown cannot be submitted.
ANZSCO code errors that trigger Additional Information Requests
Selecting the wrong occupational category means your competencies are evaluated against the wrong standard, and failure can follow even when the underlying engineering is strong.
Common job-title-to-code mismatches assessors flag
The recurring patterns are predictable: a networks engineer applying under a 233 code when the work belongs to ACS; a technician-level role submitted under a Professional Engineer code the evidence cannot support; a broad title like "Project Engineer" mapped to Civil when the episodes are mechanical. Your job title does not need to match the ANZSCO description word for word. What matters is that your CDR evidence demonstrates the competencies listed for the code you chose.
Why a mismatch means resubmission, not a quick fix
When the code and the evidence pull in different directions, Engineers Australia may issue an Additional Information Request or assess the file under the wrong category, producing an outcome below what your qualifications actually warrant. Reversing that is not a phone call and a correction. It generally means a fresh submission under the right code, with the fees and the months that a resubmission costs. That is why the code is the decision you make first and get right once.
Frequently asked questions on Engineers Australia ANZSCO codes
What happens if I select the wrong ANZSCO code for my CDR?
Your CDR is assessed against the competency standard tied to that code, so a wrong code means your evidence is graded on the wrong criteria. The likely results are an Additional Information Request or an outcome in a lower category than your qualifications support, and correcting it usually requires resubmission rather than a simple amendment.
Can I apply under more than one ANZSCO code?
No. Each CDR is submitted under a single ANZSCO code. When your experience spans disciplines, choose the code that reflects the majority of the work described across your three career episodes, then map your summary statement to that code's competency elements.
Does my job title need to match the ANZSCO description?
No. Title mismatch is common and not itself a problem. Engineers Australia assesses the tasks and competencies your career episodes demonstrate, not your job title, so the requirement is that your evidence aligns with the chosen code's occupation description.
Which ANZSCO code should a software engineer use?
Usually none. Software and computer-network roles such as Software Engineer (261313) and Computer Network and Systems Engineer (263111) are assessed by the Australian Computer Society, not Engineers Australia. Engineers with telecommunications engineering backgrounds may be EA-assessable; confirm the specific code on Engineers Australia's current occupation list before proceeding.
Can I change my ANZSCO code after I have submitted my CDR?
Not easily. Once assessment is underway, the code is locked to your file, and moving to a different category generally means a new submission with its own fee and processing time. Verifying the code against the occupation list before writing is precisely what prevents that outcome.
Once you have confirmed your ANZSCO code, the next step is making sure your CDR evidence maps to that occupation's competency elements. The Engineers Australia CDR skills assessment criteria page sets out what each category requires, and the CDR complete guide for 2026 walks the full report structure so you can build against the right standard from the start.