Technology · Mid-career

Cloud Engineer Resume Example

This example suits a cloud or infrastructure engineer with three to eight years of experience. It shows how to present migrations, infrastructure as code, networking, security and cost work with enough scale for a technical reader to judge it, and where certifications belong on the page.

The example resume

Laid out in the Recto template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.

Nadia Rahman

Cloud Engineer | AWS, Terraform, Kubernetes

Professional summary

Cloud engineer with six years in infrastructure, the last four building and running AWS platforms for a payments company. Works mainly in Terraform, EKS and GitHub Actions, with a focus on network design, least-privilege access and predictable monthly spend. AWS Certified Solutions Architect (Professional).

Work experience

Cloud Engineer

Kestrel Lane Payments, Toronto

Feb 2022 – Present

  • Migrated 38 services from two colocation data centres to AWS (EKS, RDS PostgreSQL, S3) over 14 months, with no unplanned customer downtime during cutovers
  • Wrote reusable Terraform modules for VPCs, EKS node groups and IAM roles, cutting the time to provision a new environment from three days to under two hours
  • Designed a hub-and-spoke network across four accounts with Transit Gateway and PrivateLink, removing every public database endpoint ahead of a PCI DSS audit
  • Reduced monthly AWS spend by 27% (about CA$31,000) through rightsizing, Savings Plans, Graviton node groups and S3 lifecycle rules
  • Built CloudWatch and Prometheus alerting with on-call runbooks, bringing mean time to recovery for platform incidents down from 54 to 19 minutes

Infrastructure Engineer

Brackenridge Retail Group, Mississauga

Aug 2020 – Jan 2022

  • Moved nightly backups for 120 Linux and Windows servers to S3 and Glacier, shortening a full restore test from one day to 90 minutes
  • Automated server patching with Ansible and AWS Systems Manager, raising on-time patch compliance from 71% to 98%
  • Containerised three internal Java applications with Docker and deployed them to ECS Fargate behind an Application Load Balancer
  • Replaced long-lived IAM user keys with single sign-on and role-based access for 45 engineers

Education

BSc Computer Science

Tarn Valley University, Ontario

2016 – 2020

Contact

  • nadia.rahman@example.com
  • +1 / +44 / +91
  • Toronto, Canada
  • linkedin.example.com/in/nadia-rahman
  • github.example.com/nadia-rahman

Skills

Cloud: AWS (EC2, EKS, ECS, RDS, S3, Lambda, IAM, VPC, Transit Gateway), working knowledge of Azure

Infrastructure as code: Terraform, Ansible, Helm

CI/CD and containers: GitHub Actions, Argo CD, Docker, Kubernetes

Observability and cost: CloudWatch, Prometheus, Grafana, Cost Explorer

Scripting: Python, Bash

Certifications

AWS Certified Solutions Architect: Professional

Amazon Web Services

2024

Certified Kubernetes Administrator (CKA)

The Linux Foundation

2023

HashiCorp Certified: Terraform Associate

HashiCorp

2022

Open this example in the resume builder Start empty with this template

Why this resume works

  • The headline and summary name AWS, Terraform and EKS in the first two lines, so a reader scanning for the platform and tooling in the advert finds them before reaching the experience section.
  • The migration bullet gives scope a hiring engineer can picture: 38 services, two data centres, 14 months and the target services. It then states the outcome that matters most in a migration, no unplanned downtime.
  • Cost is treated as an engineering result. The 27% saving is paired with the four methods used (rightsizing, Savings Plans, Graviton and lifecycle rules), which shows how the number was reached.
  • Security appears as concrete work instead of a claim: private database endpoints before a PCI DSS audit, reusable IAM role modules, and single sign-on replacing long-lived access keys.
  • Each certification matches work described in the experience section, so the three certificates read as confirmation of hands-on skill and not as a substitute for it.

What employers look for in this role

  • Design, build and maintain cloud infrastructure (networks, compute, storage and databases) on AWS, Azure or Google Cloud
  • Write and review infrastructure as code, usually Terraform, CloudFormation or Bicep, and manage modules and state
  • Plan and run migrations of applications and data from on-premises systems or between cloud accounts
  • Manage identity and access, network segmentation, encryption and secrets in line with security standards
  • Monitor availability, performance and spend, and respond to alerts as part of an on-call rota
  • Build and maintain CI/CD pipelines and container platforms with development teams
  • Document architecture and runbooks, and test backups, failover and disaster recovery

