Cloud engineer with 5 years of experience building and operating AWS infrastructure for a growing SaaS company. Codified 100% of production infrastructure in Terraform and cut monthly cloud costs by 27% through right-sizing and scheduling. Brings reliable automation, solid networking fundamentals and practical on-call experience.
Experience
Cloud Engineer, Pathwise Learning (Raleigh, NC)
Feb 2023 – Present
Converted all production infrastructure across 9 AWS accounts to Terraform modules with automated plan reviews
Cut monthly cloud spend 27% by right-sizing RDS and scheduling non-production environments off-hours
Moved 35 services from EC2 to ECS Fargate, shortening deploys from 25 minutes to 6
Built VPC and Transit Gateway designs supporting a new EU region for GDPR data residency
Junior Cloud Engineer, Oak City Payments (Raleigh, NC)
Jun 2021 – Jan 2023
Automated EC2 patching with Systems Manager across 220 instances
Created CloudWatch alarms and dashboards for 15 critical services
Rotated 300 IAM access keys into role-based access, closing a top finding from the annual PCI DSS assessment
Education
B.S. Computer Science, Appalachian State University (Aug 2017 – May 2021)
A strong Cloud Engineer resume shows the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Put your most relevant recent role first and make every bullet show a result, not a duty.
Sections, in order
Summary
Experience
Projects
Skills
Education
Length: One page for most candidates; move to two only if every line is relevant.
Summary: Write two or three lines: your role, your strongest skills, and one result that proves them.
Skills to feature
Programming languages
System design
Cloud platforms (AWS, GCP, Azure)
CI/CD
Testing and code review
Databases and SQL
Observability
Security fundamentals
APIs and integrations
Technical documentation
Example bullet points
Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users
Introduced contract tests and staged rollouts, reducing production incidents by 45% in two quarters
Migrated 30 services to Kubernetes with Terraform, lowering cloud spend by $250k a year
Tips from recruiters
Group skills by category (for example "Languages: Go, TypeScript") so recruiters and ATS parsers find them quickly.
Link to a repository, demo or write-up for at least one project you can talk about in depth.
Name the stack inside each bullet; keyword matching happens at the bullet level, not only in the skills list.
Recommended templates
Classic (ATS-friendly): Jake's-style LaTeX classic: small caps and hairline rules
Tech (ATS-friendly): Developer style: mono headings and tags, sans body
Modern (ATS-friendly): Clean single column with accent headings and rules
Cloud Engineer resume FAQ
What should a Cloud Engineer resume include?
A Cloud Engineer resume should show the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Use these sections in this order: Summary, Experience, Projects, Skills and Education. Put your most relevant recent role first and make every bullet show a result, not a duty.
What is the best resume template for a Cloud Engineer?
Classic, Tech and Modern work well for Cloud Engineer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Cloud Engineer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a Cloud Engineer put on a resume?
Prioritize the skills named in the job posting. Common ones for Cloud Engineer roles are Programming languages, System design, Cloud platforms (AWS, GCP, Azure), CI/CD, Testing and code review and Databases and SQL.
How do I write strong Cloud Engineer resume bullet points?
Start with an action verb, say what you did, and end with a measurable result such as latency, uptime and deploy frequency. For example: "Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users."