Network Engineer and ACS: ANZSCO 263111 vs Sysadmin and Cybersecurity
Common problems within the networking group
A network engineer (Network Engineer, ANZSCO 263111) is one code within the ANZSCO 263 group — ICT Infrastructure Professionals. This group has several codes that sit close together, which leads to confusion when lodging an ACS file:
- 263111 — Network Administrator / Network Engineer: designing, installing and operating networks
- 262113 — ICT Systems Administrator (Sysadmin): administering server systems, the OS and users
- 262116 — ICT Security Specialist (Cybersecurity): securing systems, analysing threats
- 263112 — Network Analyst: analysing network performance and operations (asking questions, not designing)
Choosing the wrong code → a file that does not match → ACS assesses it negatively or downgrades it to another code.
For an overview of the migration pathway, see the related article on network engineer migration to Australia.
ANZSCO 263111 — Network Engineer/Administrator: what do they do?
Under the ANZSCO classification, code 263111 covers two job titles: Network Administrator and Network Engineer. This is a broader code than the job titles commonly used in everyday practice.
The core work of 263111:
- Designing and deploying network infrastructure: LAN, WAN, SD-WAN, MPLS
- Configuring routers, switches, firewalls, load balancers
- Monitoring network performance and resolving connectivity incidents
- Managing DNS, DHCP and IP address management
- Designing and deploying VPNs, WAN optimisation
- Ensuring the availability and redundancy of the network infrastructure
Distinguishing keywords: network infrastructure, routing and switching, connectivity, network design.
Comparison with the codes it is confused with
263111 vs 262113 — Sysadmin
| Network Engineer 263111 | Sysadmin 262113 | |
|---|---|---|
| Focus | Network, connectivity, routing | Servers, OS, users |
| Main equipment | Router, switch, firewall | Server, hypervisor, storage |
| Protocols | BGP, OSPF, VLAN, VPN | Active Directory, DNS, DHCP (from the server side) |
| Output | Network topology, routing table | Server running, user accounts, email working |
If you spend most of your time managing servers and Active Directory even though you also do a little networking — you are most likely a Sysadmin 262113.
263111 vs 262116 — Cybersecurity
Network security (firewall rules, IDS/IPS, network segmentation) is one part of a network engineer’s work — but it is not enough to nominate code 262116 (Cybersecurity). Code 262116 is for someone specialised in security: threat analysis, penetration testing, security policy, incident response.
If you do network security as part of managing the network, you are still 263111. If your whole role is cybersecurity with no networking operations, you are 262116.
263111 vs 263112 — Network Analyst
A Network Analyst (263112) is someone who analyses network performance, not someone who designs or operates it. This is a less common role and usually does not match the experience of most network engineers.
Cloud networking: does it count as 263111?
A common question from modern network engineers: if I do cloud networking (AWS VPC, Azure VNet, GCP VPC, SD-WAN on cloud), does ACS count it as 263111?
The answer: yes — if the work is genuinely network engineering, just in a cloud environment. Cloud networking work that is usually counted towards 263111:
- Designing VPC architecture, subnets, routing tables, VPN Gateway
- Configuring Transit Gateway, peering, Direct Connect / ExpressRoute
- Deploying software-defined WAN or network virtualisation
- Managing network security groups, NACLs, firewall rules
Cloud networking work that does not count as 263111:
- Purely DevOps/Infrastructure as Code unrelated to network design → DevOps 261316
- Managing cloud IAM and security policies that are not networking → Cybersecurity 262116
Common mistakes in a network engineer’s file
Mistake 1: Listing certifications (CCNA, CCIE, AWS Networking) as experience Professional certifications are not counted by ACS as work experience. A certification can support a file but cannot replace a description of the actual work.
Mistake 2: Describing the network too generically “Managed the company’s network infrastructure” is not enough. You need specifics: the number of devices, the type of devices (Cisco, Juniper, Palo Alto and so on), the routing protocols used, the scale of the network (number of sites, number of users), and the incidents you handled.
Mistake 3: Not distinguishing between network ops and network design If you mainly operate an existing network (following runbooks, not designing) — this is a Network Administrator leaning towards ops. If you design new networks, choose the topology and select the equipment — this is a Network Engineer. Both fall under 263111, but the file needs to reflect the correct role.
Mistake 4: Experience spread across too many areas (network + server + security) If the work is spread evenly across network, server and security, ACS needs to determine the code. Make it clear in the file which part is the main focus. If it really is 40/30/30, you need to think carefully about which code best reflects the main work.
How to present a network engineer’s ACS file
Each position in the file should describe:
- The network infrastructure you manage: scale, type, environment (on-premise, cloud, hybrid)
- The design or change work you did: specifically what changed, and why
- The incidents you handled: the troubleshooting process and the outcome
- The technology and vendors: Cisco, Juniper, Fortinet, AWS, Azure — ACS understands the technical terminology
A good description: “Designed and deployed an MPLS hub-and-spoke architecture for 12 branch offices across South-East Asia. Configured BGP peering with the ISP and designed a QoS policy to prioritise VoIP and video conference traffic. Resolved a route-flapping incident affecting 3 sites over 4 hours and identified the cause as out-of-sync BGP timers.”
For more, see the related articles on DevOps 261316 vs Sysadmin 262113, the cybersecurity specialist ACS file, and choosing the right ANZSCO code for IT occupations.