DevOps and Cloud Engineer CV: AWS/Azure Certifications, Projects and Examples That Pass Screening

DevOps and cloud CVs fail in two opposite ways: a wall of 60 tool names with no evidence, or a vague paragraph about «improving processes». The reader, usually an engineering manager, wants to see the platforms you ran, at what scale, and what changed because of your work: deployment frequency, uptime, recovery time, cost. Name the stack once, then prove it with numbers.

Structure of a DevOps or cloud CV

1. Header: name, city, phone, email, GitHub or GitLab, LinkedIn, and your top certification.
2. Profile: 3 lines on years, the clouds and platforms you own, scale (services, nodes, users, spend) and the role you want.
3. Skills: grouped by layer (cloud, containers, IaC, CI/CD, observability, languages), only tools you have used in production.
4. Experience: most recent first, with the platform, scale and outcomes.
5. Certifications: AWS, Azure, GCP, Kubernetes (CKA/CKAD), Terraform, security; with year.
6. Projects and open source, if relevant; education brief.

Sample profile

DevOps engineer with 6 years running AWS platforms for SaaS products (EKS, 120 microservices, 40k requests per second at peak), AWS Solutions Architect Professional and CKA certified. Moved deployments from fortnightly releases to 30+ a day with GitOps, cut cloud spend by 28 % and brought p99 incident recovery under 20 minutes. Seeking a senior platform engineering role.

Achievements with numbers

• Raised deployment frequency from fortnightly to 30+ a day by introducing trunk-based development, GitHub Actions pipelines and Argo CD; change failure rate fell from 18 % to 4 %.
• Reduced monthly AWS spend by 28 % ($45k) through right-sizing, Savings Plans, spot node groups and S3 lifecycle policies, with no SLO regressions.
• Improved availability from 99.5 % to 99.95 % across 120 services by implementing SLOs, error budgets and automated rollbacks.
• Cut mean time to recovery from 2 hours to 18 minutes with structured on-call runbooks, Prometheus alerting and PagerDuty escalation.
• Migrated 40 legacy VMs to Kubernetes with Terraform and Helm, zero customer-facing downtime, and decommissioned two data-centre racks.

Skills to list, grouped

• Cloud: AWS (EKS, EC2, RDS, Lambda, IAM, VPC), Azure (AKS, App Service, Entra ID), GCP (GKE, Cloud Run); multi-account and landing-zone design.
• Containers and orchestration: Docker, Kubernetes, Helm, Kustomize, service mesh (Istio, Linkerd).
• Infrastructure as code: Terraform, OpenTofu, Pulumi, CloudFormation, Ansible.
• CI/CD and GitOps: GitHub Actions, GitLab CI, Jenkins, Argo CD, Flux; artifact and secret management (Vault, SOPS).
• Observability and reliability: Prometheus, Grafana, Loki, OpenTelemetry, Datadog, ELK; SLOs, incident management, on-call.
• Security and compliance: IAM least privilege, image scanning (Trivy), policy as code (OPA), SOC 2 or ISO 27001 controls.
• Languages: Python, Go, Bash, YAML; SQL for operational queries.

Projects, on-call and incidents

Two or three projects with scale and outcome are worth more than a long list. For incident work, write the result and what you changed afterwards («Led the post-mortem for a 90-minute outage; shipped connection-pool limits and a circuit breaker that prevented recurrence»). State your on-call cadence plainly; managers want to know you have carried a pager.

ATS keywords

DevOps engineer, cloud engineer, site reliability engineer, platform engineer, AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, GitOps, infrastructure as code, observability, Prometheus, Grafana, Docker, Helm, automation, incident management, SLO, cost optimisation, security, Python, Bash. Match the role title in the advert and include both the acronym and the full phrase once (IaC, infrastructure as code).

Country notes

The stack is global; the framing differs. UK and Ireland: contract vs permanent and IR35 status matter; day rate expectations go in the cover note. Germany: certifications and a tidy skills matrix are valued, and German at B2 opens most non-startup roles. Gulf: government and banking employers ask for named certifications and often on-site presence; state visa status. US: mention security clearance if any, and whether you are open to remote; Japan and China: list domestic clouds (Alibaba Cloud, Tencent Cloud, Sakura) alongside AWS where you have used them.

Tools are the alphabet. A DevOps CV should contain sentences: platform, scale, number before, number after.

Check what the screen sees

CV Analyz compares your CV with the job ad, flags tool lists without evidence and missing certifications, and rewrites your roles around scale and outcomes, using only what you have actually run.