Choosing an engineering occupation code doesn't choose your visa — it chooses your competency standard

Seven codes, one visa reach — the pattern this family breaks

Aeronautical (233911), Agricultural (233912), Biomedical (233913), Engineering Technologist (233914), Environmental (233915), Naval Architect (233916) and Engineering Professionals nec (233999) all sit on both the Medium and Long-term Strategic Skills List and the Core Skills Occupation List, and all seven reach the full set of eight skilled visas — 186, 189, 190, 407, 482, 485, 491 and 494. None of the seven carries the kind of list contradiction that affects a handful of other occupations on the current register, and none of them shows the visa-narrowing that some other engineering and trade codes carry when a discipline sits on a shorter list. The one list-level curiosity is Agricultural Engineer, which additionally carries the Regional Occupation List on top of the two every sibling carries — but MLTSSL and CSOL between them already reach all eight visas, so that third membership adds no further visa access. It is a curiosity, not a second pathway. Since visa reach can't distinguish these codes from each other, the only thing that should decide your nomination is which one your actual qualification and work genuinely match.

The category trap: how nominating an occupation locks in your competency standard

Engineers Australia sorts every applicant into one of four occupational categories — Professional Engineer, Engineering Technologist, Engineering Associate or Engineering Manager — and that category is not something you separately declare. EA's own preparation guide states it directly: once you choose an engineering occupation from the list, the skill level, ANZSCO code and occupational category fields all auto-populate together. Aeronautical, Agricultural, Biomedical, Environmental and Naval Architect Engineer are all professional-engineer-designated occupations in that list. Nominate any of them, and your three Career Episodes have to demonstrate the entry-to-practice competencies for the Professional Engineer category specifically — EA's guidance is explicit that each episode must show the competencies "listed for your specific occupational category." There is no way to nominate, say, Aeronautical Engineer and be assessed as a technologist instead. If your qualification is genuinely at Sydney Accord (three-year technology) depth rather than Washington Accord (four-year professional) depth, the occupation that matches that depth is Engineering Technologist itself — a different code, not a different setting on the same one. The outcome letter does make the result visible rather than hidden: EA states that both your occupational category and your engineering occupation appear together on it, so a mismatch, if one exists, is at least discoverable after the fact rather than buried.

What Engineering Technologist actually is — and isn't

233914 does two jobs at once in EA's system. It is one of the four occupational categories every applicant lands in, and it is also, separately, one of the 31 specific occupations selectable on the CDR pathway. For this one code, those two things collapse into the same event: nominating the occupation "Engineering Technologist" and being assessed into the category "Engineering Technologist" happen together. ANZSCO's own description of the occupation is that it analyses and modifies new and existing engineering technologies and applies them in testing and implementation — a distinct scope, not simply "junior engineer." EA's Stage 1 Competency Standard for the category is explicit about what actually separates it from Professional Engineer, and it isn't depth of skill: technologists "may not... be expected to exercise the same breadth of perspective as Professional Engineers, or carry the same wide-ranging responsibilities for stakeholder interactions, for system integration, and for synthesising overall approaches to complex situations," while within their specialist field "their expertise may be at a high level, and fully equivalent to that of a Professional Engineer." The distinction EA draws is breadth of role, not lesser competence. 233914 also carries five named specialisations — Biomedical, Industrial, Mining, Safety and Structural Engineering Technologist — that mirror discipline names assessed separately at professional level elsewhere in the system.

The quiet version of the same trap, inside 233914 itself

Four of Engineering Technologist's five specialisations — Biomedical, Industrial, Mining and Structural — share a name with a separately assessed professional-engineer code (Biomedical Engineer 233913 is in this family; Industrial, Mining and Structural Engineer sit in other unit groups covered elsewhere on this site). Someone doing biomedical, industrial, mining or structural engineering work whose competencies genuinely sit at technologist depth is not choosing between "the discipline code" and "a generic technologist code." They're choosing between the professional discipline code and the technologist specialisation of that same discipline — two different unit groups, two different competency standards, for work that might look identical on paper. Getting this wrong the way round it usually goes wrong — nominating the professional code because the discipline name matches, rather than the technologist code with the matching specialisation — produces the same category mismatch described above, just arrived at from the technologist side rather than the professional-engineer side.

