AWS cloud engineer is a term that means three completely different jobs depending on who's hiring. Understanding the distinction separates you from candidates who just slap AWS experience on their resume and hope.
Three jobs are hiding in the same keyword
Cloud architect: Strategic thinking about cloud transformation, cost optimization, and multi-account strategy. You're designing systems at a high level—not writing code, but making decisions about whether to use Lambda vs. EC2, RDS vs. DynamoDB, etc. These roles go to experienced engineers (6+ years) and usually require AWS Solutions Architect or similar certification. They're the highest-paid and often the most political.
Cloud platform engineer: Building internal platforms that other engineers use. You're creating deployment infrastructure, CI/CD pipelines, observability stacks, and infrastructure-as-code templates. You're deep in Terraform, CloudFormation, or CDK. This role is increasingly common as companies realize they need abstraction layers. You don't necessarily need to have architected massive systems—you need to be strong at tooling and automation.
Cloud migration specialist: Taking legacy applications and moving them to AWS. You understand capacity planning, data migration strategies, and the political complexity of large migrations. These roles are less common now (most migrations happened 2018–2023), but they're well-paid if available. They require patience and deep knowledge of both old infrastructure and new cloud paradigms.
Four employer types cover most of the market
Cloud-first startups and scale-ups: Companies born on AWS without legacy infrastructure. They need engineers who can build cloud-native systems from first principles. The role is usually a mix of architecture and platform building. Remote is standard. The pace is fast and the problems are interesting.
Enterprises migrating to cloud: Large organizations modernizing infrastructure. They're hiring armies of cloud engineers to move workloads. The work can be tedious but pays well and the job security is solid. Remote work varies—many are still hybrid. The hiring process is slow.
Managed services and consulting firms: Companies like Accenture, Deloitte, or AWS boutiques. You're helping clients architect and migrate systems. The variety is high but the client juggling is exhausting. Remote work depends on the firm. It's a great place to see a lot of systems quickly.
Tech companies building on AWS: Cloud-native companies that aren't migration-focused. They need cloud engineers who can design systems and build internal platforms. Remote is standard. You'll learn how large-scale systems actually work.
What the stack actually looks like
Infrastructure-as-code is mandatory—Terraform dominates, CloudFormation is enterprise standard, AWS CDK is growing. You'll work with compute (EC2, Lambda, Fargate), databases (RDS, DynamoDB, Aurora), networking (VPC, ELB, CloudFront), and storage (S3, EBS). Observability is critical: CloudWatch for baseline, but most companies layer on Datadog, New Relic, or Splunk. Automation happens through CI/CD platforms (GitHub Actions, GitLab, Jenkins) integrated with AWS services. Containerization is standard—Docker and Kubernetes are the baseline. Secret management through AWS Secrets Manager or HashiCorp Vault. Most teams use multiple AWS services for the same problem and need to make intentional choices.
Six things worth checking before you apply
Clarify what "cloud engineer" actually means: Ask directly whether they're hiring architects, platform engineers, or migration specialists. A job description that doesn't distinguish is usually a sign that the team hasn't thought clearly about the role.
Understand their AWS maturity: How long have they been on AWS? If it's less than 2 years, you'll be doing migration and learning the platform simultaneously. If it's 5+ years, you're probably optimizing existing systems. Newer = more learning; older = more optimization.
Ask about infrastructure-as-code discipline: Do they use Terraform? Is it version controlled? Do they have code review processes for infrastructure? Lacking this is a huge red flag—it means changes are chaotic and rollbacks are hard.
Check their deployment safety: Can they do blue-green deployments? Canary releases? Or does everything go live at once? Deployment safety correlates with system maturity and engineering culture.
Find out about cost management: Is anyone tracking AWS spending? Do they optimize for cost, or is budgeting a black box? Cost obsession usually correlates with good architecture decisions.
Understand the change management process: How quickly can you deploy infrastructure changes? If it takes 6 months to get approval for a new VPC, the process is broken. If you can spin up infrastructure in minutes, the team is probably healthy.
The bottleneck is different at every level
Junior cloud engineers often come from sysadmin or DevOps backgrounds, making the shift from on-premises to cloud. The learning curve is steep because there are a million AWS services and it's not obvious which to use. After a year, they usually hit the architecture wall—they can deploy things, but they don't understand how to design systems at scale.
Mid-level cloud engineers (3–5 years) usually plateau around architectural decision-making. They can execute, but they often don't have the authority to make major infrastructure choices. The frustration point is watching the team make suboptimal decisions and being unable to change course. This is where some engineers burn out and others move into architecture or platform roles.
Senior cloud engineers either move into architecture (becoming solutions architects or staff engineers), specialize in platform engineering, or move into management. Pure IC growth is limited because most companies don't have staff cloud engineer roles. This is why experienced cloud engineers often target companies with defined staff engineering tracks or migrate into consulting.
What the hiring process usually looks like
Cloud engineer interviews vary wildly depending on role. Recruiter screen, then a practical exercise—often designing an architecture for a specified workload, maybe with constraints (cost, latency, compliance). Technical interview focusing on your past work, design decisions, and how you think about tradeoffs. Systems design round where you handle a complex architecture question. Chat with the team about culture fit and interests. Some companies ask you to do a take-home lab where you build actual infrastructure in a sandbox environment, which is more realistic than whiteboarding. The process is usually 3–4 weeks.
Red flags and green flags
Red flags: Job description says "architect" but the actual work is ops. They ask about theoretical AWS services you'd never use. They can't explain why they chose AWS over other clouds. The team can't tell you what infrastructure challenges they actually have. No one on the team is passionate about cloud. They've been on AWS for 5+ years without doing a cost optimization review.
Green flags: Someone from the team does the technical interview and asks about systems you've actually built. They acknowledge that AWS is complex and have clear standards for what they use. They can articulate why they chose specific services. The team has shipped infrastructure that scales. They're honest about what's working and what's not.
Gateway to current listings
AWS positions are everywhere, but quality and scope vary hugely. These listings are verified and from companies actively hiring.
Want weekly updates on new cloud engineer positions? Subscribe below.
Frequently asked questions
Q: Do I need AWS certification to get hired as a cloud engineer?
Certifications help but aren't required, especially if you have production experience. Solutions Architect Professional is valuable at the architecture level. DevOps Engineer Professional is respected for platform roles. SysOps Administrator is less impressive but useful. Most companies care more about real systems you've built than certifications.
Q: What's the difference between DevOps engineer and AWS cloud engineer?
DevOps is broader—it includes CI/CD, automation, and cultural practices. AWS cloud engineer is more specialized to AWS infrastructure. DevOps roles at AWS-only companies often overlap with cloud engineer roles. DevOps skills are more portable across cloud providers; AWS skills are specific to one vendor.
Q: Should I learn Terraform or CloudFormation first?
Terraform. It's cloud-agnostic, more popular, and the learning applies across AWS, GCP, and Azure. CloudFormation is AWS-specific and more restrictive. Once you know Terraform, CloudFormation is easy. The reverse isn't always true.
Q: How much do AWS cloud engineers make?
Junior: $100–$140k. Mid: $160–$260k. Senior: $260–$380k+. AWS expertise pays well because it's in-demand and requires depth. Remote positions sometimes offer geographic adjustments, so verify before accepting.
RemNavi verifies AWS cloud engineer positions from legitimate employers. We can't assess whether a role matches your level or validate salary claims, so research companies independently. Verify actual infrastructure scale and responsibilities before committing.
Related resources
- Remote DevOps Engineer Jobs – Broader DevOps context
- Remote Go Developer Jobs – Systems language
- Remote Python Backend Developer Jobs – Infrastructure scripting
- Remote Fullstack Developer Jobs – Full stack perspective
- Remote TypeScript Developer Jobs – Frontend context