Service Desk to Networking.

The slowest route to feel productive in, and the one that travels furthest into every other domain.

Verdict

Networking is the hardest route to justify in year one and the most durable foundation in the industry. Salary curve is unkind. The cert is genuinely hard. Five years in, the engineers who took it pass interviews the cloud and security crowd fail. Both facts are true. Most people only hear the first one.

Who this is for

·Desk staff who enjoy debugging something they didn't build.
·Anyone willing to spend year one in a NOC doing repetitive ticket work for the reflexes it builds.
·Career changers thinking long-term, not 18-month-term.

Who this isn't for

·Anyone optimising for the fastest pay bump. CCNA holders earn less than AZ-104 holders in year one.
·Anyone who finds Wireshark boring. Year one is mostly Wireshark.
·Anyone who wants to work remote from day one. NOC rotations are usually on-site for the first 12 to 18 months.

Named observation

The Packet Trace Test.

The interview moment where the candidate is shown a Wireshark capture and asked what it means. Networking people pass it. Cloud people often don't. Hiring managers across every infrastructure-adjacent domain quietly use it to separate the two.

The cert, honestly

What CCNA actually proves.

CCNA is one of the few certifications in technology that still passes a competence test. It is hard. It cannot be cheated past. The knowledge holds up in interviews for five years afterwards. That makes it unusually valuable as a signal, and is the reason hiring managers still ask for it long after the rest of the cert market has been flooded.

It is not, on its own, the job. You need lab hours. Packet Tracer, then GNS3 or EVE-NG, then a real switch off eBay. The candidates who pass first interview can talk for ten minutes about something they actually broke and fixed. Most don't.

A weak networker doesn't survive a network problem. A strong networker doesn't really notice the cloud boundary.

The three rooms by year three

Same first three years. Three different decades.

Traditional enterprise networking. Large estate, sometimes a global one. Pay is solid. The market is mature, the role is mature, the work is predictable enough to plan a life around.

Cloud networking. The intersection most cloud engineers can't fill because they came in through the developer route. Demand is large. Supply is small. The premium has held for a decade and shows no sign of collapsing.

Network security. Pays unusually well for the same reason. The interview filter is brutal. Strong networkers pass it. Weak ones don't.

All three start with the same first three years. The decision doesn't have to be made up front. Most of the strong networkers I've worked with didn't pick the lane until year four, and it didn't cost them anything.

Named observation

The Cloud Networking Premium.

The above-market salary attached to engineers who can do both halves. Most cloud engineers can't read BGP. Most network engineers don't deploy via Terraform. The intersection is small, the demand is large, and the premium has held for a decade.

Where it stalls

The mistake even strong networkers make.

The trap isn't the cert and it isn't the lab. It's the year-two assumption that the work will surface you on its own. NOCs reward visible reliability and almost never visible ambition. The engineers who plateau in year three are the ones who waited to be noticed instead of asking for the change ticket, the architecture review, the on-call shadow.

That isn't a networking problem. It's just sharper in networking because the work itself is so quiet.

Named observation

Waiting To Be Noticed.

The year-two assumption that strong execution in a NOC will surface you on its own. It almost never does. The networkers who break through ask for the project. The ones who don't, don't.

The honest part

Networking is one of the best long-bet routes in the industry and one of the worst short-bet routes. Whether you can take a slow year one for a strong year five is not a question a guide can answer for you.

The Route Planner is the place to test it against your specific starting point, salary floor and timeline.

Next step

Pick the role you think you're aiming at and see what the route actually looks like from where you are. Honest, hop by hop, with the parts that tend to break.

See your route into Networking