From Network Engineer to Technical Project Manager: A Career Roadmap
The move from engineering to project management is one of the most common — and least explained — transitions in IT. A practical roadmap.
Many of the best technical project managers I've worked with started as engineers. They understand what a change window really involves, why a "simple" firewall rule takes two weeks, and when an engineer's estimate is optimistic. That background is an advantage — if you make the transition deliberately.
What changes when you move into project management
| As an engineer | As a technical PM |
|---|---|
| You solve the problem | You make sure the problem gets solved — on time, in scope, with the right people |
| Success = working configuration | Success = business outcome delivered with managed risk |
| Depth in one area | Breadth across teams, vendors and stakeholders |
| Your work is visible in the network | Your work is visible in decisions, plans and communication |
Step 1 — Start doing the work before you have the title
- Volunteer to own the RAID log or the cutover plan on your next change
- Write the weekly status update for your workstream
- Run a lessons-learned session after a major change
These are low-risk ways to build evidence.
Step 2 — Learn the language
Pick one recognised framework and learn it properly. Options include APM, PMI-based certifications, PRINCE2, and Agile/Scrum or SAFe for organisations that use them. A certification won't make you a project manager, but it gives you shared vocabulary and signals intent.
Step 3 — Get comfortable with numbers
Project managers are trusted when they understand cost. Learn to read a budget, track forecast against actuals and explain variance. This is also where business education — formal or self-taught — pays off.
Step 4 — Rewrite your story
Your resume should show scope, coordination and outcomes, not just technologies:
- ❌ "Configured Cisco switches for data-centre migration"
- ✅ "Coordinated cutover of 40 network devices across three change windows with zero unplanned downtime"
Only use numbers you can stand behind in an interview.
Step 5 — Target the right first role
Technical project coordinator, project analyst or technical project assistant roles are realistic stepping stones. Infrastructure-heavy organisations — telecom providers, managed service providers, large enterprises — value engineers who can manage delivery.
A 12-month plan
- Months 1–3: take on PM-style tasks in your current role; start a certification
- Months 4–6: complete the certification; document 3–4 delivery stories
- Months 7–9: update your resume and LinkedIn; talk to PMs in your organisation
- Months 10–12: apply internally first, then externally
If you'd like help building your own roadmap, take a look at career mentoring.
- #Career
- #Project Management
- #Career Transition
- #IT Careers
Related reading
The RAID Log: The Most Underused Tool in Infrastructure Projects
Every project has a RAID log. Few use it well. A practical guide to Risks, Assumptions, Issues and Dependencies — with a free template.
Beyond Cisco: The Enterprise Networking Market in 2026
Two 2025 deals redrew the map: HPE now owns Juniper and Arista owns VeloCloud. Part 1 of a vendor-neutral, 19-vendor analysis — who really competes with Cisco, and in which category.
Enterprise Network Vendors Compared: Products and Technical Capabilities
Switching, routing, Wi-Fi 7, SD-WAN, NGFW, SASE, data-center fabrics and automation — a side-by-side view of what Cisco and 13 alternatives actually offer, plus a 24-row feature matrix.
Let's talk
Have a technology initiative, a project, or a career question?
Tell me a little about it. I read every message and usually reply within two working days.