Cloud Infrastructure Engineer → Cloud Engineer

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

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

Transition from Cloud Infrastructure Engineer to Cloud Engineer.

Transferable skills

  • AWS / Azure / GCP
  • Terraform
  • Cloud networking
  • Linux
  • Scripting (Python)

Skills to learn

  • Identity & access management
  • Containers
  • Cost optimisation

Step-by-step learning plan

  1. 1. Build on your Cloud Infrastructure Engineer experience

    2–4 weeks

    Leverage

    • AWS / Azure / GCP
    • Terraform
    • Cloud networking
    • Linux

    Map transferable skills — AWS / Azure / GCP, Terraform, Cloud networking — against what a Cloud Engineer needs.

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

    6–10 weeks

    Learn

    • Identity & access management
    • Containers

    Technologies

    LambdaGitLab CI

    Cover the biggest gaps first: Identity & access management, Containers.

  3. 3. Master advanced Cloud Engineer skills

    6–10 weeks

    Learn

    • Cost optimisation

    Handle the advanced topics: Cost optimisation.

  4. 4. Get productive with the Cloud Engineer toolchain

    4–8 weeks

    Technologies

    LambdaGitLab CI

    Be hands-on with Lambda, GitLab CI 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