What is a cloud engineer?
A cloud engineer is an IT professional who designs, builds, manages and maintains an organisation’s cloud infrastructure and services — the person who makes sure applications run reliably, securely and cost-effectively on platforms like AWS, Azure or Google Cloud. It is a broad title that spans provisioning servers and networks, automating infrastructure with code, securing and monitoring what is running, and troubleshooting when something breaks. This article covers what the role actually does day to day, the skills it requires, how it relates to nearby titles like DevOps engineer, and how to work toward it.
What a cloud engineer actually does
Day to day, the work centres on a handful of recurring responsibilities: provisioning and managing infrastructure — servers, storage, networks and databases — on a cloud platform; automating that provisioning with infrastructure as code, so environments are reproducible rather than clicked together by hand; configuring networking, so services can reach each other and the internet securely; applying security controls, from access permissions to encryption; monitoring systems and responding when something fails; and keeping an eye on cost, since cloud bills scale with usage and unmanaged spend is a common failure mode.
The exact mix varies enormously by employer. A cloud engineer at a small company might touch all of the above plus application deployment; at a large enterprise, the role is often narrower — focused specifically on networking, or security, or a particular platform — with other specialists covering the rest. There is no single "cloud engineer job" so much as a cluster of closely related ones sharing the same underlying skill set.
The core skills
A working cloud engineer typically needs: fluency in at least one major cloud platform (AWS, Azure or Google Cloud); comfort with Linux, since a large share of cloud workloads run on it — our guide on whether you need to know Linux for cloud computing covers this in depth; solid networking fundamentals (IP addressing, DNS, load balancing, firewalls); infrastructure as code, most commonly Terraform or a provider-native tool, for provisioning reproducibly rather than by hand; enough scripting ability (commonly Python or Bash) to automate routine tasks; and security fundamentals — identity and access management, encryption, least-privilege thinking — because a cloud engineer is frequently the person who configures who can access what.
None of these need to be mastered before you start; they are built up through structured study and hands-on practice over time, and a certification path is a common way to sequence that learning.
How it relates to nearby roles
"Cloud engineer" overlaps heavily with several adjacent titles, and the boundaries between them are genuinely blurry in practice — job adverts often use the titles inconsistently. A DevOps engineer shares much of the same toolkit but is typically more focused on the software delivery pipeline itself — CI/CD, deployment automation, developer workflow — where a cloud engineer is more focused on the infrastructure the pipeline deploys onto; our dedicated comparison of cloud engineer versus DevOps engineer covers that distinction properly. A site reliability engineer (SRE) applies software-engineering discipline specifically to reliability and incident response. A cloud architect works at a higher, more strategic level, designing systems rather than implementing and operating them day to day. A cloud administrator leans more toward operating existing infrastructure than building new systems. In smaller organisations, one person often wears several of these hats at once.
How to become one
The common path runs: foundations first (general IT and networking basics, and comfort with Linux and the command line), then a cloud platform plus a certification to structure the learning (a foundational credential like AWS Cloud Practitioner or Azure Fundamentals, followed by an associate-level exam such as AWS Solutions Architect Associate), then hands-on projects that go beyond exam material — deploying something real in a free-tier account, breaking it, and fixing it. Certifications validate knowledge and help a CV get noticed, but employers consistently weight hands-on evidence heavily too, so the projects step is not optional padding.
Our detailed guide on how to become a cloud engineer with no experience walks through this path step by step, including how to build a portfolio without a prior IT job to draw on. It is a realistic route for a career changer, not just for people already in tech.
The title varies more than you might expect
Because "cloud engineer" is used so broadly across the industry, two roles with the identical title can look quite different — one might be almost entirely Terraform and networking, another almost entirely security and compliance, another closer to application deployment. When evaluating a specific job, read the actual responsibilities listed rather than relying on the title alone, and expect some negotiation between what a posting calls a role and what the work will actually involve once you are in it.
What we won’t claim
We are not going to quote salary figures for cloud engineers here. Published salary numbers vary enormously by country, city, employer size, seniority and the specific mix of responsibilities behind the title, and a single figure printed in an article is rarely an honest representation of what any individual reader should expect. The reliable way to answer "what does this role pay" is to look at live job adverts and salary-transparency data for your own market and level, not a generic blog statistic.
Original practice questions, timed mock exams and revision notes. No card, nothing to pay.