HTD Talent

How to become a cloud engineer

By HTD Talent editorial team Updated 9 min read

The short answer

To become a cloud engineer, learn Linux and networking, then Python, then one cloud provider (AWS or Azure) in depth, then Terraform, containers with Kubernetes, and CI/CD. HTD Talent's program data puts that at 176 hours of study, about 18 weeks at 10 hours a week. Most people land an IT support or sysadmin job first.

Key takeaways

  • Cloud engineering is a stack of six skills, and the order matters because each one sits on the one before it.
  • Python and automation show up in more than half of the job postings HTD Talent sampled for its Cloud and DevOps program.
  • One associate-level cert (AWS Solutions Architect Associate or Azure AZ-104) plus projects you can show beats a pile of entry-level badges.
  • With no experience, the usual route runs through help desk, IT support or systems administration before the cloud title.
  • BLS doesn't track "cloud engineer" as its own job, so use network architects and systems administrators as your closest reference points.

What a cloud engineer does (and why BLS can't tell you)

A cloud engineer builds and runs the servers, networks and storage a company rents from AWS, Microsoft Azure or Google Cloud. Most of that work happens in code. You write the files that create infrastructure, the pipelines that ship software, and the alerts that wake someone up when it breaks.

The U.S. Bureau of Labor Statistics has no "cloud engineer" occupation. The work is split across a few codes, and it's worth knowing which ones are closest so you can read the numbers accurately.

BLS occupation Median pay (May 2025) Projected change, 2025 to 2035 How it maps to cloud work
Computer network architects $134,050 +8% Closest senior match. BLS says cloud expansion will drive demand.
Network and computer systems administrators $99,130 -4% The on-premises version of the job, and a common feeder role.
Computer network support specialists $76,220 +1% Typical entry point for people without IT experience.

Read that table as a career ladder. BLS lists "5 years or more" of related experience for network architects, and the OOH page says architects usually need several years working with IT systems. The sysadmin decline matters too. BLS notes some of that work is moving to outside providers, which is one reason admins who learn cloud tooling have more options than admins who don't.

How to become a cloud engineer in 6 steps

Take these in order. Skipping Linux to get to Kubernetes faster is a fast way to stall out.

Step 1. Learn Linux and networking basics

Almost every cloud server runs Linux, and almost every cloud outage is a networking problem in disguise. Get comfortable in a terminal: files, permissions, processes, package managers, SSH and logs.

For networking, learn IP addressing, subnets and CIDR notation, DNS, HTTP, load balancers and firewalls. You'll use subnets on day one of building anything in AWS or Azure. HTD Talent's IT and Networking program covers this layer in 106 hours, and half of the postings in that program's sample (50%) ask for Linux.

Step 2. Pick up a scripting language (Python first)

Python is the default. In HTD Talent's program data (October 2026), 57% of sampled Site Reliability Engineer postings mention Python, and 56% mention automation. Bash is the second language you'll pick up along the way. If you're heading into a Microsoft shop, add PowerShell, which shows up in 41% of the sysadmin postings HTD sampled.

You don't need software-engineer depth. Aim to write a script that calls an API, parses JSON, loops through a list of servers and handles errors without crashing.

Step 3. Go deep on one cloud provider

Pick AWS or Azure and stay there until you can build without a tutorial open. Look at job postings in your city and choose whichever shows up more. The concepts transfer, so the second cloud is much faster to learn later.

"Deep" means you can set up identity and access (IAM), a virtual network with public and private subnets, compute, storage, a managed database, monitoring, and a budget alert so you don't get a surprise bill.

Step 4. Write infrastructure as code with Terraform

Clicking around the console is fine for learning. Employers want infrastructure written as code so it can be reviewed, versioned and rebuilt. Terraform is a widely used tool for this, and it works across AWS, Azure and Google Cloud.

Rebuild everything you made in Step 3 as Terraform files. Then destroy it and rebuild it from scratch. That exercise teaches more than any course module.

Step 5. Learn containers and Kubernetes

Start with Docker. Package a small app into a container, run it locally, and push the image to a registry. Then move to Kubernetes, which runs and scales those containers across many machines.

Kubernetes appears in 39% of the SRE postings in HTD Talent's sample. Learn pods, deployments, services, config maps and secrets first. Then try a managed version (Amazon EKS or Azure AKS) so you see how it plugs into the cloud you already know.

Step 6. Automate deployments with CI/CD

CI/CD pipelines test and ship code every time someone pushes a change. 34% of the SRE postings HTD sampled ask for it. Use GitHub Actions or GitLab CI to build a pipeline that runs tests, builds your container and applies your Terraform.

That last pipeline is your portfolio. One repo that goes from a code push to running infrastructure, with a README explaining your choices, is the single best thing to show a hiring manager.

Cloud engineer skills employers ask for

Here's how often each skill shows up in the job postings behind HTD Talent's Cloud and DevOps program, which targets the Site Reliability Engineer role.

Share of sampled SRE job postings that mention each skill

  1. Python57%
  2. Automation56%
  3. Kubernetes39%
  4. CI/CD34%
Source: HTD Talent program data (October 2026), built from live job-posting data

Two things stand out. Python and automation lead by a wide margin, so the scripting step is the one to overinvest in. And no single tool appears in every posting, which is why going deep on one stack beats collecting logos on a resume.

The soft skill that matters most is troubleshooting under pressure. You'll spend real hours reading logs and figuring out why something worked yesterday and doesn't today.

Cloud engineer certifications worth the exam fee

Certifications help most when you have no cloud job on your resume yet. They give a recruiter a filter to say yes to. Here's what the four most common starter exams involve, from the vendors' own pages.

Certification Exam length Format Cost Who it's for
AWS Certified Cloud Practitioner 90 minutes 65 multiple choice or multiple response $100 Newcomers. AWS says no prior AWS experience is required.
AWS Certified Solutions Architect Associate 130 minutes 65 multiple choice or multiple response $150 AWS recommends at least 1 year of hands-on AWS design experience. Valid 3 years.
Microsoft Azure Fundamentals (AZ-900) 45 minutes Score of 700 or higher to pass Varies by country Anyone starting with Azure.
Microsoft Azure Administrator Associate (AZ-104) 100 minutes See Microsoft's study guide Varies by country People who run Azure environments. Renews every 12 months via a free online assessment.

Our take: skip the fundamentals exam if you're working through all six steps above, and go straight for Solutions Architect Associate or AZ-104. The entry exams are useful if you need a structured first goal or your employer pays for them. The associate exams are the ones hiring managers recognize.

If you want a Terraform credential later, HashiCorp's Terraform Associate is an hour-long multiple-choice exam. Get it after you've written real Terraform.

How to become a cloud engineer with no experience

Few people get hired straight into a cloud engineer title with no IT background. The title assumes you've already kept systems running for someone. The people who make the jump usually come through one of these doors:

  • IT support or help desk, where you learn tickets, users, Windows, networking and how to stay calm when things break.
  • Systems administration, which is the closest on-premises cousin of cloud work.
  • Junior DevOps or "cloud support associate" roles, which some larger companies post for people with certs and projects.
  • Software development, for people who already code and want to move toward infrastructure.
  • Internal moves, where you volunteer for the cloud migration project at the company you already work for.

That last one is underrated. If your current employer is moving anything to AWS or Azure, ask to help. Internal experience counts on a resume.

If you're starting from zero, a realistic plan is the IT and Networking program first (106 hours of study, about 11 weeks at 10 hours a week), a support or admin job, then the Cloud and DevOps program on top. Not sure which layer you need? Build your own plan, skip what you already know, and set your weekly hours.

How long it takes to become a cloud engineer

Study time and hiring time are different clocks. HTD Talent's program data measures the first one: hours of study to reach job-ready skills. It doesn't measure how long a job search takes.

Program Study hours 5 hrs/week 10 hrs/week 20 hrs/week
IT and Networking 106 22 weeks 11 weeks 6 weeks
Cloud and DevOps 176 36 weeks 18 weeks 9 weeks

If you already work in IT, the Cloud and DevOps hours are your number. If you're starting cold, add both together, roughly 280 hours, and plan for a year or more of on-the-job experience before a cloud title. For a broader look at how study hours turn into calendar time, see our guide on how long it takes to learn to code.

When cloud engineering is the wrong move

This path isn't for everyone, and it's better to know now.

Skip it if you hate troubleshooting. Much of the job is figuring out why a deploy failed at 4 p.m. on a Friday. If ambiguous problems drain you, look at data analytics or QA instead.

Think twice if you want the fastest possible first tech job. Cloud roles sit higher on the ladder, and BLS's own numbers show the senior version of this work expects years of experience. A support or admin role first is the honest timeline.

And reconsider if you're chasing it purely for pay. The table above shows a wide spread between support specialists and architects. Most of that gap comes from years on the job. A certificate alone won't close it.

If you're unsure, speak with a recruiter on a free call. They can look at your background and tell you whether to start at the IT layer or the cloud layer. You can also browse all ready-made programs to compare paths.

Frequently asked questions

Do I need a computer science degree to become a cloud engineer?

BLS lists a bachelor's degree as the typical entry education for both network architects and systems administrators. In practice, many cloud teams weigh certifications, a working portfolio and prior IT experience heavily. A degree helps with some large employers and government roles, so check the postings you're targeting.

Is AWS or Azure better to learn first?

It depends on who's hiring near you. Azure tends to show up at companies that already run Microsoft software. Search job boards in your city for both and pick the one with more openings near you.

What's the difference between a cloud engineer and a site reliability engineer?

A cloud engineer usually focuses on building and managing cloud infrastructure. A site reliability engineer (SRE) focuses on keeping services fast and available, using monitoring, automation and incident response. The skill sets overlap heavily, which is why HTD Talent's Cloud and DevOps program targets the SRE role.

Can I practice without paying for cloud services?

Yes. AWS, Azure and Google Cloud all offer free tiers or trial credits for new accounts. Set a billing alert on day one and tear down resources when you're done, since a forgotten database or load balancer is the classic surprise bill.

Sources

HTD Talent editorial team

HTD Talent recruits, staffs and trains technology talent, and writes these guides from job-posting data, BLS figures and the questions we hear every week. How we research and update guides.

Turn this into your plan.

Pick a job, tap what you already know and set your hours. You'll see every step and the total before you pay.

Build my plan
Headline
Hero
Grid
Grid
Cards
Table
Tone