Infrastructure Engineer → Cloud Engineer

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

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

Transition from Infrastructure Engineer to Cloud Engineer.

Transferable skills

  • Cloud networking
  • Linux

Skills to learn

  • AWS / Azure / GCP
  • Terraform
  • Identity & access management
  • Containers
  • Cost optimisation
  • Scripting (Python)

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 Engineer needs.

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

    6–10 weeks

    Learn

    • AWS / Azure / GCP
    • Terraform
    • Identity & access management

    Technologies

    GCPCloudFormationDocker

    Cover the biggest gaps first: AWS / Azure / GCP, Terraform, Identity & access management.

  3. 3. Master advanced Cloud Engineer skills

    6–10 weeks

    Learn

    • Containers
    • Cost optimisation
    • Scripting (Python)

    Technologies

    IAMS3EKS

    Handle the advanced topics: Containers, Cost optimisation, Scripting (Python).

  4. 4. Get productive with the Cloud Engineer toolchain

    4–8 weeks

    Technologies

    GCPCloudFormationDockerIAMS3EKSLambdaGitLab CI

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

  5. 5. Practise Cloud Engineer work in real conditions

    4–8 weeks

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

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

    4–8 weeks

    Technologies

    AWS Solutions Architect AssociateAZ-104Terraform Associate

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

Alternative routes