Jordan Vance

Senior DevOps / Site Reliability Engineer

jordan.vance@devopsmail.com+1 (555) 839-2041https://jordanvance.devSeattle, WA

Infrastructure Automation Specialist with 7+ years of experience designing and managing cloud infrastructure. Expert in AWS, Kubernetes orchestration, Terraform IaC, and robust CI/CD pipelines. Proven record of reducing cloud spend by 30% and improving deployment frequency by 200%.

Experience

Senior DevOps Engineer · CloudScale Systems2023-01-01 — Present

Architected multi-region Kubernetes clusters in AWS (EKS) serving 5M+ daily active users, achieving 99.99% system uptime.
Wrote modular Terraform code to automate provisioning of VPCs, RDS instances, and IAM roles, reducing setup times from days to minutes.
Designed GitLab CI pipelines to automate security scans (SAST/DAST) and blue-green deployments, cutting release cycles by 40%.
Implemented Prometheus and Grafana alerts that reduced Mean Time to Resolution (MTTR) for production incidents by 50%.

DevOps / Release Engineer · AppForge Studio2019-06-01 — 2022-12-31

Containerized legacy monolith applications using Docker, improving local developer environment setup times by 80%.
Managed Jenkins automation server, maintaining 50+ pipeline configurations and migrating them to declarative Jenkinsfiles.
Optimized AWS resource allocation, including reserved instance scheduling and lifecycle rules, saving $120,000 annually.

Education

B.S. in Computer Science

University of Washington

2015-09-01 — 2019-05-15

Projects

Automated Cloud Cost Optimizer · github.com/jordanvance/cost-optimizer2022-01-01 — 2022-08-01

Open-source Go CLI tool that scans AWS accounts for underutilized EC2 and RDS instances and sends automatic shutdown alerts.

Received 400+ stars on GitHub and was featured in DevOps Weekly newsletter.

Skills

Cloud & Orchestration

AWS (EKS, EC2, RDS, S3, IAM), Kubernetes, Docker, ECS

IaC & Automation

Terraform, Ansible, GitLab CI, Jenkins, Helm

Monitoring & Scripting

Prometheus, Grafana, Python, Bash, Go, Git

Sample Data Pre-loaded

DevOps Engineer Resume Example

Review this premium layout for a DevOps Engineer role. This design uses standard single-column rules and formatting parameters to guarantee clean parser scans.

Edit This Resume (Free)← View More Industry Samples

Writing Guidelines for DevOps Engineers

•Prioritize technical competencies: Order skill sets relative to matching keyword phrases in job descriptions.
•Focus on metrics: Quantify your results (e.g. page speeds, savings, sales figures) in your bullet highlights.
•Reverse Chronological: List experiences starting from the most recent to align with ATS filters.

Formatting Advice & FAQ

How do you format a DevOps resume so it passes Workday or Greenhouse parser systems?

To pass Workday or Greenhouse parsers, avoid placing technical skills in graphic text boxes, sidebar bubbles, or tables. Instead, list your tools (e.g., Kubernetes, Terraform, AWS) in a standard, single-column text-based list. This ensures the parsing engine maps your tools to your skills profile without scrambling or omitting keywords.

Where is the best place to list AWS or Kubernetes certifications on a DevOps resume?

Always place AWS or Kubernetes certifications in a dedicated section titled 'Certifications' or 'Licenses & Certifications'. List the full name of the certification (e.g., 'AWS Certified Solutions Architect – Associate') along with the date obtained. This helps semantic search filters flag your resume when recruiters filter for certified cloud professionals.

Should a DevOps engineer use a single-column or two-column resume template?

A single-column layout is strongly recommended for DevOps resumes. Major corporate applicant tracking portals process PDF resumes by reading text left-to-right, top-to-bottom. Two-column formats can cause the parser to merge your technical skill lists with your job history details, corrupting your application.