Kubernetes engineer with nearly 8 years in infrastructure roles, 7 of them running production Kubernetes. Operates 28 clusters with 6,000 nodes and completed a multi-version upgrade program with zero customer-facing incidents. Brings cluster lifecycle automation, networking with Cilium and multi-tenant security hardening.
Experience
Kubernetes Engineer, Arcfield Data Cloud (Remote)
Feb 2022 – Present
Operate 28 clusters with 6,000 nodes, automating lifecycle with Cluster API and keeping every cluster within one minor version
Migrated cluster networking from Calico to Cilium eBPF, cutting service latency 18% and adding L7 network policies
Built a custom operator for tenant onboarding that replaced 40 manual steps
Hardened clusters to CIS benchmarks with Kyverno policies and Pod Security Standards
Site Reliability Engineer, Bluefin Streaming (Seattle, WA)
Oct 2019 – Jan 2022
Migrated 120 services from Mesos to Kubernetes over 14 months without a major outage
Tuned HPA and cluster autoscaler settings, reducing compute costs 25%
Linux Administrator, Cascade Freight Systems (Portland, OR)
Jan 2019 – Sep 2019
Maintained 300 CentOS servers and Docker hosts
Education
B.S. Computer Science, Oregon State University (Sep 2015 – Jun 2019)
Security: Kyverno, Pod Security Standards, RBAC, Falco
Languages: Go, Python, Bash
How to write a Kubernetes Engineer resume
A strong Kubernetes 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
Kubernetes Engineer resume FAQ
What should a Kubernetes Engineer resume include?
A Kubernetes 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 Kubernetes Engineer?
Classic, Tech and Modern work well for Kubernetes Engineer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Kubernetes Engineer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a Kubernetes Engineer put on a resume?
Prioritize the skills named in the job posting. Common ones for Kubernetes 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 Kubernetes 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."