Curated for this specific career level.
Level path
Network Practitioner
NE
Own features and services with solid implementation judgment across neighboring layers.
Concepts explicitly listed in this level.
Concepts span multiple tracks and layers.
Job description signalsTypical responsibilities↓
- Design, implement, troubleshoot, and evolve enterprise, data-center, and cloud networks.
- Own addressing, routing, switching, traffic services, network security, and connectivity reliability.
- Automate network change and improve observability, capacity, resilience, and incident response.
- Own features end to end from design through implementation, testing, release, and support.
- Make local technical tradeoffs and explain them clearly to teammates.
- Improve reliability, maintainability, and observability of the systems you touch.
- Collaborate with product, design, QA, operations, and adjacent engineering teams.
Track / layer masteryConcept coverage by layer↓
Software
10 concepts
Operations
1 concepts
Software
143 concepts
Management
16 concepts
Operations
13 concepts
Product
8 concepts
Theory
3 concepts
Data
2 concepts
Learning scopeConcepts by learning area↓
Specific to this level
Concepts introduced by this level
Level concepts
Routing & Connectivity
Mid-level network engineers own connectivity domains and understand how traffic moves between them.
Level concepts
Network Services
Production networks depend on controlled ingress, service distribution, and resilient name resolution.
Cumulative level expectation
All concepts expected at this level
Inherited path
Coding Foundations
Developers begin by learning to translate requirements into working, readable code.
Inherited path
Developer Tooling
Daily development depends on version control, language tooling, static checks, and repeatable local workflows.
Inherited path
Testing & Debugging
A developer owns not only writing code, but proving that it behaves as intended.
Inherited path
Employment Basics
Technical candidates benefit from understanding who employs them, how they are paid, and which terms govern the working relationship.
Inherited path
Programming Foundations
Learn the basic building blocks used to express behavior in code.
Inherited path
Software Design
Structure code so it remains readable, testable, and maintainable as it grows.
Inherited path
Data & Persistence
Understand how applications store, retrieve, and protect durable state.
Inherited path
Architecture & Systems
Design systems that handle growth, latency, failure, and multiple communicating components.
Inherited path
Production Awareness
Know how software is built, deployed, observed, and recovered in production.
Inherited path
Network Foundations
Junior network engineers need a reliable mental model of addressing, frames, packets, protocols, and network devices.
Inherited path
Addressing & Services
Most connectivity failures become easier to diagnose when addressing, naming, and local resolution are understood together.
Inherited path
Application Design
Mid-level developers own complete features and make local design choices inside an established architecture.
Inherited path
Runtime & Data
Feature ownership requires practical knowledge of runtimes, memory management, and relational persistence.
Inherited path
Delivery & Collaboration
Professional development includes the complete implementation loop, not only editing source files.
Path concepts
Routing & Connectivity
Mid-level network engineers own connectivity domains and understand how traffic moves between them.
Path concepts
Network Services
Production networks depend on controlled ingress, service distribution, and resilient name resolution.