CI/CD engineer with 8 years of experience designing build and deployment pipelines for polyglot monorepos and Kubernetes platforms. Cut median pipeline time from 38 to 11 minutes for 300 developers. Brings deep GitHub Actions and Argo CD expertise, supply-chain security practices and reusable pipeline templates.
Experience
CI/CD Engineer, Marlowe Fintech (Charlotte, NC)
Jan 2022 – Present
Redesigned monorepo pipelines with Bazel remote caching and test selection, cutting median CI time from 38 to 11 minutes for 300 developers
Rolled out Argo CD GitOps for 140 services, moving releases from weekly to 25 deploys per day
Added SLSA level 3 provenance, Sigstore signing and SBOM generation to every container build
Built self-hosted autoscaling runners on EKS, lowering CI compute spend by $180K per year
A strong CI/CD 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
CI/CD Engineer resume FAQ
What should a CI/CD Engineer resume include?
A CI/CD 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 CI/CD Engineer?
Classic, Tech and Modern work well for CI/CD Engineer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a CI/CD Engineer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a CI/CD Engineer put on a resume?
Prioritize the skills named in the job posting. Common ones for CI/CD 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 CI/CD 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."