LAN/WAN Engineer → SD-WAN Engineer

A realistic transition from LAN/WAN Engineer to SD-WAN Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 58%. Difficulty: Medium.

Difficulty: Medium7 stepsDuration: 9 to 13 monthsOverlap: 58%

Transition from LAN/WAN Engineer to SD-WAN Engineer.

Transferable skills

  • Routing
  • Security
  • Troubleshooting
  • Monitoring

Skills to learn

  • SD-WAN (Veloce/Fortinet)
  • Automation
  • Cloud networking

Step-by-step learning plan

  1. 1. Build on your LAN/WAN Engineer experience

    2–4 weeks

    Leverage

    • Routing
    • Security
    • Troubleshooting
    • Monitoring

    Map transferable skills — Routing, Security, Troubleshooting — against what a SD-WAN Engineer needs.

  2. 2. Close the partial gaps toward SD-WAN Engineer

    3–6 weeks

    Improve

    • Scripting

    Raise Scripting to the level a SD-WAN Engineer relies on.

  3. 3. Learn the core of the SD-WAN Engineer role

    6–10 weeks

    Learn

    • SD-WAN (Veloce/Fortinet)
    • Automation

    Technologies

    VeloCloudFortinetCisco Viptela

    Cover the biggest gaps first: SD-WAN (Veloce/Fortinet), Automation.

  4. 4. Master advanced SD-WAN Engineer skills

    6–10 weeks

    Learn

    • Cloud networking

    Technologies

    AnsibleAWSAzure

    Handle the advanced topics: Cloud networking.

  5. 5. Get productive with the SD-WAN Engineer toolchain

    4–8 weeks

    Technologies

    VeloCloudFortinetCisco ViptelaAnsibleAWSAzure

    Be hands-on with VeloCloud, Fortinet, Cisco Viptela and the rest of the target stack.

  6. 6. Practise SD-WAN Engineer work in real conditions

    4–8 weeks

    Ship a portfolio project or take on SD-WAN Engineer tasks at work.

  7. 7. Get certified and position yourself as a SD-WAN Engineer

    4–8 weeks

    Technologies

    Fortinet NSE 5 SD-WANCisco SD-WANVMware VeloCloud

    Update your CV and LinkedIn around SD-WAN Engineer, then apply to target roles.