Cloud engineer CVs fail at two filters before a human reads a single bullet point. The first is certification: recruiters screening for AWS, Azure, or GCP roles check for a recognised provider certification in the first scan — AWS Solutions Architect, Azure Administrator, or Google Associate Cloud Engineer. If it isn't visible immediately, the CV often doesn't advance. The second filter is infrastructure as code: a cloud engineer who provisions infrastructure manually rather than through Terraform, Pulumi, or CloudFormation is a reliability and security risk, and senior engineers reviewing CVs know it. Most cloud engineer CVs fail one or both of these filters while listing impressive-sounding services they have used. This guide covers how to structure a cloud engineer CV that passes both, what ATS keyword clusters actually matter, and the three mistakes that cost otherwise qualified candidates shortlisting.

What Cloud Engineer Job Descriptions Require in 2026

Cloud engineering JDs have converged around a consistent core despite the role varying significantly between companies. Whether the title is Cloud Engineer, Cloud Infrastructure Engineer, or Platform Engineer, the requirements that appear across the majority of 2026 JDs are:

  • A primary cloud provider at depth — AWS is the most common (appearing in approximately 60% of cloud engineer JDs in the UK and US), followed by Azure (dominant in enterprise and public sector), then GCP (strong at data-heavy companies and Google-stack organisations). JDs name the provider explicitly. Your CV should lead with your primary provider, not list all three equally.
  • Infrastructure as Code — Terraform is the industry standard in 2026; CloudFormation for AWS-only roles; Pulumi at companies adopting more developer-centric approaches. IaC is listed as a requirement, not a nice-to-have, in the majority of cloud engineer JDs. Candidates without it are screened out early.
  • Container orchestration — Kubernetes is expected at mid-level and above. The managed variants (EKS on AWS, AKS on Azure, GKE on GCP) are the production standard. JDs increasingly distinguish between running workloads on an existing cluster versus administering the cluster itself — senior roles require the latter.
  • Networking and security — VPC design, subnetting, security group management, IAM policy authoring, and cloud security fundamentals. Zero Trust architecture and secrets management (HashiCorp Vault, AWS Secrets Manager) appear in security-sensitive roles.
  • Scripting — Python and Bash for automation, tooling, and pipeline scripting. Go is emerging in platform engineering roles.

Cloud engineer salaries in 2026: £55K–£95K UK; $120K–$180K US, with senior cloud engineers at hyperscaler-adjacent companies exceeding $200K total compensation.

ATS Keywords for a Cloud Engineer CV

Cloud engineer ATS searches are provider-specific and certification-sensitive. Recruiters filter by provider name (AWS, Azure, GCP) and by IaC tool (Terraform) before reading anything else.

Essential ATS terms for a cloud engineer CV:

  • Title variants: Cloud Engineer, Cloud Infrastructure Engineer, Platform Engineer, DevOps Engineer, Site Reliability Engineer, Cloud Architect
  • Providers: AWS, Amazon Web Services, Microsoft Azure, Google Cloud Platform, GCP, multi-cloud
  • IaC: Terraform, Pulumi, CloudFormation, Ansible, Infrastructure as Code, IaC, GitOps
  • Container and orchestration: Kubernetes, EKS, AKS, GKE, Docker, Helm, ArgoCD, container orchestration
  • CI/CD: GitHub Actions, Jenkins, GitLab CI, CircleCI, ArgoCD, pipeline automation
  • Languages: Python, Bash, Go
  • Networking and security: VPC, IAM, security groups, Zero Trust, cloud security, Vault, secrets management
  • Cost and operations: cloud cost optimisation, FinOps, Reserved Instances, cloud migration, disaster recovery, RTO, RPO
  • Certifications: AWS Solutions Architect, Azure Administrator, Google Associate Cloud Engineer, CKA (Certified Kubernetes Administrator)
  • Long-tail phrases: cloud engineer resume examples, how to write a cloud engineer resume, cloud engineer cv template, AWS engineer resume, Terraform engineer resume

