A core and transport engineer works one layer back from where connections are made and instead keeps the enormous, already-connected system correctly ordered — the routers, switches, and long-distance links that carry traffic between exchanges, data centres, and cities once it is already on the network. The primary pull is Organization rather than Connection precisely because the distinct contribution here is not building new links but structuring how an existing web of thousands of them stays legible, correctly routed, and resilient to a single point of failure — a genuinely different skill from the access and radio roles earlier in this field, closer in spirit to `dat`'s data engineering than to a field technician's work.
The daily texture is configuration management, capacity planning (making sure traffic growth does not outpace the network's ability to carry it), and routing design, most of it done through code and configuration tooling rather than physical hardware, with the occasional data-centre visit for a hardware refresh or a new platform build.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
The job is closer to software engineering than the job title suggests — modern core networks are increasingly software-defined, configured and automated through code rather than manually cabled and switched, and the strongest engineers in this specialism are often as comfortable scripting and version-controlling network configuration as a software engineer is with application code. General UK network engineer salaries show real dispersion depending on how "network engineer" is scoped: broad averages cluster around £38,000–£45,000, while active market data for roles specifically hired for core, enterprise, or telecoms-grade infrastructure points closer to £52,500–£70,000, with a market median nearer £57,000 for positions currently being recruited [survey_aggregator, Indeed / PayScale / Robert Half 2026].
A computer science, electronic engineering, or telecommunications degree is a common route, alongside vendor networking certifications (Cisco's CCNA/CCNP and equivalents remain widely recognised industry credentials) that many entrants pursue independently of a degree. Progression typically runs from a junior or field-support role into core network configuration as an engineer builds up vendor-specific and routing-protocol expertise.
Automation absorbs routine configuration and monitoring, but capacity-planning judgement and change-window risk ownership on live traffic stay human, gated by the field's trust gap.
Increasingly resembles software/platform engineering; automation-and-coding-fluent engineers are best positioned.
People drawn to Core & Transport Network Engineerare often drawn to these — in the order they're closest. The ones marked sit in a different field entirely.