Cloud Engineer Jobs: AWS, GCP and Azure Roles and How They Differ From DevOps
The Short Answer
Cloud engineer jobs are roles where you build and maintain the cloud foundation that applications run on. You choose or configure cloud services, write infrastructure as code, connect networks, set permissions, and manage cost. The role is broader than provisioning servers and more architecture-heavy than many DevOps jobs.
| Level | Typical focus | Common skills and stack |
|---|---|---|
| Junior/associate | Provision resources, handle basic cloud tickets, write simple automation | AWS, Azure, or GCP console, Terraform basics, Python or Bash, VPC networking fundamentals |
| Mid-level | Own services, improve infrastructure as code, track cost, support incidents | Terraform modules, Kubernetes, CI/CD awareness, IAM, FinOps dashboards |
| Senior/staff | Cloud architecture, multi-account governance, migrations, platform strategy | Advanced networking, policy as code, cost optimization, stakeholder work |
Salary bands vary by region and company stage. Levels.fyi self-reported data shows many US cloud engineer offers clustered between roughly $120,000 and $180,000, with senior roles above that. Cloud engineer pay also overlaps with what remote full stack developers earn at the senior end, although the skill mix is different.
What the Role Actually Involves Day to Day
Most cloud engineer weeks are a mix of building, reviewing, and fixing the cloud platform. You will spend less time writing application code and more time deciding how services fit together.
A typical day can include writing Terraform, CloudFormation, or Bicep to create virtual private clouds, subnets, load balancers, databases, Kubernetes clusters, serverless functions, or object storage. You will review identity and access management roles, tighten security groups, and check whether anyone has granted more access than needed. You will sit in cost reviews and explain why a development environment went over budget. You may plan a migration from a data center or from another cloud provider.
Cloud engineering sits next to DevOps and SRE. A cloud engineer typically owns the platform: networks, accounts, services, cost, and baseline security. A DevOps engineer owns release flow: CI/CD, deployment scripts, test environments, and developer tooling. An SRE owns reliability targets: service level objectives, error budgets, and incident response. Small companies blur these roles. Larger companies hire separate people for each one. If you want to compare live titles, browse DevOps and cloud roles on the board.
What You Need to Break In (Skills, Portfolio, Experience)
The fastest path into cloud engineer jobs is one strong cloud platform, working knowledge of Terraform, and a project that proves you can run something in production safely.
Employers usually look for these skills:
- Deep knowledge of one cloud provider: AWS, Azure, or GCP.
- Infrastructure as code with Terraform, CloudFormation, or Bicep.
- Networking: DNS, VPC routing, load balancers, VPN, and subnets.
- Identity and security: IAM roles, service accounts, least-privilege access.
- Scripting in Python, Bash, PowerShell, or Go.
- Cost control: budget alerts, resource tagging, right-sizing, and basic FinOps.
- Container awareness: Docker and Kubernetes for many platform roles.
Certifications still matter, but only when they support real work. Global Knowledge's 2024 IT Skills and Salary Report lists AWS Certified Solutions Architect Professional as one of the highest-paying cloud certifications, with Microsoft Azure Administrator and Google Cloud Professional Cloud Architect also showing strong value. For most candidates, AWS Solutions Architect Associate is the best starting cert because AWS remains the most widely used cloud platform in Stack Overflow's 2024 Developer Survey. Go for Azure AZ-104 if you are targeting Microsoft-heavy or regulated companies. Choose GCP Associate Cloud Engineer if you want data, analytics, or AI infrastructure work.
Build a small project that shows judgment, not just a sandbox. A serverless application with IAM boundaries, a Terraform module that deploys to two environments, or a cost-control dashboard with an actual budget alarm will stand out. Cloud skills also feed AI infrastructure demand. If you are new to that side, the guide to entry-level AI jobs shows how candidates without AI titles get into adjacent work, and you can browse remote AI jobs to see cloud-adjacent AI infrastructure roles.
Common Mistakes People Make Here
Most people lose interviews for cloud engineer jobs by collecting broad knowledge instead of showing depth on a specific platform.
The first mistake is stacking certifications while never writing Terraform outside a tutorial. Hiring managers ask how you handled state files, module structure, and access boundaries. They do not ask how many badges you have.
The second mistake is picking a cloud provider based on brand rather than target employers. AWS is the broadest market, but Azure dominates many enterprise and government shops, and GCP shows up heavily in data and AI teams. Research the companies you want, then choose the first cert accordingly.
The third mistake is sending the same resume to cloud, DevOps, SRE, and backend roles. Cloud engineer applications should emphasize platform architecture, networking, IAM, and cost. DevOps applications should emphasize pipelines and delivery. A generic cloud resume gets lost.
The fourth mistake is ignoring cost and access control. Candidates who can describe how they reduced spend, prevented privilege escalation, or set up guardrails get interviews. One-click applications rarely help either. The LinkedIn Easy Apply guide explains why applying more slowly to fewer roles tends to work better.
Where to Actually Find These Roles
The most productive approach is a focused remote job board with fresh cloud listings, not a general search engine. Search by cloud provider, seniority, and region, then apply early with a tailored resume.
On JobsBoard you can browse remote jobs on JobsBoard across AWS, Azure, GCP, DevOps, security, and platform roles. Listings are re-checked twice a day and closed roles are taken down instead of collecting applications. Set up free weekly job alerts for cloud engineer roles in your time zone or stack. If a posting looks thin, ask specific questions about the environment and the hiring manager's expectations. The guide on ghost jobs shows how to tell whether a listing is actually hiring.
Frequently Asked Questions
Do cloud engineer jobs require a degree?
A degree is not always required. Many employers weigh hands-on infrastructure projects, Terraform skills, and one strong certification more than a computer science degree. Some large enterprises and regulated industries still filter on a bachelor's degree. If you do not have one, lead with a runnable project and measurable cost or uptime results.
Which cloud certification should I get first?
For most candidates, AWS Solutions Architect Associate is the safest first certification because AWS appears in the widest share of developer usage, according to Stack Overflow's 2024 Developer Survey. If you target Microsoft shops or government, take Azure AZ-104 first. Pair whichever cert you choose with a Terraform project.
Is cloud engineer the same as DevOps?
No. A cloud engineer focuses on cloud platform design, provisioning, networking, IAM, and cost. A DevOps engineer focuses on delivery pipelines, release automation, and developer experience. Many teams use one title for both, but senior roles usually split platform and delivery responsibilities.
Do remote cloud engineer jobs pay less?
Remote pay often depends on location band and employer policy more than the title. Levels.fyi self-reported data shows many US remote cloud engineer offers clustered between roughly $120,000 and $180,000. Some companies adjust salaries by region, so the same role can pay differently across states or countries.
Where to Look Next
Start with live cloud and platform roles on a focused board. Run the free resume match to see which current listing fits your Terraform, AWS, Azure, or GCP experience before you apply.
If you are hiring, the same filters apply in reverse. A cloud engineer post should specify the provider, the environment, the ownership model, and the cost or reliability problems the hire will solve. Use the principles in how to write a job post that attracts senior AI engineers. Employers looking for platform and cloud candidates can post a job and receive applications there.
