Infrastructure Engineer → Cloud Infrastructure Engineer

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

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

Transition from Infrastructure Engineer to Cloud Infrastructure Engineer.

Transferable skills

  • Cloud networking
  • Linux

Skills to learn

  • AWS / Azure / GCP
  • Terraform
  • IAM
  • Kubernetes
  • Scripting
  • Security

Step-by-step learning plan

  1. 1. Build on your Infrastructure Engineer experience

    2–4 weeks

    Leverage

    • Cloud networking
    • Linux

    Map transferable skills — Cloud networking, Linux — against what a Cloud Infrastructure Engineer needs.

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

    6–10 weeks

    Learn

    • Terraform
    • AWS / Azure / GCP
    • IAM

    Technologies

    GCPCloudFormationDocker

    Cover the biggest gaps first: Terraform, AWS / Azure / GCP, IAM.

  3. 3. Master advanced Cloud Infrastructure Engineer skills

    6–10 weeks

    Learn

    • Scripting
    • Security
    • Kubernetes

    Technologies

    IAMS3EKS

    Handle the advanced topics: Scripting, Security, Kubernetes.

  4. 4. Get productive with the Cloud Infrastructure Engineer toolchain

    4–8 weeks

    Technologies

    GCPCloudFormationDockerIAMS3EKSPrometheusVault

    Be hands-on with GCP, CloudFormation, Docker and the rest of the target stack.

  5. 5. Practise Cloud Infrastructure Engineer work in real conditions

    4–8 weeks

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

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

    4–8 weeks

    Technologies

    AWS Solutions Architect AssociateAzure AZ-104Terraform Associate

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