keenresume
  1. Home
  2. Resume examples
  3. Software & IT
  4. DevOps engineer

DevOps engineer resume example

A senior DevOps engineer’s resume with seven years of experience, starting from systems administration. Platform hiring managers look for automation, reliability and cost results, so each bullet pairs a tool with what it changed.

DevOps engineer resume example, page 1 of 1Tomás HerreraSenior DevOps Engineertomas.herrera@example.com · (919) 555-0157 · Raleigh, NC · linkedin.com/in/tomasherrera-devops ·github.com/example-therreraSummaryDevOps engineer with seven years automating infrastructure and delivery on AWS. I build platforms that letdevelopers deploy safely many times a day, and I keep the pager quiet by fixing the causes of alerts rather thanthe alerts.ExperienceSenior DevOps EngineerAug 2022 – PresentCarolina Insurance Group · Raleigh, NC•Built the Kubernetes platform (EKS, Argo CD, Helm) that now runs 140 services; deploys went from twice amonth to 60 a day.•Codified all AWS infrastructure in Terraform across 12 accounts, removing manual changes and passing theSOC 2 Type II audit.•Cut monthly cloud spend by 31% ($52,000) with Spot instances, autoscaling and a cost dashboard for everyteam.•Introduced SLOs and alert rules based on user impact, reducing pages by 65% and mean time to recoveryfrom 2 hours to 25 minutes.DevOps EngineerMay 2019 – Jul 2022Triangle Health Partners · Durham, NC•Moved 60 applications from an on-premises data center to AWS in 14 months with no unplanned downtime.•Built GitHub Actions pipelines with automated security scans, catching 200 vulnerable dependencies beforerelease.•Wrote the incident runbooks and ran on-call training for 25 developers.Systems AdministratorJun 2017 – Apr 2019Oak City Software · Raleigh, NC•Managed 80 Linux servers and automated patching with Ansible, cutting patch time from 2 days to 2 hours.EducationB.S. in Information Technology2013 – 2017North Carolina State University · Raleigh, NCSkillsAWS · Kubernetes (EKS) · Terraform · Argo CD · Helm · GitHub Actions · Docker · Linux · Ansible · Prometheus ·Grafana · Python · Bash · GoCertificationsCertified Kubernetes Administrator (CKA)2024The Linux FoundationAWS Certified DevOps Engineer, Professional2023Amazon Web Services
DevOps engineerUse this example

What recruiters look for

  • Deployment speed and safety: deploy frequency, lead time, change failure rate. These are the DORA metrics many teams track.
  • Infrastructure as code: Terraform, Pulumi or CloudFormation across real environments, with how much is codified.
  • Reliability: SLOs, incident response, mean time to recovery, alert noise.
  • Cost: cloud savings with numbers. Every company wants this and few resumes show it.
  • Security and compliance: scanning in pipelines, SOC 2, ISO 27001, HIPAA work.

Writing the summary

Say your years, your main cloud and platform, and the outcome you are best at (faster deploys, fewer incidents, lower cost).

The summary in this example

DevOps engineer with seven years automating infrastructure and delivery on AWS. I build platforms that let developers deploy safely many times a day, and I keep the pager quiet by fixing the causes of alerts rather than the alerts.

Site reliability engineer (SRE)

Site reliability engineer with six years keeping high-traffic services up, from 99.9% to 99.99%. I define SLOs with product teams, lead incident response and write the code that removes toil.

Systems administrator moving into DevOps

Linux systems administrator with five years of experience who has automated most of my own job with Ansible and Python. Now building CI/CD pipelines and Terraform modules, and looking for a full-time DevOps role.

Bullet points that work

Strong lines for this role, beyond the ones in the example. Borrow the shape and put in your own numbers.

  • Reduced pipeline time from 45 to 12 minutes by parallelizing tests and caching build layers.
  • Built a self-service environment tool that spins up a full preview stack per pull request in 6 minutes.
  • Rolled out secrets management with Vault across 90 services, removing 300 hard-coded credentials.
  • Designed disaster recovery with a 15-minute recovery point and tested it quarterly.
  • Moved logging to OpenTelemetry and Grafana Loki, cutting observability costs by 48%.
  • Automated certificate renewal for 400 domains, ending a recurring cause of outages.
  • Cut change failure rate from 18% to 4% with canary releases and automatic rollback.
  • Patched a critical OpenSSL vulnerability across 2,000 hosts in 26 hours.
  • Ran 8 game days to rehearse failures, finding and fixing 14 weaknesses before they caused incidents.

Skills to list

Hard skills

  • A main cloud (AWS, Azure or GCP)
  • Kubernetes and containers
  • Terraform or another infrastructure-as-code tool
  • CI/CD (GitHub Actions, GitLab CI, Jenkins, Argo CD)
  • Linux administration
  • Scripting (Python, Bash, Go)
  • Monitoring and observability (Prometheus, Grafana, Datadog)
  • Networking (DNS, load balancing, VPCs)
  • Security tooling and secrets management

Soft skills

  • Calm incident command
  • Teaching developers
  • Writing runbooks
  • Saying no to risky shortcuts

Certifications and licenses worth listing

  • Certified Kubernetes Administrator (CKA): widely recognized and hands-on.
  • AWS Certified DevOps Engineer Professional or Solutions Architect: match the employer’s cloud.
  • Microsoft Azure DevOps Engineer Expert or Google Professional Cloud DevOps Engineer: for Azure or GCP shops.
  • HashiCorp Certified Terraform Associate: useful early in a DevOps career.

Length and format

One page up to about eight years of experience, two after. Put certifications where they are easy to see, because platform recruiters often filter on them.

Common mistakes

  • A list of tools with no outcomes. “Kubernetes, Terraform, Jenkins” says nothing about what improved.
  • Leaving out scale: number of services, accounts, hosts, deploys a day.
  • Ignoring cost. Savings are one of the strongest bullets a DevOps engineer can write.
  • Mixing up SRE and DevOps language. Mirror the job ad: SRE roles want SLOs and incidents, DevOps roles want pipelines and platforms.

Questions and answers

What is the difference between a DevOps and an SRE resume?

They overlap heavily. SRE resumes lean on reliability (SLOs, incidents, error budgets) and often more coding; DevOps resumes lean on delivery pipelines, platforms and automation. Adjust the order of your bullets to match.

Are certifications important for DevOps jobs?

More than in software engineering. CKA and a cloud certification are common filters, especially at consultancies and enterprises.

Should I include on-call experience?

Yes, with the result: what you changed so incidents happened less often or were fixed faster.

Related examples

All Software & IT examples

All resume examples