Network Engineer

The journey

1. Practised under observation

   1. 01Networks, models and the vocabulary of connectivityThe mental model everything else hangs on: what a network actually is, the layered models used to reason about it, and the devices and media that make it physical.Practised under observation

      MilestoneSpeaks the layer language

      A symptom is assigned to a layer rather than to a shrug, and the difference between bandwidth, throughput and latency is one you use rather than one you looked up.

2. From here, milestones are verified rather than practised.

   Verified against a real task

   1. 02Addressing and the design of address spaceThe engineering that separates technicians from designers, with address space designed deliberately, subnetted correctly, and documented so it survives growth.Verified against a real task

      MilestoneDesigns the address space

      You can subnet in your head rather than reach for a calculator, and the next site fits the plan without anybody renumbering anything.

   2. 03Switching and the local networkInside the building: the switched network built with segmentation, loop protection and aggregated capacity, then diagnosed under fault.Verified against a real task

      MilestoneBuilds the local network, breaks it, fixes it

      Losing a link changes the timing and not the service, and a host in one segment cannot reach what it must not because you tested rather than assumed.

   3. 04Routing and multi-site connectivityBetween the buildings, with routing understood as decision-making, dynamic protocols configured and defended, and the redundancy actually failed over.Verified against a real task

      MilestoneRoutes it, and proves the failover

      The primary path can be taken away and traffic keeps moving, a loop or a black hole is found in the tables rather than by restarting things, and a change to a device you cannot physically reach carries a way to undo itself.

   4. 05Network security and secure accessThe defended network: trust boundaries designed, firewalls and inspection deployed with intent, encrypted access engineered, and zero trust understood honestly.Verified against a real task

      MilestoneDefended, and the blast radius proven

      An attacker who lands inside this network reaches a boundary you drew on purpose, and the rule set has been read closely enough to find the rule that does nothing.

   5. 06Wireless, mobility and network automationConnectivity without cables, and the shift that modernised the seat: wireless engineered rather than installed, and network configuration treated as code.Verified against a real task

      MilestoneWireless engineered, configuration as code

      Where the access points go is answered by interference evidence rather than by guesswork, a device that has drifted from its committed configuration is found by your own check, and one task is left manual on purpose with the reason given.

   6. 07Observability, performance and the cloud networkSeeing and shaping traffic, and the estate the modern network extends into, with measurement, quality of service, load distribution and hybrid cloud connectivity.Verified against a real task

      MilestoneMeasured, prioritized, and extended to the cloud

      The capture settles whether the slowness is the network or the application, and the cloud side of this network shares one address plan with the rest of it rather than colliding with it.

   7. 08The Network Engineer in the organizationThe professional seat: designing to requirements, changing production without breaking it, and documenting so the network outlives you.Verified against a real task

      MilestoneDesigns to requirements, changes without breaking

      Design decisions here each name the requirement behind them, the accusation that it is the network is answered with evidence whether or not it is, and a stranger can diagnose a fault and make a change from your documents alone.

3. 1. Capstone

      A network an organization depends on

      A complete network design and implementation for a realistic multi-site organisation, built under observation on real or accurately emulated equipment, from requirements and an addressing plan through switching, routing, security, wireless and automation to observability, hybrid cloud connectivity and the organisational layer of the seat.

      Defence

      You walk an instructor through your own network: why this addressing plan and where the next site goes, what happens when a link is lost and for how long, what somebody who owns one host inside can reach and why that is acceptable, and what only you know about this network. The credential is not awarded if you cannot account for your own work.

   2. Credential

      High-assurance credential

      Evidence that you can design connectivity that stays up, stays private, and can be diagnosed to the exact layer by somebody reading your documentation. It does not claim seniority, and it does not oblige any employer to accept it.

      See how proof works