Placement: Your primary cloud provider and Terraform belong in your CV headline. Certifications belong in a dedicated section near the top — not buried in a footer. AWS Solutions Architect or Azure Administrator appearing above the fold on the first screen is the fastest filter signal a recruiter has.

Cloud Engineer CV Structure and Bullets That Show Infrastructure Scale

Section order:

  1. Headline — "Cloud Engineer | AWS · Terraform · Kubernetes · Python" or "Cloud Infrastructure Engineer | Azure · Terraform · AKS · GitHub Actions"
  2. Certifications — dedicated section, near the top. List: certification name, issuing body, year, expiry if relevant. Do not bury this.
  3. Skills — layered by domain: Cloud Providers / IaC / Container & Orchestration / CI/CD / Languages / Monitoring
  4. Experience — 4–6 bullets per role; infrastructure scale and cost metrics are the primary evidence
  5. Education — CS, networking, or engineering degree; bottom of page

Two pages for 4+ years; one to two pages for under 4. Include a GitHub link if you have public Terraform modules or IaC repositories.

Cloud engineer bullets need three elements: the infrastructure built (provider + tool + scale), the operational outcome (uptime, deployment frequency, recovery time), and the business impact (cost, speed, reliability). Three examples:

  • Designed and deployed a multi-region AWS infrastructure using Terraform across 14 environments and 3 AWS accounts, serving 400K active users with 99.98% monthly uptime and automated Route 53 failover achieving RTO under 4 minutes
  • Reduced monthly AWS spend from £82K to £49K by implementing Reserved Instance coverage for baseline workloads, rightsizing 60+ EC2 instances using CloudWatch utilisation data, and introducing S3 lifecycle policies for 12TB of infrequently accessed data
  • Built a GitOps CI/CD pipeline with GitHub Actions and ArgoCD deploying to EKS, cutting average deployment time from 45 minutes to 6 minutes and eliminating manual release steps responsible for 3 production incidents in the prior 6 months

Cloud engineer technical interviews test three things: architecture design ("design a highly available, multi-region deployment for this application"), IaC proficiency ("walk me through a Terraform module you've written and the decisions behind it"), and cost/security reasoning ("this architecture works — where are the risks and what would you change?"). A CV with infrastructure scale numbers and cost metrics signals that you can engage with all three.

Three Cloud Engineer CV Mistakes That Get You Filtered

Listing services without infrastructure scale. "Used EC2, S3, RDS, Lambda" appears on nearly every cloud engineer application — it describes a user, not an engineer. The recruiter's question is: how much? At what scale? Did you architect it or consume an existing setup? "Managed a Kubernetes cluster serving 40 microservices across 3 availability zones with auto-scaling node groups from 6 to 28 nodes during peak load" is a statement only someone who actually ran production infrastructure can make. Without scale, any claim about cloud experience is indistinguishable from tutorial-level exposure.

IaC absent from a CV applying to infrastructure roles. Click-ops — provisioning infrastructure through the cloud console rather than code — is not acceptable at companies running any serious cloud estate. Infrastructure provisioned manually cannot be version controlled, reviewed, or reliably reproduced. A cloud engineer CV without Terraform, CloudFormation, or Pulumi signals that the candidate either doesn't know IaC or worked somewhere that hadn't adopted it — neither is a positive signal for a role where IaC is a day-one expectation. If you have used Terraform at all, even on a side project or a migration pilot, include it with specifics.

Certifications buried at the bottom. The AWS Solutions Architect, Azure Administrator, and CKA are not decorative additions — they are the single fastest signal a recruiter has when screening cloud engineering applications. These certifications validate a baseline of knowledge the interviewer doesn't have to test for. Putting them in a one-line "Other" section at the foot of page two means the recruiter may never see them. A dedicated Certifications section near the top of page one — visible in the first few seconds — changes the shortlisting rate meaningfully.

If you are applying to cloud engineering or platform engineering roles and want your CV rebuilt around the specific AWS, Terraform, and Kubernetes requirements in a target job description, Resumegpt generates your cloud engineer CV from your work history in under 60 seconds — certifications surfaced, IaC signals prioritised, ATS-optimised, and exported as a PDF ready to submit.