Free Download • No Sign-up Required

AWS Resume

Cloud recruiters don't care about a list of services; they care about how you solved scale and cost problems. This AWS resume format focuses on showing your hands-on experience with high-availability distributed systems and IaC.

98% ATS Score LaTeX Quality 50K+ Downloads
Get Your Resume Template

or

Convert your existing resume
resume.pdf

Elena Davis

elena.davis@proton.me • +1 (345) 760-8093 • github.com/elenadavis • linkedin.com/in/elena-davis

Education

Georgia Tech May 2018
Bachelor of Science in Computer Science GPA: 3.85/4.0

Technical Skills

Languages: Python, Go, Java, TypeScript, Bash, SQL
Frameworks: FastAPI, React, Node.js, Boto3, Pulumi, Gin
Tools: Terraform, AWS Lambda, Kubernetes (EKS), DynamoDB, CloudFormation, Jenkins, Prometheus

Professional Experience

Senior Cloud Engineer June 2021 – Present
Databricks San Francisco, CA
  • Architected a multi-region EKS deployment strategy that improved system availability to 99.99%, supporting over 200 microservices across US and EU regions.
  • Reduced monthly EC2 spend by $140,000 by implementing a custom automated lifecycle manager for spot instances and right-sizing underutilized RDS clusters.
  • Designed a serverless data ingestion pipeline using SQS, Lambda, and S3 that processes 4TB of logs daily, replacing a legacy Kafka cluster and reducing maintenance overhead by 60%.
Software Engineer (Infrastructure) July 2018 – May 2021
Twilio San Francisco, CA
  • Automated 100% of infrastructure provisioning using Terraform, cutting the time to spin up new staging environments from 4 hours to 12 minutes.
  • Migrated a monolithic API to a microservices architecture on AWS Fargate, resulting in a 35% reduction in p99 latency for core messaging endpoints.

Projects

CloudCost-Sentinel Go, AWS SDK, Lambda, Slack API
  • Developed an open-source tool that monitors real-time AWS usage and alerts engineering teams via Slack when individual resource costs deviate by 20% from the 7-day rolling average.
✓ ATS-Optimized

Get a Reality Check on Your Current Resume

Upload your file to see if your cloud experience actually stands out or if you're just listing keywords that recruiters ignore.

Drop your resume here

or click to upload (PDF only, max 10MB)

We'll analyze your resume and show you how to improve it

Write Bullets That Prove You Know the Cloud

Shift from listing features to describing how you improved reliability and bottom-line costs using AWS services.

❌ Vague/Generic

Worked with various AWS services like EC2, S3, and RDS to host web applications.

✓ Impact-Focused

Optimized a high-traffic web application's storage strategy by migrating 50TB of legacy data to S3 Intelligent-Tiering, reducing storage costs by 30% without impacting retrieval latency.

Copied!

Why it works: It shows you don't just 'use' services, but you understand the cost-performance trade-offs of different storage classes.

❌ Task-Focused

Setup CI/CD pipelines to deploy code to AWS.

✓ Results-Driven

Built a blue-green deployment pipeline using AWS CodePipeline and Lambda-based health checks, eliminating deployment-related downtime for 1.2M monthly active users.

Copied!

Why it works: This highlights the methodology (blue-green) and the direct benefit to the user base, rather than just the tool used.

❌ No Metrics

Improved the security of our AWS environment.

✓ Quantified Achievement

Enforced least-privilege access by refactoring 450+ IAM roles and implementing SCPs via AWS Organizations, reducing the internal attack surface and passing a SOC2 Type II audit.

Copied!

Why it works: Security is hard to quantify, but mentioning specific audits and the number of roles refactored proves the scale of your work.

❌ Passive Voice

Responsibility for monitoring AWS infrastructure was held by me.

✓ Action-Oriented

Engineered a centralized observability platform using CloudWatch and Grafana, reducing Mean Time to Recovery (MTTR) for production incidents by 45 minutes.

