Junior Cloud Engineer → Cloud Engineer

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

Difficulty: Medium7 stepsDuration: 9 to 13 monthsOverlap: 53%

Transition from Junior Cloud Engineer to Cloud Engineer.

Transferable skills

  • Linux

Skills to learn

  • Identity & access management
  • Containers
  • Cost optimisation

Prerequisites

  • Hands-on with one cloud provider: compute, storage, networking and IAM basics.
  • Infrastructure as code with Terraform for simple, reproducible provisioning.
  • Git for versioning infrastructure and configuration changes.
  • Basic Linux command line and networking troubleshooting.

Step-by-step learning plan

  1. 1. Build on your Junior Cloud Engineer experience

    2–4 weeks

    Leverage

    • Linux

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

  2. 2. Close the partial gaps toward Cloud Engineer

    3–6 weeks

    Improve

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

    Raise AWS / Azure / GCP, Terraform, Cloud networking to the level a Cloud Engineer relies on.

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

    6–10 weeks

    Learn

    • Identity & access management
    • Containers

    Technologies

    GCPCloudFormationEKS

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

  4. 4. Master advanced Cloud Engineer skills

    6–10 weeks

    Learn

    • Cost optimisation

    Technologies

    LambdaGitLab CIVault

    Handle the advanced topics: Cost optimisation.

  5. 5. Get productive with the Cloud Engineer toolchain

    4–8 weeks

    Technologies

    GCPCloudFormationEKSLambdaGitLab CIVaultPrometheus

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

  6. 6. Practise Cloud Engineer work in real conditions

    4–8 weeks

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

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

Learning outcomes

  • Design and operate a secure landing zone with proper networking and IAM boundaries.
  • Own cloud workloads end to end: cost, security, performance and availability.
  • Automate provisioning and operations with Terraform and scripts.
  • Apply tagging, cost controls and basic FinOps practices to cloud spend.

Practical projects

  • Build a secure landing zone — Provision a VPC/VNet with public and private subnets, a NAT gateway, security groups and an IAM role for a workload — all in Terraform.
  • Set up monitoring and alerts — Deploy a small workload and configure CloudWatch, Azure Monitor or Prometheus alerts on availability and latency, then test an alert.
  • Estimate and reduce cost — Tag all resources, review the monthly bill, identify one waste (idle resource or oversized instance) and right-size it.

Alternative routes