Observability engineer with 9 years in infrastructure and SRE roles, focused on metrics, tracing and logging platforms for microservice fleets. Rolled out OpenTelemetry across 220 services and cut mean time to detect from 18 to 4 minutes. Brings cost-aware telemetry design and SLO-driven alerting.
Led OpenTelemetry adoption across 220 services, giving on-call engineers end-to-end traces for 95% of customer requests
Rebuilt alerting around 60 SLOs with burn-rate rules, reducing pages by 52% while cutting mean time to detect to 4 minutes
Moved high-cardinality metrics from a vendor to self-hosted Grafana Mimir, saving $410K annually
Created logging standards and a Loki sampling pipeline that trimmed log volume 35% without losing error events
Site Reliability Engineer, Kestrel Health Systems (Denver, CO)
Aug 2019 – Apr 2022
Deployed Prometheus and Thanos for 14 Kubernetes clusters with 13-month retention for HIPAA audit needs
Built Grafana dashboards per service tier, adopted by 18 teams for weekly reliability reviews
Systems Administrator, Tallgrass Networks (Boulder, CO)
Jun 2017 – Jul 2019
Replaced Nagios checks with Prometheus exporters for 300 Linux hosts
Education
B.S. Computer Science, University of Colorado Boulder (Aug 2013 – May 2017)
Skills
Telemetry: OpenTelemetry, Prometheus, Grafana Mimir, Loki, Tempo
Vendors: Datadog, Honeycomb, PagerDuty
Infrastructure: Kubernetes, Terraform, Helm, AWS
Practices: SLOs and error budgets, alert design, incident review, telemetry cost control
How to write a Observability Engineer resume
A strong Observability 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
Observability Engineer resume FAQ
What should a Observability Engineer resume include?
A Observability 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 Observability Engineer?
Classic, Tech and Modern work well for Observability Engineer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Observability Engineer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a Observability Engineer put on a resume?
Prioritize the skills named in the job posting. Common ones for Observability 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 Observability 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."