Copied!

Why it works: Starting with an action verb like 'Engineered' and providing a specific metric (MTTR) shows ownership and technical leadership.

Advice from the Interview Loop

Practical answers to the most common questions I get about building a resume for cloud-heavy engineering roles.

Should I list every AWS service I've ever touched?

No. Listing 50 services looks like keyword stuffing and makes you look like a generalist. Focus on the core services you can actually explain in depth during an interview—usually VPC, IAM, EC2/Lambda, and a few database services.

How important are AWS certifications on a resume?

Certs are great for getting past initial HR screens, especially if you're early in your career. However, for senior roles, they are a secondary signal. Hiring managers care much more about your experience managing production traffic and large-scale migrations.

What's the best way to show 'Infrastructure as Code' experience?

Don't just list 'Terraform' in your skills. Write bullets about how you used it to manage state, handle multi-account environments, or modularize your infrastructure to help other teams move faster.

Do I need to include my GitHub if I only have private work repos?

If your professional work is private, use your resume to describe the architecture you built. A GitHub with a few well-documented, clean terraform modules or a small serverless app is better than an empty profile or a profile with 100 forked repositories.

What is the biggest mistake cloud engineers make on their resumes?

Treating AWS like a black box. You need to show you understand what's happening under the hood—like networking, disk I/O, or cold starts—rather than just clicking buttons in the AWS Console.

How do I stand out for a Senior Cloud Architect role?

Focus on the 'why' behind your technical choices. Explain why you chose DynamoDB over RDS for a specific project, or how you handled a complex migration without losing data. Decision-making is the hallmark of a senior engineer.

Ready to Build Your Resume?

Use our AI-powered builder to create a Jake's Resume that stands out. Upload your existing resume and get an ATS-optimized version in seconds.

Build Your Resume Now

Free to start • No credit card required

AWS Resume LaTeX Code

Copy and paste into Overleaf or your LaTeX editor 

%-------------------------
% AWS Resume
% LaTeX Resume Template - Jake's Resume Format
%-------------------------

\documentclass[letterpaper,11pt]{article}

\usepackage{latexsym}
\usepackage[empty]{fullpage}
\usepackage{titlesec}
\usepackage{marvosym}
\usepackage[usenames,dvipsnames]{color}
\usepackage{verbatim}
\usepackage{enumitem}
\usepackage[hidelinks]{hyperref}
\usepackage{fancyhdr}
\usepackage[english]{babel}
\usepackage{tabularx}

\pagestyle{fancy}
\fancyhf{}
\fancyfoot{}
\renewcommand{\headrulewidth}{0pt}
\renewcommand{\footrulewidth}{0pt}

% Adjust margins
\addtolength{\oddsidemargin}{-0.5in}
\addtolength{\evensidemargin}{-0.5in}
\addtolength{\textwidth}{1in}
\addtolength{\topmargin}{-.5in}
\addtolength{\textheight}{1.0in}

\urlstyle{same}

\raggedbottom
\raggedright
\setlength{\tabcolsep}{0in}

% Sections formatting
\titleformat{\section}{
  \vspace{-4pt}\scshape\raggedright\large
}{}{0em}{}[\color{black}\titlerule \vspace{-5pt}]

