Cloud Engineer Roadmap Cheatsheet: Full Path in One Page

The cloud engineering career path has a logical shape. There are foundations you need before the core skills make sense. There are core skills you need before you are hirable. And there is ongoing growth once you are in the door. This cheatsheet compresses that full path into one page.

The roadmap has four phases: Foundation, Core Skills, Job-Ready, and Growth.

Phase 1: Foundation (Weeks 1–4)#

Before cloud services make sense, you need to understand what is underneath them.

What to cover:

• Linux basics — file system navigation, permissions (chmod/chown), running processes, SSH access
• Networking fundamentals — IP addressing and CIDR notation, DNS, HTTP/HTTPS, TCP/UDP, what a firewall does
• Scripting basics — Python or Bash for automation. You do not need to be a developer, but you need to be able to write a script that does something useful.
• What the cloud actually is — IaaS vs PaaS vs SaaS, regions and availability zones, the shared responsibility model

Phase 1 milestone: You can launch a VM in a cloud console, SSH into it, run commands on it, and explain what you are doing and why.

Common mistake in Phase 1: Skipping Linux and networking because they feel like prerequisites rather than “real cloud stuff.” They are the real cloud stuff. Everything else builds on them.

Phase 2: Core Skills (Weeks 5–16)#

This is the longest phase. It is where you build the skills that get you hired.

Pick one cloud provider and go deep:

• AWS — largest job market, widest range of roles
• GCP — strong for data, ML, and modern infrastructure patterns
• Azure — dominant in Microsoft-heavy enterprises and public sector

Do not try to learn all three at once. The concepts transfer. The specifics differ enough to be confusing if you switch constantly.

Core services (hands-on, not just reading):

• Compute: launch VMs, configure auto-scaling, understand instance types
• Storage: create object storage buckets, set access controls, understand lifecycle policies
• Networking: create a VPC, configure subnets, set up a load balancer
• IAM: create roles and service accounts, apply least privilege policies, understand the difference between identity and resource policies

Infrastructure as Code:

Learn Terraform basics. Write a configuration file, run terraform init, terraform plan, terraform apply. Deploy a real resource. Understand what state is and why it matters.

Containers:

Build a Docker image from a Dockerfile. Run it locally. Push it to a container registry. Understand what a container is and why it is different from a VM.

Kubernetes basics:

Understand pods, deployments, and services. Deploy something to a cluster (use a managed one — EKS, GKE, or AKS). You do not need deep Kubernetes expertise at this stage.

CI/CD:

Build a basic pipeline using GitHub Actions or GitLab CI. It should do something on every push — run a test, build an image, deploy a resource.

Phase 2 milestone: You have deployed a real project using IaC, containers, and a CI/CD pipeline. It is on GitHub with a README.

Common mistake in Phase 2: Watching tutorials without building anything. Tutorials create the illusion of learning. Deploying things and breaking them creates actual learning.

Phase 3: Job-Ready (Weeks 17–24)#

This phase is about packaging your skills for the market.

Get certified:

Sit an associate-level certification: AWS Solutions Architect Associate, GCP Associate Cloud Engineer, or AZ-104. This gets your CV through automated screening and demonstrates you have studied to a recognised standard.

Build 2–3 portfolio projects:

Each project should demonstrate a distinct skill or combination of skills. Document them well. A GitHub repository with a clear README, an architecture diagram, and working code is worth more than a certification alone.

Prepare your CV:

Write experience and project bullets that show outcomes, not just tasks. List certifications with full official names. Include a skills section that is accurate and scannable.

Start applying:

Apply before you feel completely ready. You will learn more from the application and interview process than from another week of studying.

Interview prep:

Review the core topics (networking, IAM, compute, storage). Practice answering scenario questions out loud. Prepare STAR stories from your projects.

Phase 3 milestone: First interview booked.

Common mistake in Phase 3: Waiting until you know everything before applying. There is no point at which you will feel fully ready. Apply when you have a project, a cert, and a CV that represents your real skills.

Phase 4: Growth (Ongoing from First Job)#

Once you are in your first cloud role, the learning compounds faster than it did on your own.

Deepen one specialisation:

• DevOps / platform engineering: focus on Kubernetes, CI/CD, IaC at scale
• Site reliability engineering: focus on observability, incident response, reliability patterns
• Cloud security: focus on IAM, compliance, threat modelling, security tooling
• Data / ML infrastructure: focus on managed data services, pipelines, cost at scale

Get a professional-level certification in your chosen path once you have 12–18 months of hands-on experience behind it.

Build domain knowledge: cloud skills plus knowledge of your industry (finance, healthcare, retail, etc.) make you significantly more valuable than cloud skills alone.

Common mistake in Phase 4: Staying a generalist indefinitely. Breadth gets you in the door; depth gets you promoted or into more interesting and better-paid roles.

Am I Ready to Apply? Checklist#

• I have hands-on experience with compute, storage, networking, and IAM on at least one cloud provider
• I have deployed a project using Terraform (or another IaC tool)
• I can explain VPCs, subnets, and security groups clearly
• I have a GitHub profile with at least one documented cloud project
• I have or am preparing for an associate-level certification
• I have a CV with specific, outcome-focused bullets
• I can answer “how would you design a highly available web app?” in rough terms
• I can explain the difference between authentication and authorisation

Ticking 6 out of 8 is enough to start applying. You do not need to tick all 8 first.

Realistic Timeline#

“Consistent effort” means 1–2 hours on working days plus longer sessions on weekends. Learning passively for a few minutes per day will not get you there.