Skills to consider

List only the skills you can back up with an example. These are the ones that come up most for this kind of role.

Cloud platforms and services
AWS EC2, EKS, ECS and Lambda, Azure virtual networks and AKS, Google Cloud GKE and Cloud Run, Managed databases (RDS, Aurora, Cloud SQL), Object storage and lifecycle policies, Load balancing and DNS
Infrastructure as code and automation
Terraform modules and remote state, CloudFormation or Bicep, Ansible, Helm and Kustomize, GitHub Actions or GitLab CI, Python and Bash scripting
Networking and security
VPC design and subnetting, Transit Gateway, peering and VPN, IAM roles and least privilege, Secrets management, Encryption with KMS, Security groups and network policies, PCI DSS, SOC 2 or ISO 27001 controls
Operations
Monitoring and alerting, Incident response and on-call, Cost management (FinOps), Backup and disaster recovery, Capacity planning

More bullet points to adapt

Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.

  • Cut NAT gateway and data transfer charges by 40% by adding VPC endpoints for S3 and DynamoDB and routing egress through a shared network account
  • Ran a quarterly disaster recovery test that restored the production database in a second region in 47 minutes against a two-hour recovery time objective
  • Introduced policy-as-code checks (OPA and tfsec) in the Terraform pipeline, blocking unencrypted storage and open security groups before merge
  • Migrated 14 Jenkins jobs to GitHub Actions with OIDC federation, removing all stored cloud credentials from the CI system
  • Upgraded six EKS clusters through three Kubernetes minor versions using blue-green node groups, with no failed deployments during the change windows
  • Set up tagging standards and per-team cost dashboards, giving 11 product teams a monthly view of their own spend for the first time

Words that recur in adverts

These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.

  • Infrastructure as code
  • Terraform
  • Kubernetes
  • CI/CD
  • IAM
  • VPC networking
  • Landing zone
  • Cloud migration
  • High availability
  • Disaster recovery
  • Observability
  • Cost optimisation
  • Serverless
  • On-call

Which sections to include

Put a short summary first that names your main cloud provider and your infrastructure as code tool, because those two facts decide whether many technical readers continue. Experience comes next and carries most of the weight: lead each role with the largest piece of infrastructure you built or migrated. Follow it with a grouped skills section, since adverts for this role list many services and a reader will look for exact names; the guide to the skills section covers grouping. Certifications deserve their own section, placed above education once you have a few years of experience.

Mistakes to avoid

  • Listing every cloud service you have ever opened in the console. Keep the skills section to services you could discuss in an interview, and show the important ones in use in your bullets.
  • Describing a migration without scale. "Migrated applications to AWS" says little; give the number of services or servers, the source environment, the duration and what happened to availability.
  • Leaving out cost and security. Employers hire cloud engineers partly to control spend and reduce risk, so include at least one bullet on each, with the method you used.
  • Putting certifications at the top with nothing behind them. A certificate with no matching experience bullet invites doubt, so tie each one to work you describe.
  • Writing tool names with no outcome, such as "Used Terraform and Kubernetes". Say what you provisioned, for which teams, and what became faster, cheaper or safer.

Questions and answers

Should a cloud engineer resume list certifications before experience?

Usually not, once you have two or more years of hands-on work. Experience shows what you have built and certifications confirm it. If you are moving into cloud from another area of IT and a certificate is your strongest evidence, place that section directly under the summary instead.

How do I show cloud experience if my employer only uses one provider?

Go deep on that provider and name the services, then describe the underlying skills in general terms: network design, identity, infrastructure as code and containers. Most concepts transfer between providers. Only list a second provider if you have really used it, and label the level honestly, as "working knowledge of Azure" does here.

What is the difference between a cloud engineer resume and a DevOps engineer resume?

The roles overlap and titles vary between employers. A cloud engineer resume usually gives more space to infrastructure design: networks, accounts, identity, migrations and cost. A DevOps resume leans towards delivery pipelines, release frequency and developer tooling. The DevOps engineer example shows that second emphasis.

How do I quantify infrastructure work?

Use the measures your team already tracks: provisioning time, monthly spend, availability, recovery time, patch compliance and the number of services, clusters or accounts. Before-and-after pairs are the clearest. If you lack exact figures, a careful estimate marked "about" is acceptable, and the guide on quantifying achievements explains how to arrive at one.