%-------------------------
% Custom commands
\newcommand{\resumeItem}[1]{
  \item\small{
    {#1 \vspace{-2pt}}
  }
}

\newcommand{\resumeSubheading}[4]{
  \vspace{-2pt}\item
    \begin{tabular*}{0.97\textwidth}[t]{l@{\extracolsep{\fill}}r}
      \textbf{#1} & #2 \\
      \textit{\small#3} & \textit{\small #4} \\
    \end{tabular*}\vspace{-7pt}
}

\newcommand{\resumeProjectHeading}[2]{
    \item
    \begin{tabular*}{0.97\textwidth}{l@{\extracolsep{\fill}}r}
      \small#1 & #2 \\
    \end{tabular*}\vspace{-7pt}
}

\newcommand{\resumeSubItem}[1]{\resumeItem{#1}\vspace{-4pt}}

\renewcommand\labelitemii{$\vcenter{\hbox{\tiny$\bullet$}}$}

\newcommand{\resumeSubHeadingListStart}{\begin{itemize}[leftmargin=0.15in, label={}]}
\newcommand{\resumeSubHeadingListEnd}{\end{itemize}}
\newcommand{\resumeItemListStart}{\begin{itemize}}
\newcommand{\resumeItemListEnd}{\end{itemize}\vspace{-5pt}}

%-------------------------------------------
%%%%%%  RESUME STARTS HERE  %%%%%%%%%%%%%%%%%%%%%%%%%%%%

\begin{document}

%----------HEADING----------
\begin{center}
    \textbf{\Huge \scshape Elena Davis} \\ \vspace{1pt}
    \small elena.davis@proton.me $|$ +1 (345) 760-8093 $|$ github.com/elenadavis $|$ linkedin.com/in/elena-davis
\end{center}

%-----------EDUCATION-----------
\section{Education}
  \resumeSubHeadingListStart
    \resumeSubheading
      {Georgia Tech}{Location}
      {Bachelor of Science in Computer Science}{May 2018}
  \resumeSubHeadingListEnd

%-----------SKILLS-----------
\section{Technical Skills}
 \begin{itemize}[leftmargin=0.15in, label={}]
    \small{\item{
     \textbf{Languages}{: Python, Go, Java, TypeScript, Bash, SQL} \\
     \textbf{Frameworks}{: FastAPI, React, Node.js, Boto3, Pulumi, Gin} \\
     \textbf{Tools}{: Terraform, AWS Lambda, Kubernetes (EKS), DynamoDB, CloudFormation, Jenkins, Prometheus}
    }}
 \end{itemize}

%-----------EXPERIENCE-----------
\section{Professional Experience}
  \resumeSubHeadingListStart
    \resumeSubheading
      {Senior Cloud Engineer}{June 2021 – Present}
      {Databricks}{San Francisco, CA}
      \resumeItemListStart
        \resumeItem{Architected a multi-region EKS deployment strategy that improved system availability to 99.99\%, supporting over 200 microservices across US and EU regions.}
        \resumeItem{Reduced monthly EC2 spend by \$140,000 by implementing a custom automated lifecycle manager for spot instances and right-sizing underutilized RDS clusters.}
        \resumeItem{Designed a serverless data ingestion pipeline using SQS, Lambda, and S3 that processes 4TB of logs daily, replacing a legacy Kafka cluster and reducing maintenance overhead by 60\%.}
      \resumeItemListEnd

    \resumeSubheading
      {Software Engineer (Infrastructure)}{July 2018 – May 2021}
      {Twilio}{San Francisco, CA}
      \resumeItemListStart
        \resumeItem{Automated 100\% of infrastructure provisioning using Terraform, cutting the time to spin up new staging environments from 4 hours to 12 minutes.}
        \resumeItem{Migrated a monolithic API to a microservices architecture on AWS Fargate, resulting in a 35\% reduction in p99 latency for core messaging endpoints.}
      \resumeItemListEnd
  \resumeSubHeadingListEnd

%-----------PROJECTS-----------
\section{Projects}
    \resumeSubHeadingListStart
      \resumeProjectHeading
          {\textbf{CloudCost-Sentinel} $|$ \emph{Go, AWS SDK, Lambda, Slack API}}{}
          \resumeItemListStart
            \resumeItem{Developed an open-source tool that monitors real-time AWS usage and alerts engineering teams via Slack when individual resource costs deviate by 20\% from the 7-day rolling average.}
          \resumeItemListEnd
    \resumeSubHeadingListEnd

%-------------------------------------------
\end{document}

Paste this code into Overleaf to compile

</> SWE Resume

Welcome back

Sign in to access the resume builder

Or continue with email