Skip to main content
RoleNetworking

Network Engineer

Packets, VLANs, BGP at 3am. Methodical, deep, occasionally on-site.

The verdict

Still one of the most defensible careers in infrastructure, provided you've made peace with being on-call and slightly out of fashion.

Pick this if
  • You like physical systems and protocols you can actually read on a wire
  • You'd rather own a smaller deep specialism than be a generalist forever
  • You're prepared to study for a CCNP and mean it, not just collect a SAA
  • You want a career that survives the next AI cycle without much drama
Skip this if
  • You can't bear change windows, half the work happens between 10pm and 4am
  • You want cloud salaries on a network engineer's market rate
  • You've never enjoyed a packet capture and aren't sure you ever will
What "doing well" looks like in the seat
  • You can trace a problem from a user complaint to a switchport without help
  • Your changes go in clean and roll back cleaner
  • You're the one the security team calls when segmentation breaks
  • You can explain BGP or VLANs to a stakeholder without a whiteboard
The bit you're probably underestimating

The market shrank, and most people pretend it didn't. There are fewer pure network seats than there were a decade ago, and the ones that remain expect cloud networking, automation in Python, and a comfortable relationship with Terraform. If you treat netadmin as the old job with new branding, you'll stagnate. Treat it as the foundation for network automation or cloud network engineering and you've got a runway that lasts.

Hover any chip for the calibrated meaning. Ratings are directional, not absolute.

Strong. Network architect and cloud-networking specialists are well paid.

Who actually gets in
  • +Cabling / NOC
  • +IT support
  • +Military signals
Common misconceptions
  • That networking is legacy, cloud just hides it, it doesn't remove it.
  • Cloud Engineer
  • Network Automation Engineer
  • Security

Listed because the graph connects them to this role, not because you need all of them. Most practitioners pick one or two.

Where this fits

Roles connect to pathways, certs and other roles. Use one to test the next.

The serious next step

You've read about the role. The harder question is whether it's the right one for you.

A Career Verdict is the written, practitioner-authored call on your specific route into and out of this role. Six primitives, same format every time.

Built on POST's practitioner-authored assessment framework, calibrated by James from twenty years across helpdesk, infrastructure and security. Framework is human-authored; the verdict applies it to your inputs.