Cloud Engineer Roadmap

Level: Intermediate

How to follow this roadmap

  1. Lock in Linux and networking fundamentals first — TCP/IP, DNS, HTTP, load balancers, and basic Bash scripting. Cloud engineering without Linux is impossible.
  2. Pick one cloud (AWS for biggest market, Azure for enterprise/Microsoft shops, GCP for data-heavy work) and learn it deep. Don't multi-cloud until you've shipped real systems on one.
  3. Master Infrastructure as Code (Terraform recommended) — modules, state, remote backends, CI integration. Click-ops is fine for learning; everything in production is IaC.
  4. Add containers and Kubernetes once you can deploy a real app to your chosen cloud. Docker first, then EKS/AKS/GKE, then Helm and the wider K8s ecosystem.
  5. Layer on observability (CloudWatch + Datadog or Prometheus + Grafana), security (IAM, VPC design, secrets management), and cost monitoring (FinOps). Then chase a certification — SAA, AZ-104, or ACE — to validate the breadth.

When to choose this path

Choose this roadmap if you want to build and operate the cloud infrastructure that everyone else's code runs on — high-leverage work that pays well and is in constant demand. It's a good fit for system administrators moving up, backend engineers crossing into platform roles, and SRE-curious developers. If your interest is purely application development, frontend or backend roadmaps are better fits. If you want to specialize in CI/CD pipelines, container orchestration, and developer-platform tooling specifically, the DevOps Roadmap drills deeper there.

What you’ll learn

Recommended resources

Frequently asked questions

Which cloud should I learn first?
AWS for the broadest job market in 2026, Azure if you're targeting enterprise or Microsoft-heavy companies, GCP for data and AI-native workloads. Pick one based on the jobs you want; the concepts transfer 70-80% across clouds, so the second one is much faster.
Are cloud certifications worth it?
Yes for getting your first cloud job — recruiters and HR filter on them. Less impactful at senior levels, where shipped systems and incident response stories matter more. The AWS Solutions Architect Associate (SAA), Azure AZ-104, and Google ACE are the high-ROI ones.
AWS Solutions Architect Associate vs Solutions Architect Pro?
Start with SAA — it's the canonical entry-level cloud cert and covers ~80% of what shows up in interviews. SA Pro is significantly harder and only worth it if you're consulting or working in a Pro-level role; many staff cloud engineers never bother.
Terraform vs Pulumi vs CloudFormation?
Terraform for the broadest job market and ecosystem in 2026 — most companies use it. Pulumi is excellent if you prefer real programming languages over HCL and is gaining ground. CloudFormation is AWS-only and increasingly considered legacy outside enterprise AWS shops.
Do I need to know Kubernetes?
For most cloud engineer roles, yes — at least intermediate level. K8s is the de-facto container orchestration standard and shows up in nearly every modern infrastructure stack. Smaller shops sometimes run on ECS/Fargate or Cloud Run instead, which are easier alternatives.
Cloud engineer vs DevOps engineer — what's the difference?
Cloud engineers focus on cloud infrastructure, networking, IaC, and security. DevOps engineers focus on developer-facing pipelines — CI/CD, build systems, deployment automation. Significant overlap, and at small companies the same person does both. At scale they're distinct roles.
How long until I can land a junior cloud role?
6-12 months if you start with some IT or development background. From scratch, expect 12-18 months. The single biggest accelerator is shipping one real public project (a small SaaS, a personal site with proper IaC, or an open-source contribution to a popular IaC module).

Related roadmaps

Last updated: 2026-04-27