How to Become a Cloud Engineer: A Roadmap From IT Basics to Certifications

Cloud engineer job posts can look like alphabet soup: AWS, Azure, Terraform, Kubernetes, CI/CD, IAM, VPC. If you are starting from IT support, or from outside tech entirely, it is hard to know what to learn first and what can wait.

Here is the honest version. Cloud engineering is built on ordinary IT skills: networking, operating systems, security and scripting. The cloud platform is where you apply them. People who skip the foundations usually stall at the certification stage, because they can pass a multiple-choice exam but cannot troubleshoot a broken network route.

This roadmap takes you from IT basics to certifications to hands-on projects, in the order that actually works.

What a cloud engineer does

A cloud engineer designs, builds and runs systems on cloud platforms such as Amazon Web Services (AWS), Microsoft Azure and Google Cloud. Day to day, that can mean:

• Setting up networks, servers, storage and databases in the cloud
• Writing infrastructure as code so environments can be rebuilt reliably
• Managing identity and access so the right people and services have the right permissions
• Automating deployments and backups
• Monitoring performance, fixing outages and keeping costs under control
• Helping move older systems into the cloud

Titles vary: cloud engineer, cloud administrator, cloud operations engineer, cloud infrastructure engineer and, more senior, cloud architect. Cost management is a growing part of the job too. Our guide to FinOps and cloud cost optimization shows why.

Cloud engineer pay and outlook

The U.S. Bureau of Labor Statistics (BLS) does not track “cloud engineer” as its own occupation, so use related categories as benchmarks.

Two things stand out. BLS says continued expansion of cloud computing will increase demand for network architects. It also notes that some traditional systems administration work is shifting to outside services and to DevOps-focused developers. In other words, the classic on-site admin role is shrinking, while cloud and automation skills are where the growth is.

Key takeaway: Cloud engineering is not an entry-level job for most people. It is the next step after you learn IT fundamentals, which is why the fastest route often runs through a help desk or systems role.

Step 1: Build the IT foundations

Do not skip this stage. Every cloud problem eventually becomes a networking, operating system or permissions problem.

• Networking: IP addressing and subnets, DNS, routing, firewalls, load balancers, VPNs and how HTTP works. CompTIA Network+ (exam N10-009) is a solid vendor-neutral benchmark.
• Linux: The command line, file permissions, processes, package management, logs and SSH. Most cloud servers run Linux.
• Security basics: Least privilege, multi-factor authentication, encryption and logging. Our explainer on zero trust security covers the model most cloud teams now follow.
• Scripting: Bash for automation and Python for anything bigger.
• Git: Version control is how infrastructure code is shared and reviewed.

If you are brand new to IT, start with our guide on how to get an entry-level IT job. A year of support work teaches troubleshooting that no course can.

Step 2: Choose one cloud platform and certify

Pick one platform to start. AWS, Azure and Google Cloud share the same core concepts, so the second one is much easier to learn after the first. Choose based on what employers in your area use: scan 20 local job posts and count.

Certification paths by platform

The figures below come from each vendor’s official certification pages as of October 2026. Prices and formats change, so check before booking.

The entry certifications are optional if you already have IT experience. The associate level is what most cloud job posts mention.

Step 3: Learn infrastructure as code and automation

Clicking around a cloud console is fine for learning. Real teams define infrastructure in code so it can be reviewed, versioned and rebuilt.

• Infrastructure as code (IaC): Terraform is widely used across clouds. Each platform also has its own tools, such as AWS CloudFormation, Azure Bicep and Google Cloud’s deployment tools. HashiCorp’s Terraform Associate (004) exam costs $70.50, runs 1 hour and is valid for 2 years, according to HashiCorp.
• CI/CD: Pipelines that test and deploy changes automatically, using tools such as GitHub Actions, GitLab CI or Azure DevOps.
• Containers: Docker basics, then an introduction to Kubernetes.
• Monitoring: Logs, metrics, alerts and dashboards.

These skills overlap heavily with DevOps. If automation is the part you enjoy most, read our roadmap on how to become a DevOps engineer.

Step 4: Build hands-on cloud projects

Certifications get your resume read. Projects get you hired. All 3 major providers offer free options for new accounts. As of October 2026, AWS gives new customers up to $200 in credits on a free plan that lasts up to 6 months, Azure offers $200 in credit for 30 days plus some services free for 12 months, and Google Cloud offers $300 in credits for 90 days. Terms change, so read the current offer.

Set billing alerts on day 1. Even small mistakes, like leaving a large server running, can cost money once you move to a paid plan.

Project ideas that look like real work

1. Static website with a custom domain, served through a CDN with HTTPS, all defined in Terraform.
2. Three-tier web app: load balancer, auto-scaling app servers and a managed database in private subnets.
3. Serverless API with a function, an API gateway and a database, plus logging and alerts.
4. CI/CD pipeline that tests and deploys your app on every commit.
5. Cost and security review of your own environment: tag resources, set budgets and lock down permissions, then write up what you found.

Document each one with a diagram, the code in a public repo and a short write-up. Our guide on how to build a tech portfolio shows the format.

Step 5: Land your first cloud role

Most people do not jump straight from a course to “cloud engineer.” Common paths:

• Help desk to systems admin to cloud. Ask to help with cloud tasks at your current job, such as user management in Microsoft Entra ID or backups to cloud storage.
• Systems or network admin to cloud. The most natural move. Your existing skills transfer directly.
• Developer to cloud. Developers who learn infrastructure and deployment are valuable on cloud and platform teams.
• Junior cloud support or operations roles at cloud providers, managed service providers and consultancies.

On your resume, lead with projects and certifications, and describe them in the language of the job post: “Deployed a 3-tier application with Terraform and automated deployments with GitHub Actions.”

Where to start this month

1. Week 1: Read 20 cloud job posts in your area. Note which platform and tools come up most.
2. Week 2: Fill your biggest foundation gap: networking, Linux or scripting.
3. Week 3: Open a free account on your chosen platform, set billing alerts and deploy a static site.
4. Week 4: Book a date for the associate certification 8 to 12 weeks out, and start studying with hands-on labs.

The bottom line

Becoming a cloud engineer is a sequence, not a leap. Learn networking, Linux, security and scripting. Pick one platform and earn its associate certification. Learn infrastructure as code and build 2 or 3 projects you can show. Then use an IT, admin or development role as your launch pad. That path takes longer than a crash course promises, but it produces engineers who can actually fix things.

Sources

• U.S. Bureau of Labor Statistics, Network and Computer Systems Administrators — pay, outlook and shifts in admin work
• U.S. Bureau of Labor Statistics, Computer Network Architects — pay, experience required and cloud-driven demand
• AWS Certified Solutions Architect – Associate — exam cost, length and recommended experience
• Microsoft Certified: Azure Administrator Associate — exam AZ-104 and renewal policy
• Google Cloud Associate Cloud Engineer — exam fee, length and recommended experience
• AWS Free Tier — free plan credits and duration for new accounts