AWS cloud engineer with 6 years of experience running containerized and serverless workloads for media and fintech companies. Built the EKS platform that hosts 90 services with 99.97% availability. Brings deep AWS networking and IAM knowledge, Terraform discipline and steady cost and security hygiene.
Experience
AWS Cloud Engineer, Brightstream Video (Los Angeles, CA)
Mar 2022 – Present
Built and operate 4 EKS clusters hosting 90 services at 99.97% availability, using Karpenter for node autoscaling
Moved video transcoding to Spot-backed AWS Batch, saving $520K a year without missing delivery SLAs
Implemented IAM Roles for Service Accounts, removing 140 static credentials from workloads
Designed CloudFront and S3 origin architecture serving 3 PB of video monthly
Cloud Engineer, Silverlake Fintech (Irvine, CA)
Jul 2020 – Feb 2022
Built Lambda and Step Functions workflows for nightly reconciliation of 2M transactions
Configured AWS Config rules and Security Hub for PCI DSS evidence
Built an SQS-based retry queue for failed settlements, cutting manual reconciliation work by 12 hours a week
Education
B.S. Computer Engineering, California State University, Long Beach (Aug 2016 – May 2020)
Monitoring: CloudWatch, Datadog, AWS Cost Explorer
How to write a AWS Cloud Engineer resume
A strong AWS 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
AWS Cloud Engineer resume FAQ
What should a AWS Cloud Engineer resume include?
A AWS 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 AWS Cloud Engineer?
Classic, Tech and Modern work well for AWS Cloud Engineer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a AWS Cloud Engineer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a AWS Cloud Engineer put on a resume?
Prioritize the skills named in the job posting. Common ones for AWS 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 AWS 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."