Virtualization Engineer → VMware Engineer

A realistic transition from Virtualization Engineer to VMware Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 45%. Difficulty: Easy.

Difficulty: Easy7 stepsDuration: 4 to 8 monthsOverlap: 45%

Transition from Virtualization Engineer to VMware Engineer.

Transferable skills

  • Storage
  • Networking
  • DR

Skills to learn

  • vSphere / vCenter
  • NSX
  • vSAN
  • Horizon

Step-by-step learning plan

  1. 1. Build on your Virtualization Engineer experience

    2–4 weeks

    Leverage

    • Storage
    • Networking
    • DR

    Map transferable skills — Storage, Networking, DR — against what a VMware Engineer needs.

  2. 2. Close the partial gaps toward VMware Engineer

    3–6 weeks

    Improve

    • PowerCLI

    Raise PowerCLI to the level a VMware Engineer relies on.

  3. 3. Learn the core of the VMware Engineer role

    6–10 weeks

    Learn

    • vSphere / vCenter
    • NSX

    Technologies

    vCentervSANHorizon

    Cover the biggest gaps first: vSphere / vCenter, NSX.

  4. 4. Master advanced VMware Engineer skills

    6–10 weeks

    Learn

    • vSAN
    • Horizon

    Technologies

    AWSAzure

    Handle the advanced topics: vSAN, Horizon.

  5. 5. Get productive with the VMware Engineer toolchain

    4–8 weeks

    Technologies

    vCentervSANHorizonAWSAzure

    Be hands-on with vCenter, vSAN, Horizon and the rest of the target stack.

  6. 6. Practise VMware Engineer work in real conditions

    4–8 weeks

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

  7. 7. Get certified and position yourself as a VMware Engineer

    4–8 weeks

    Technologies

    VMware VCP-DCVVMware VCAP-DCVVMware NSX-T

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