233999 nec is a named list of eight, not a catch-all

Engineering Professionals nec sounds, on its name alone, like the code for any engineer who doesn't fit anywhere else. ANZSCO says otherwise, in writing: the occupations it actually covers are Acoustic Engineer, Calibration Engineer, Corrosion Engineer, Fire Safety Engineer, Mechatronics Engineer, Product Design Engineer, Safety Engineer, and Test and Activation Engineer (Naval Shipbuilding) — eight specific disciplines, named individually. If your work is not one of those eight, and it doesn't match one of the other named 2339 codes either, nec is not automatically the right fallback; it's a specific list you either match or don't. This dossier could not find any current Engineers Australia page that discusses, beyond that ANZSCO list itself, when nec is or isn't the correct nomination — which may be part of why the confusion below has persisted for so long.

A real applicant got this wrong, in writing, 18 years ago

In a 2008 thread on the British Expats forum, an applicant preparing a CDR asked directly: "Ok please advise will I apply for Engineer(nec) then?" The reply: "Yes, mention your occupation as Engineering Technologist NEC (60 points). Mention in your CDR that you use generic engineering knowledge in your daily work." That is forum advice, not authority guidance, and it is worth reading as exactly that — a real exchange between two applicants, not a rule. It also predates the current occupation structure by a wide margin: the 2008 thread's combined "Engineering Technologist NEC" label doesn't exist any more, Engineering Technologist (233914) and Engineering Professionals nec (233999) are now two separate codes with two separate scopes, the points figure quoted is from a long-superseded points test, and it predates the accreditation changes Engineers Australia has made since. Under the current published material, the advice is wrong on two counts at once: nec is a fixed eight-occupation list, not a generic catch-all, and "generic engineering knowledge" is the opposite of what any CDR — technologist or professional — actually needs to demonstrate. The thread is useful for exactly one thing: it shows this confusion between technologist and nec, and the "generic knowledge" framing, is not a new mistake. It has been circulating among applicants for close to two decades.

Naval Architect and Marine Surveyor: same degree, two different jobs

Naval Architect (233916) is assessed by Engineers Australia, and only Engineers Australia. AMSA runs a separate migration skills assessment scheme, but it names exactly four occupations it covers — Marine Engineer, Ship's Master, Ship's Officer and Marine Surveyor — and its explicit exclusion list is scoped entirely to unit group 2312, Marine Transport Professionals. Naval Architect sits in 2339, not 2312, so it was never in scope for AMSA to begin with; there's no boundary dispute here, just two authorities with entirely separate territories. The one genuine overlap: AMSA's own worked example of an accepted qualification for its Marine Surveyor occupation — a different code, no sea service required, assessed on professional experience rather than CDR — is a degree in Naval Architecture and Ocean Engineering with eight years of post-degree experience. So a naval-architecture graduate can genuinely have two real, different pathways open to them on the strength of one degree: Naval Architect through EA's CDR process, or Marine Surveyor through AMSA's experience-based one. They are two different jobs assessed by two different bodies, not two labels for the same thing, and deciding between them is about which work you actually want to do, not which one sounds closer to your degree title.

Moving categories later, and what this dossier couldn't confirm

