60%major-rebuild transition
Career transition
Network Engineer → Data Analyst
Not generic reskilling advice, but an analysis of the distance between two specific occupations: tasks, skills, pace, money and risk.
01 · Starting distance
Transition realism index
Five factors answer a more useful question than “will it work?”: where the route is naturally strong and where proof is needed.
This is a major-rebuild transition. The strongest support is Entry accessibility (68%), while the main constraint is Resilience gain (39%). The index estimates the distance between roles, not your ability.
Skill transfer64%
Task similarity56%
Entry accessibility68%
Market opportunity67%
Resilience gain39%
Starting roleNetwork Engineer · 32%
→
Learning estimate6–12 months
→
Target roleData Analyst · 51%
02 · What changes in the work
Task comparison
The work shifts from Hands-on work toward Analysis and data, a 25-point change. This is the main behavioral adjustment in the move.
Network EngineerData Analyst56% · profile similarity
Analysis and data+25
People and communication0
Creation and design+6
Hands-on work-25
Control and accountability-19
Routine operations+13
Network Engineer: high-exposure tasks
Data Analyst: high-exposure tasks
03 · Foundation and gaps
Skill-gap map
The map shows the gap between your starting point and a level you can demonstrate to an employer through work evidence—not simply “know / do not know.”
Already transferable
- systems thinking and physical-constraint awareness
- engineering thinking
- calculation and diagnostics
- technical documentation
- physical-constraint understanding
Needs development
- SQL and data preparation
- visualization and forecasting
- AI-agent-assisted development
- architecture and system design
- AI-generated code security
- observability and DevOps
015 wk
SQL and data preparation
Prove it in “Working prototype: Network Engineer → Data Analyst transition case”: include a distinct output that uses sQL and data preparation.
start 24%target 87%
025 wk
visualization and forecasting
Prove it in “Working prototype: Network Engineer → Data Analyst transition case”: include a distinct output that uses visualization and forecasting.
start 42%target 79%
036 wk
AI-agent-assisted development
Prove it in “Working prototype: Network Engineer → Data Analyst transition case”: include a distinct output that uses aI-agent-assisted development.
start 19%target 80%
046 wk
architecture and system design
Prove it in “Working prototype: Network Engineer → Data Analyst transition case”: include a distinct output that uses architecture and system design.
start 39%target 85%
057 wk
AI-generated code security
Prove it in “Working prototype: Network Engineer → Data Analyst transition case”: include a distinct output that uses aI-generated code security.
start 25%target 82%
067 wk
observability and DevOps
Prove it in “Working prototype: Network Engineer → Data Analyst transition case”: include a distinct output that uses observability and DevOps.
start 39%target 84%
04 · Choose a pace
Three transition scenarios
The same route affects work, money and fatigue differently. A duration without weekly effort says very little.
Keep your current job
14mo.4 h/week
242 hours total
242 hours total
Two short weekday sessions and one hands-on weekend block.
- First applications
- 11 months
- Trade-off
- Income is protected, but market feedback arrives later.
First apply SQL and data preparation in the current role, then build the portfolio.
Balanced route
9mo.7 h/week
273 hours total
273 hours total
Three weekly sessions: theory, practice and one end-to-end project.
- First applications
- 6 months
- Trade-off
- The pace allows market feedback without abruptly ending the current career.
After the foundation in SQL and data preparation, move into the project and first interviews.
Accelerated entry
6mo.12 h/week
312 hours total
312 hours total
Four study blocks weekly, weekly practice and mentor review.
- First applications
- 4 months
- Trade-off
- The new qualification develops faster, but fatigue and a shallow portfolio are real risks.
Start applying before training ends and improve evidence every week.
05 · If the direct jump is too large
Bridge occupations
These are not mandatory stops. They matter when they provide paid experience in the new kind of work before the full move.
Network Engineer→Analytics Engineer→Data Analyst
in 66%out 87%≈ 14 mo.
The Analytics Engineer role lets you learn part of the new task set in a more familiar context, then approach Data Analyst with stronger evidence.
Network Engineer→AI Workflow Designer→Data Analyst
in 66%out 87%≈ 14 mo.
The AI Workflow Designer role lets you learn part of the new task set in a more familiar context, then approach Data Analyst with stronger evidence.
Network Engineer→Cybersecurity Engineer→Data Analyst
in 58%out 62%≈ 18 mo.
The Cybersecurity Engineer role lets you learn part of the new task set in a more familiar context, then approach Data Analyst with stronger evidence.
06 · Evidence over certificates
Portfolio project
One project cannot replace experience, but it gives an employer something concrete to discuss and shows you can finish real work.
36 hours
Working prototype: Network Engineer → Data Analyst transition case
Take a real but anonymized situation from your current field and solve it as a Data Analyst would. The central project task is a role-specific task.
Your advantage is domain context from Network Engineer. Make it visible: show which beginner mistakes it helps you avoid.
What the project folder should contain
- A repository or interactive prototype with architecture, tests and a demo
- A concise decision memo covering inputs, constraints and two rejected alternatives
- A result check using measurable criteria plus one failed approach and what changed
- A public 5–7-screen case study with all confidential data removed
What makes the project strong
- visible use of sQL and data preparation
- a real-world problem rather than a tutorial exercise
- a measurable outcome and explicit limitations
- enough depth to support technical interview questions
07 · Italia · pay before tax
Income trajectory
In the baseline scenario, modeled income returns to the current level about 45 months after learning begins. This is a scenario model, not a pay promise.
Now€3 560
During study€3 489
First offer€2 531
+1 year€3 074
+2 years€3 450
Model horizon€3 900
Show long-term salary comparison through 2035
08 · Technology horizon
How automation risk changes
The target role is not necessarily safer. By 2035, its modeled risk is 25 points higher. Risk reduction should not be the only reason to move.
2026
32%Network Engineer51%Data Analyst
2028
46%Network Engineer68%Data Analyst
2030
50%Network Engineer73%Data Analyst
2035
56%Network Engineer81%Data Analyst
09 · An honest check
What you may not like
A good career choice is more than a list of benefits. Before studying, check whether you can live with the target role’s daily reality.
Debugging consumes real time
Much of the output is invisible until late; days include root-cause analysis, documentation and detail work.
The daily rhythm will change
The target role contains substantially more working with data and ambiguous conclusions. That can be tiring even when the occupation sounds appealing in theory.
Entry pay may dip
Modeled average pay in the target occupation is lower. A financial buffer or an internal project may help avoid losing seniority.
10 · Where to start
Suggested sequence
- 01
Review 20–30 Data Analyst vacancies and record actual tasks, mandatory requirements and tools.
- 02
Define the bridge from Network Engineer: systems thinking and physical-constraint awareness. Prepare two examples where this experience produced a measurable result.
- 03
Learn SQL and data preparation and visualization and forecasting to the level of completing an independent practical task—not merely finishing a course.
- 04
Build a working prototype, publish the code in a repository, and add tests, documentation and a decision record.
- 05
Review 20–30 vacancies and choose only courses or certificates that repeatedly appear in employer requirements.
- 06
Rewrite your résumé for Data Analyst, add the case and begin with test applications, internships, projects or adjacent tasks at your current employer.
All timelines, salaries and percentages are scenario estimates. They depend on starting skills, location, experience, weekly study time and employer requirements. Validate the route through practitioner conversations, a test project and real vacancies.