Roadmaps
Cloud Engineer Roadmap 2026
The most common mistake in learning cloud engineering is spreading thin across three providers at once -- this roadmap goes deep on one first.
Stage 1: Networking and Systems Fundamentals (3-4 weeks)
- IP addressing, subnets, and CIDR notation
- DNS, load balancing, and firewalls
- Linux fundamentals -- most cloud infrastructure runs on it
- Example: manually design (on paper) a simple network layout with a public and private subnet
Stage 2: Pick One Cloud Provider and Go Deep (6-8 weeks)
- Compute (EC2 / Azure VMs / Compute Engine)
- Storage (S3 / Blob Storage / Cloud Storage)
- Identity and access management
- Managed databases
- Example: manually deploy a simple two-tier app (a web server + database) using the console, to understand what's actually happening before automating it
Stage 3: Infrastructure as Code (3-4 weeks)
- Terraform (cloud-agnostic) or the provider's native IaC tool (CloudFormation, Bicep)
- State management and modules
- Example: rebuild the Stage 2 deployment entirely in Terraform, so it's reproducible from code
Stage 4: Containers and Automation (3-4 weeks)
- Docker fundamentals
- A managed Kubernetes service (EKS, AKS, or GKE)
- A basic CI/CD pipeline for automated deployment
- Example: containerize and deploy the app to a managed Kubernetes cluster with an automated pipeline
Stage 5: Security and Cost Optimization (2-3 weeks)
- Least-privilege IAM policies
- Cost monitoring and right-sizing resources
- Example: audit the deployed infrastructure for overly broad permissions and unused resources
Stage 6: Certification (2-4 weeks, in parallel)
- A foundational certification for your chosen provider (AWS Cloud Practitioner, AZ-900, or GCP's equivalent)
- An associate-level certification once you have real hands-on practice (AWS Solutions Architect Associate, AZ-104)
Frequently Asked Questions
AWS has the largest market share and job listings overall, making it a safe default choice if you have no other constraint. But if your target companies or region skew toward Azure (common in enterprise/.NET shops) or GCP (common in data-heavy companies), match that instead -- the underlying concepts transfer between all three.
They're a genuinely useful structured way to learn and a real resume signal, especially for candidates without much hands-on cloud experience yet -- but hands-on projects you can actually discuss in an interview matter more than the certification alone. Do both, in the order shown above (learn by building first, certify as a formal checkpoint).