Cloud Engineer Roadmap 2026
Build and operate cloud infrastructure: identity, storage, compute, networking, monitoring and automation across Azure, Google Cloud and AWS.
4 stages · 8 units · Intermediate · about 110 hours · Last reviewed 19 November 2026
What is a cloud engineer?
A cloud engineer builds and runs infrastructure on platforms such as Azure, Google Cloud and AWS. The work includes setting up accounts and identity, provisioning storage and compute, designing virtual networks, directing traffic, monitoring systems and automating recovery. The goal is reliable, secure infrastructure that applications can run on without manual effort.
Step-by-step cloud engineer roadmap
- 1
Setup and Governance
Beginner · about 30 hours
Start safely.
- Environment
A cloud environment is the structure of accounts, subscriptions or projects, and identity controls that everything else is built inside. Setting it up correctly means separating workloads, applying role-based access with least privilege and protecting the highest-privilege identities, because mistakes here are hard to fix once resources exist.
- Tooling
Cloud tooling means the command-line interfaces, web portals and SDKs used to manage resources. The portal is good for exploring, while the CLI and scripts make tasks repeatable and automatable. Learning to move from clicking to commands is the first step toward infrastructure as code.
- Environment
- 2
Storage and Compute
Intermediate · about 30 hours
Run workloads.
- Storage
Cloud storage services hold files and data durably at scale. Object storage such as buckets and storage accounts keeps blobs accessed over HTTP, with tiers that trade cost against access speed and policies for access and lifecycle. It is used for backups, logs, media and static website content.
- Compute
Cloud compute is the set of services that run your code, from virtual machines you manage fully, to container platforms, to app services that hide the servers. This unit covers how to size and launch VMs and when a container or managed app platform is a better fit.
- Storage
- 3
Networking
Intermediate · about 30 hours
Connect it.
- Virtual Networks
A virtual network is a private, isolated network in the cloud where you place resources. It is divided into subnets from a CIDR address range, with route tables controlling paths and security groups or network security groups filtering traffic. Good subnet design keeps public-facing and private components separate.
- Traffic
Traffic management is how user requests reach healthy servers. DNS translates names to addresses, and load balancers distribute connections across instances using health checks, working at layer 4 for TCP or layer 7 for HTTP. Together they provide a stable entry point, high availability and the ability to scale out.
- Virtual Networks
- 4
Operations
Advanced
Keep it healthy.
- Monitoring
Cloud monitoring is the collection and analysis of metrics and logs from resources so teams can see health, detect problems and be alerted. Services such as CloudWatch, Azure Monitor and Cloud Monitoring gather CPU, latency and error data, while log search helps explain what happened during an incident.
- Recovery
Recovery and automation cover how to restore services after failure and remove manual work. Backups, snapshots and cross-region copies protect data, while scripts and infrastructure as code rebuild environments consistently. A backup counts only when its restore has been tested.
- Monitoring
Frequently asked questions
Ready to practise for interviews?
Practise cloud engineer questions with an AI mock interviewer and get feedback on your answers.