If a category mismatch does surface — an outcome letter naming a category you didn't expect — Engineers Australia's named process for correcting it going forward is "articulation," open to technologists and associates who want to move to a higher category, usually professional engineer for a technologist. The ordinary route is completing the accredited qualification for the higher category; EA also states that someone who doesn't want to do that can instead pass an entry-to-practice competency assessment for the new category. What this research could not establish is whether articulation can be applied against a migration skills assessment outcome letter that has already been issued, or whether a category correction after the fact requires an entirely fresh CDR application — articulation is documented as EA's own membership and domestic-practice process, and nothing found here ties it explicitly back to a migration outcome. If this applies to your situation, that's a question to put to Engineers Australia directly rather than assume an answer to. Two smaller gaps worth naming honestly: the Therapeutic Goods Administration's medical-device regulation was unreachable from this research pass, so nothing here describes whether it touches a biomedical engineer's own role personally; and no labour agreement or DAMA occupation list naming any of these seven codes was found, though not every regional list was checked occupation by occupation.

Does the engineering code I choose change which visas I can apply for?

Not in this family. Aeronautical, Agricultural, Biomedical, Engineering Technologist, Environmental, Naval Architect and Engineering Professionals nec all sit on the same two skilled lists and reach the same eight visas — 186, 189, 190, 407, 482, 485, 491 and 494. What the code changes is which Engineers Australia competency standard your Career Episodes are assessed against, because the occupation you choose auto-populates your occupational category.

What happens if I nominate a professional-engineer code but my real qualification is technologist-level?

Engineers Australia's own guidance states that choosing an occupation auto-populates the skill level, ANZSCO code and occupational category together. There is no way to nominate a professional-engineer-designated occupation like Aeronautical or Biomedical Engineer and be assessed as a technologist instead — your Career Episodes have to satisfy the Professional Engineer standard for that code. If your qualification sits at Sydney Accord (three-year technology) depth, the matching occupation is Engineering Technologist (233914) itself, nominated directly.

Can I fix a category mismatch after I've already got my outcome letter?

Engineers Australia's outcome letter shows both your occupational category and your specific occupation together, so a mismatch is visible rather than hidden. EA's named process for moving to a higher category later is called articulation, and the ordinary route is completing the accredited qualification for that higher category, or otherwise passing a fresh entry-to-practice competency assessment. This research could not confirm whether articulation can be applied against an outcome letter already issued for a migration skills assessment specifically — check directly with Engineers Australia.

Is 233999 Engineering Professionals nec a fallback for any engineer who doesn't fit elsewhere?

No. ANZSCO names exactly eight occupations under this code — Acoustic, Calibration, Corrosion, Fire Safety, Mechatronics, Product Design, Safety, and Test and Activation (Naval Shipbuilding) Engineer. If your work isn't one of those eight and doesn't match another named 2339 code, nec is not automatically the right nomination just because nothing else seems to fit.

I have a naval architecture degree — should I nominate Naval Architect, or apply through AMSA?

They're two different jobs. Naval Architect (233916) is assessed only by Engineers Australia, through the CDR process. AMSA runs a separate scheme covering four different occupations, and its own worked example of an accepted qualification for its Marine Surveyor occupation is a naval architecture and ocean engineering degree with post-degree experience — but Marine Surveyor is a different code, assessed on professional experience rather than a CDR, with no sea service required. Which one to pursue depends on which work you actually want to do, not which name sounds closer to your degree.

Does being assessed as an Engineering Technologist mean I'm considered a lesser engineer?

Not on skill, according to Engineers Australia's own Stage 1 Competency Standard. It states a technologist's expertise within their specialist field may be fully equivalent to a Professional Engineer's. The distinction it draws is breadth of role — technologists aren't expected to carry the same system-integration and stakeholder-wide responsibilities professional engineers are — not lesser technical competence.

Why does Agricultural Engineer carry three list memberships when the other 2339 codes carry two?

Agricultural Engineer (233912) sits on the Regional Occupation List in addition to the MLTSSL and CSOL every sibling code carries. Because MLTSSL and CSOL between them already reach all eight visas this family can reach, the extra Regional Occupation List membership doesn't open any further visa access — it's a list-membership curiosity rather than a second, easier pathway.