System Engineer → Infrastructure Engineer

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

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

Transition from System Engineer to Infrastructure Engineer.

Transferable skills

  • Virtualisation & compute
  • Networking
  • Infrastructure as Code
  • Linux
  • Cloud (hybrid)

Skills to learn

  • Storage & backup
  • Disaster recovery
  • Automation

Step-by-step learning plan

  1. 1. Build on your System Engineer experience

    2–4 weeks

    Leverage

    • Virtualisation & compute
    • Networking
    • Infrastructure as Code
    • Linux

    Map transferable skills — Virtualisation & compute, Networking, Infrastructure as Code — against what an Infrastructure Engineer needs.

  2. 2. Learn the core of the Infrastructure Engineer role

    6–10 weeks

    Learn

    • Storage & backup
    • Disaster recovery

    Technologies

    VeeamCiscoZabbix

    Cover the biggest gaps first: Storage & backup, Disaster recovery.

  3. 3. Master advanced Infrastructure Engineer skills

    6–10 weeks

    Learn

    • Automation

    Technologies

    Nutanix

    Handle the advanced topics: Automation.

  4. 4. Get productive with the Infrastructure Engineer toolchain

    4–8 weeks

    Technologies

    VeeamCiscoZabbixNutanix

    Be hands-on with Veeam, Cisco, Zabbix and the rest of the target stack.

  5. 5. Practise Infrastructure Engineer work in real conditions

    4–8 weeks

    Ship a portfolio project or take on Infrastructure Engineer tasks at work.

  6. 6. Get certified and position yourself as a Infrastructure Engineer

    4–8 weeks

    Technologies

    VMware VCP-DCVAZ-104AWS Solutions Architect Associate

    Update your CV and LinkedIn around Infrastructure Engineer, then apply to target roles.

Alternative routes