Site Reliability Engineer Resume Examples by Level (2026)

title: "Site Reliability Engineer Resume Examples That Get Interviews in 2026" description: "3 proven SRE resume examples for entry-level, mid-career, and senior engineers with quantified achievements, real tools, and ATS-optimized keywords." slug: "site-reliability-engineer-resume-examples" category: "resume-examples" job_title: "Site Reliability Engineer" soc_code: "15-1244" industry: "Technology" date_published: "2026-02-21" date_modified: "2026-02-21" author: "ResumeGeni"

Site Reliability Engineer Resume Examples That Get Interviews in 2026

The Bureau of Labor Statistics projects roughly 14,300 annual openings for network and computer systems administrators (SOC 15-1244) through 2034, the occupational category that encompasses Site Reliability Engineers. Yet the SRE role itself commands compensation far above the category median of $96,800. Glassdoor reports a median total compensation of $200,000 for SREs in 2025, with senior engineers at companies like Google, Netflix, and Uber regularly exceeding $350,000 in total compensation. The gap between the BLS baseline and real SRE pay reflects a fundamental truth: companies will pay a premium for engineers who can quantify their impact on availability, latency, and incident response, and your resume is where that quantification starts. Below are three complete SRE resume examples, from entry-level through senior, built on real tools, real certifications, and the metrics hiring managers actually screen for.

Key Takeaways

• **Lead every bullet with a number.** SRE is a metrics-driven discipline. Hiring managers at Google, Datadog, and Cloudflare scan for availability percentages, latency reductions, and incident MTTR before they read anything else.
• **Name your observability stack explicitly.** "Monitoring experience" means nothing. "Built Prometheus + Grafana dashboards tracking 4,200 SLIs across 38 microservices" tells a hiring manager exactly what you can do on day one.
• **Separate infrastructure-as-code from general DevOps.** Terraform modules, Pulumi stacks, and Crossplane compositions are distinct skills from CI/CD pipeline configuration. List them in their own section.
• **Quantify incident management outcomes, not just participation.** "On-call rotation" is a job duty. "Reduced P1 MTTR from 47 minutes to 12 minutes by implementing automated runbooks in PagerDuty" is a hiring signal.
• **Certifications carry real weight for SREs.** The Certified Kubernetes Administrator (CKA) from CNCF, Google Cloud Professional Cloud DevOps Engineer, and AWS Certified DevOps Engineer Professional are the three credentials hiring managers mention most frequently in SRE job postings.

What Hiring Managers Look For

Availability and Reliability Metrics

Every SRE job description includes a variation of "maintain high availability." The resumes that get callbacks translate that into specifics. Hiring managers want to see that you improved service availability from 99.95% to 99.99%, which means you reduced annual downtime from 4.4 hours to 52 minutes. They want to know whether you define SLOs using the error budget model Google popularized in their SRE books, or whether you treat availability as an abstract goal. According to Google's SRE Workbook, an SLO of 99.9% on a service receiving 3 million requests over four weeks translates to an error budget of 3,000 permissible failures. If your resume demonstrates that you have operationalized error budgets to balance feature velocity against reliability, you are speaking the language hiring managers understand.

Observability and Incident Response

The 2025 Observability Survey found that 70% of companies now use both Prometheus and OpenTelemetry for their monitoring needs. Hiring managers expect SRE candidates to demonstrate fluency across the observability stack: metrics collection with Prometheus or Datadog, visualization with Grafana, log aggregation with the Elastic Stack or Loki, distributed tracing with Jaeger or Tempo, and alerting routed through PagerDuty or Opsgenie. The strongest resumes describe the full incident lifecycle. Prometheus detects an anomaly, Grafana dashboards surface the blast radius, PagerDuty pages the on-call engineer, and a post-incident review produces an action item that prevents recurrence. Hiring managers at companies like Uber and Cloudflare specifically look for candidates who can point to reduced Mean Time to Recovery (MTTR) and fewer repeat incidents.

Infrastructure Automation and Toil Reduction

Toil reduction is the defining mission of SRE. Google's SRE book establishes that SRE teams should spend no more than 50% of their time on operational toil, with the remaining time devoted to engineering work that reduces future toil. Your resume needs to demonstrate this philosophy in action. Listing Terraform, Ansible, or Pulumi as skills is baseline. What separates strong candidates is quantifying the toil they eliminated: "Automated 340 manual deployment steps into a 12-stage Terraform pipeline, reducing provisioning time from 6 hours to 14 minutes" or "Wrote Python-based auto-remediation scripts that resolved 73% of disk-pressure alerts without human intervention." Infrastructure-as-code, GitOps workflows with ArgoCD or Flux, and self-healing systems are the concrete proof points that move resumes to the top of the stack.

Programming and Systems Design

SRE is a software engineering discipline, not an operations role with a new title. Companies like Google, LinkedIn, and Dropbox require SRE candidates to pass coding interviews on par with software engineering roles. Your resume should demonstrate programming proficiency in Python, Go, or Java, with specific projects that show systems-level thinking. Building a custom Kubernetes operator in Go that manages 200 CRDs, writing a chaos engineering framework that runs 45 automated failure injection tests weekly, or developing an internal CLI tool adopted by 150 engineers are the kinds of entries that signal engineering depth rather than operational breadth.

Entry-Level Site Reliability Engineer Resume Example (0-2 Years)

**Jordan Nakamura** San Francisco, CA | [email protected] | github.com/jnakamura LinkedIn: linkedin.com/in/jordannakamura

**Summary** Site Reliability Engineer with hands-on experience operating Kubernetes clusters and Prometheus monitoring stacks at scale during internships at Cloudflare and Datadog. Built automated incident response tooling that reduced alert noise by 38%. Certified Kubernetes Administrator (CKA) with strong Python and Go programming skills.

**Certifications** - Certified Kubernetes Administrator (CKA) | Cloud Native Computing Foundation (CNCF) | 2025 - HashiCorp Certified: Terraform Associate (004) | HashiCorp | 2025 - AWS Certified Cloud Practitioner | Amazon Web Services | 2024

**Technical Skills** - **Languages:** Python, Go, Bash, SQL - **Containers & Orchestration:** Kubernetes, Docker, Helm, Kustomize - **Observability:** Prometheus, Grafana, Datadog, PagerDuty, ELK Stack - **Infrastructure as Code:** Terraform, Ansible, CloudFormation - **Cloud Platforms:** AWS (EC2, EKS, S3, Lambda), GCP (GKE, Cloud Run) - **CI/CD:** GitHub Actions, Jenkins, ArgoCD - **Operating Systems:** Linux (Ubuntu, CentOS, Amazon Linux)

**Experience** **Site Reliability Engineer Intern** | Cloudflare | San Francisco, CA | May 2025 - Aug 2025 - Deployed Prometheus exporters across 14 edge data centers, increasing metric coverage from 62% to 94% of production services - Wrote 23 Grafana dashboards tracking request latency (p50, p95, p99) for Cloudflare Workers, used daily by a team of 8 SREs - Automated TLS certificate rotation for 1,200 customer domains using a Python script integrated with Cloudflare's internal PKI, reducing manual renewal tickets by 89% - Participated in weekly incident reviews and contributed 4 post-incident action items that were implemented in production - Reduced alert fatigue by tuning 47 Prometheus alerting rules, decreasing false-positive pages by 38% over 8 weeks **DevOps Engineering Intern** | Datadog | New York, NY | May 2024 - Aug 2024 - Managed Terraform configurations for 6 AWS environments (dev, staging, production across 2 regions) comprising 340 resources - Built a CI pipeline in GitHub Actions that ran Terraform plan on every pull request, catching 12 infrastructure drift issues before they reached production - Wrote a Go-based CLI tool for log analysis that parsed 2.3 million log lines per run, reducing investigation time for on-call engineers from 25 minutes to 4 minutes - Contributed to internal Kubernetes operator that managed 85 CronJob resources, ensuring 99.7% scheduled job success rate **Teaching Assistant, Distributed Systems** | UC Berkeley | Berkeley, CA | Jan 2024 - May 2024 - Assisted 180 students with lab assignments on distributed consensus (Raft), RPC frameworks, and fault-tolerant key-value stores - Developed 3 automated grading scripts in Python that evaluated student MapReduce implementations against 45 test cases

**Education** **Bachelor of Science, Computer Science** | University of California, Berkeley | May 2025 - Relevant Coursework: Distributed Systems, Operating Systems, Computer Networking, Database Systems - Senior Capstone: Built a chaos engineering tool that injected network partitions and latency faults into a 12-node Kubernetes cluster, validating self-healing behavior across 8 failure scenarios

Mid-Career Site Reliability Engineer Resume Example (3-7 Years)

**Priya Raghavan** Seattle, WA | [email protected] | github.com/praghavan LinkedIn: linkedin.com/in/priyaraghavan

**Summary** Site Reliability Engineer with 5 years of experience building and scaling observability platforms, incident response systems, and infrastructure automation at Netflix and Stripe. Improved platform availability from 99.95% to 99.995% while supporting 3x traffic growth. Led SRE practices for a payments infrastructure handling $2.1 billion in annual transaction volume.

**Certifications** - Google Cloud Professional Cloud DevOps Engineer | Google Cloud | 2024 - Certified Kubernetes Administrator (CKA) | Cloud Native Computing Foundation (CNCF) | 2023 - AWS Certified DevOps Engineer - Professional | Amazon Web Services | 2022

**Technical Skills** - **Languages:** Python, Go, Java, Bash, HCL - **Containers & Orchestration:** Kubernetes, Docker, Istio, Envoy, Helm, Kustomize - **Observability:** Prometheus, Thanos, Grafana, Datadog, Jaeger, OpenTelemetry, PagerDuty, Loki - **Infrastructure as Code:** Terraform, Pulumi, Crossplane, Ansible - **Cloud Platforms:** AWS (EKS, RDS, DynamoDB, Lambda, CloudFront), GCP (GKE, BigQuery, Spanner) - **CI/CD & GitOps:** ArgoCD, Spinnaker, Jenkins, GitHub Actions, Flux - **Databases:** PostgreSQL, Redis, Cassandra, DynamoDB - **Chaos Engineering:** Gremlin, Chaos Monkey, Litmus

**Experience** **Senior Site Reliability Engineer** | Netflix | Los Gatos, CA | Mar 2023 - Present - Architected observability platform serving 42 engineering teams, ingesting 18 million metrics per second through a federated Prometheus + Thanos stack with 99.99% query availability - Reduced P1 incident MTTR from 34 minutes to 9 minutes by building automated diagnostic runbooks that correlated metrics, logs, and traces across 280 microservices - Designed and implemented SLO framework adopted by 38 services, with error budget policies that automatically throttled deployments when services consumed more than 80% of their monthly budget - Led migration of 14 stateful services from EC2 to Kubernetes (EKS), completing the transition with zero customer-facing downtime across 3 availability zones - Built a capacity planning model in Python that predicted compute needs 90 days ahead with 94% accuracy, saving $1.8 million annually in over-provisioned infrastructure - Reduced on-call burden by automating remediation for 12 of the top 20 recurring alert types, decreasing after-hours pages from 23 per week to 6 **Site Reliability Engineer** | Stripe | San Francisco, CA | Jun 2021 - Feb 2023 - Maintained 99.999% availability for payment processing infrastructure handling 14,000 transactions per second during peak (Black Friday, Cyber Monday) - Implemented distributed tracing with Jaeger across 65 microservices, reducing mean time to identify root cause from 22 minutes to 4 minutes for latency-related incidents - Wrote Terraform modules managing 2,400 AWS resources across 4 regions, with automated drift detection that caught and corrected 89 configuration discrepancies over 12 months - Developed a load testing framework using k6 that simulated 500,000 concurrent users, identifying 7 bottlenecks before they impacted production during a 2022 holiday traffic surge - Led 28 post-incident reviews and tracked 94% of action items to completion within 14 days, reducing repeat incident rate by 61% - Created PagerDuty escalation policies and runbooks for 9 payment-critical services, reducing escalation-to-resolution time by 43% **Junior Site Reliability Engineer** | Stripe | San Francisco, CA | Aug 2020 - May 2021 - Managed Kubernetes clusters running 120 pods across 3 environments, maintaining 99.97% pod scheduling success rate - Built Grafana dashboards tracking 1,800 SLIs for the payments API, adopted as the default monitoring view by 4 engineering teams - Automated SSL certificate management for 340 internal services using cert-manager and Let's Encrypt, eliminating 100% of manual certificate renewal tasks - Wrote Python scripts to analyze on-call metrics, identifying that 68% of pages originated from 4 services, leading to targeted reliability improvements

**Education** **Master of Science, Computer Science** | University of Washington | Dec 2020 - Thesis: "Adaptive Load Shedding in Distributed Systems Under Cascading Failures" **Bachelor of Science, Computer Engineering** | University of Michigan | May 2018

Senior Site Reliability Engineer / Staff SRE Resume Example (8+ Years)

**Marcus Chen** New York, NY | [email protected] | github.com/marcuschen LinkedIn: linkedin.com/in/marcuschen

**Summary** Staff Site Reliability Engineer with 11 years of experience designing reliability architectures for platforms serving 500+ million users. Built Google-scale observability infrastructure, led Uber's migration to multi-region active-active architecture, and established SRE practices that reduced annual incident costs by $4.2 million. Direct experience managing SRE teams of 8-14 engineers with budgets exceeding $12 million in cloud infrastructure.

**Certifications** - Google Cloud Professional Cloud DevOps Engineer | Google Cloud | 2024 - Certified Kubernetes Security Specialist (CKS) | Cloud Native Computing Foundation (CNCF) | 2023 - Certified Kubernetes Administrator (CKA) | Cloud Native Computing Foundation (CNCF) | 2021 - AWS Certified DevOps Engineer - Professional | Amazon Web Services | 2020

**Technical Skills** - **Languages:** Go, Python, Java, C++, Rust, Bash, HCL - **Platform Architecture:** Multi-region active-active, cell-based architecture, service mesh (Istio, Linkerd), edge computing - **Containers & Orchestration:** Kubernetes, Docker, Nomad, Helm, Kustomize, Crossplane, custom operators - **Observability:** Prometheus, Thanos, Cortex, Grafana, Datadog, Jaeger, OpenTelemetry, Honeycomb, PagerDuty - **Infrastructure as Code:** Terraform, Pulumi, CDK, Ansible, SaltStack - **Cloud Platforms:** AWS, GCP, Azure (multi-cloud) - **CI/CD & GitOps:** ArgoCD, Spinnaker, Tekton, Jenkins, GitHub Actions - **Databases:** PostgreSQL, CockroachDB, Cassandra, Redis, Vitess, TiDB - **Chaos Engineering:** Gremlin, Chaos Monkey, Litmus, custom fault injection frameworks

**Experience** **Staff Site Reliability Engineer** | Uber | New York, NY | Jan 2022 - Present - Architected multi-region active-active deployment across 4 AWS regions (us-east-1, us-west-2, eu-west-1, ap-southeast-1) serving 130 million monthly active users with 99.995% availability - Led a team of 12 SREs through the migration of 420 microservices to a cell-based architecture, reducing blast radius of any single failure from 100% of users to less than 8% - Designed and built a custom Kubernetes operator in Go that manages 3,400 CRDs for automated canary deployments, reducing failed deployments by 78% (from 14 per month to 3) - Implemented cost-aware autoscaling across 18,000 Kubernetes pods that dynamically adjusts replica counts based on real-time demand, SLO headroom, and spot instance pricing, saving $3.6 million annually - Built centralized SLO platform tracking 2,800 service-level indicators across 420 services, with automated error budget burn-rate alerts that prevented 23 potential outages in 2024 - Established incident command structure and trained 45 on-call engineers across 6 teams, reducing P1 MTTR from 52 minutes to 11 minutes and P2 MTTR from 3.2 hours to 38 minutes - Authored internal SRE handbook adopted by 200+ engineers, covering on-call best practices, runbook templates, and post-incident review processes - Led quarterly chaos engineering exercises injecting failures across network partitions, zone outages, and database failovers, achieving 96% automated recovery rate across tested scenarios **Senior Site Reliability Engineer** | Google | Mountain View, CA | Mar 2018 - Dec 2021 - Managed observability infrastructure for Google Cloud's Compute Engine, processing 2.4 billion metrics per minute across 28 data centers with 99.999% data durability - Designed Borgmon-to-Prometheus migration path for 14 internal teams, reducing monitoring configuration complexity by 62% while maintaining sub-second alert latency - Built automated capacity planning system that forecasted compute demand for 90+ GCE machine types with 97% accuracy over 6-month horizons, directly influencing $180 million in annual hardware procurement - Developed SLO-based release qualification system that gated deployments for 8 critical infrastructure services, catching 34 reliability regressions before they reached production - Reduced toil from 58% to 31% of team time over 18 months by building self-healing automation for the top 15 recurring operational tasks, including automatic disk expansion, unhealthy node replacement, and certificate rotation - Led cross-functional incident response for 3 Sev-1 outages affecting Google Cloud customers, coordinating 40+ engineers and delivering root cause analysis within 24 hours of resolution - Mentored 6 junior SREs through Google's SRE onboarding program, with 5 promoted to senior level within 2 years **Site Reliability Engineer** | LinkedIn | Sunnyvale, CA | Jul 2015 - Feb 2018 - Operated Kafka infrastructure processing 4.2 trillion messages per day across 1,800 brokers, maintaining 99.99% message delivery guarantee - Migrated 23 legacy services from bare metal to Kubernetes, reducing deployment frequency from bi-weekly to 12 times per day while maintaining 99.97% deployment success rate - Built a distributed load testing platform using Gatling that simulated 2 million concurrent connections, identifying 11 critical bottlenecks before LinkedIn's annual traffic peaks - Implemented automated database failover for 14 PostgreSQL clusters, reducing failover time from 8 minutes (manual) to 22 seconds (automated) with zero data loss - Created Terraform modules for LinkedIn's Azure infrastructure, managing 1,600 resources with a module reuse rate of 84% across 9 engineering teams **Systems Engineer** | Amazon Web Services | Seattle, WA | Jun 2013 - Jun 2015 - Maintained availability of EC2 fleet management systems across 3 regions, supporting 4 million active instances with 99.99% control plane availability - Automated AMI patching pipeline that applied security updates to 2,300 base images within 48 hours of CVE publication, reducing mean patch deployment time by 71% - Built monitoring dashboards in CloudWatch tracking 450 operational metrics for EC2 placement algorithms, enabling data-driven capacity decisions

**Education** **Master of Science, Computer Science** | Carnegie Mellon University | May 2013 - Focus: Distributed Systems and Networking - Thesis: "Fault-Tolerant Consensus in Heterogeneous Network Environments" **Bachelor of Science, Computer Science** | Georgia Institute of Technology | May 2011

Common Mistakes on SRE Resumes

1. Listing Tools Without Context

**Wrong:** "Experienced with Kubernetes, Terraform, Prometheus, Grafana, and AWS." **Right:** "Managed 42 Kubernetes clusters running 8,400 pods across 3 AWS regions using Terraform for infrastructure provisioning and Prometheus + Grafana for observability covering 2,100 SLIs." Tools are commodities. How you used them and at what scale is the differentiator.

2. Describing Duties Instead of Achievements

**Wrong:** "Responsible for maintaining system uptime and responding to incidents." **Right:** "Improved service availability from 99.93% to 99.99% by implementing automated canary analysis and progressive rollouts, reducing annual customer-facing downtime from 6.1 hours to 52 minutes." Every SRE is "responsible for uptime." What did you specifically do to improve it?

3. Omitting Availability Numbers

**Wrong:** "Ensured high availability of production systems." **Right:** "Maintained 99.995% availability (26 minutes annual downtime) for a payments API processing 9,400 transactions per second across 3 availability zones." "High availability" without a number is meaningless. A hiring manager at Stripe reads 99.995% and immediately understands the engineering rigor required.

4. Vague Incident Response Claims

**Wrong:** "Participated in on-call rotation and incident response." **Right:** "Led incident response for 34 production incidents over 12 months, reducing P1 MTTR from 41 minutes to 13 minutes by implementing automated diagnostic correlation across Prometheus metrics, Loki logs, and Jaeger traces." On-call participation is expected. Measurable improvement to incident outcomes is what gets you hired.

5. Ignoring the Business Impact of Reliability Work

**Wrong:** "Optimized cloud infrastructure costs." **Right:** "Implemented right-sizing automation and spot instance strategies across 14,000 EC2 instances, reducing annual AWS spend by $2.1 million (23%) while maintaining p99 latency SLOs." SRE work has dollar-value impact. Calculate it and put it on your resume.

6. Treating SRE as an Operations Role

**Wrong:** "Managed servers, deployed applications, and monitored systems." **Right:** "Wrote a Go-based Kubernetes operator that automated deployment validation for 85 services, running 12 automated checks (resource limits, readiness probes, PDB configuration) per deployment and blocking 23 misconfigured releases in Q3 2025." SRE is a software engineering discipline. Your resume should reflect that you write code to solve reliability problems, not that you manually operate systems.

7. Missing SLO/SLI/Error Budget Language

**Wrong:** "Monitored application performance and system health." **Right:** "Defined SLOs for 28 services using the error budget model, with automated burn-rate alerts that froze non-critical deployments when services consumed more than 75% of their 30-day error budget, preventing 8 potential customer-facing incidents in Q4 2025." If your resume does not mention SLOs, SLIs, or error budgets, hiring managers at companies that practice SRE will assume you have not worked in a mature reliability organization.

ATS Keywords for Site Reliability Engineer Resumes

Observability & Monitoring

Prometheus, Grafana, Datadog, New Relic, OpenTelemetry, Jaeger, Honeycomb, Splunk, ELK Stack, Loki, Thanos, Cortex, distributed tracing, log aggregation, metrics collection

Infrastructure & Cloud

Kubernetes, Docker, Terraform, Pulumi, AWS, GCP, Azure, EC2, EKS, GKE, S3, Lambda, CloudFormation, Helm, Kustomize, Crossplane, infrastructure as code

Automation & CI/CD

ArgoCD, Spinnaker, Jenkins, GitHub Actions, GitLab CI, Ansible, Chef, Puppet, SaltStack, Flux, Tekton, GitOps, configuration management

Incident Management & Reliability

PagerDuty, Opsgenie, incident response, MTTR, MTTD, SLO, SLI, SLA, error budget, post-incident review, blameless postmortem, on-call, runbook, escalation policy

Programming & Systems

Python, Go, Bash, Java, Rust, Linux, TCP/IP, DNS, load balancing, service mesh, Istio, Envoy, Linkerd, chaos engineering, Gremlin, capacity planning, performance tuning

Frequently Asked Questions

Should I list my on-call experience on an SRE resume?

Yes, but frame it around outcomes rather than participation. Instead of "participated in 24/7 on-call rotation," write "served as primary on-call for 6 production services averaging 14,000 requests per second, maintaining 99.98% availability during on-call shifts and reducing escalation rate by 34% through improved runbook automation." Hiring managers expect on-call experience. What they screen for is whether you made on-call better for the next person.

Which certifications matter most for SRE roles?

The three certifications most frequently mentioned in SRE job postings are the Certified Kubernetes Administrator (CKA) from CNCF ($445, hands-on performance-based exam), the Google Cloud Professional Cloud DevOps Engineer ($200, validates SRE practices on GCP), and the AWS Certified DevOps Engineer Professional. The HashiCorp Certified Terraform Associate ($70.50, validates infrastructure-as-code proficiency) is also increasingly valued, especially for roles that emphasize infrastructure automation. Certifications matter most for entry-level and mid-career candidates. At the staff level, your project portfolio and system design experience carry more weight.

How do I write an SRE resume with no SRE title in my work history?

Many SREs transition from software engineering, systems administration, or DevOps roles. Focus on transferable achievements: if you wrote automation that reduced manual work, that is toil reduction. If you set up monitoring and alerting, that is observability. If you improved deployment reliability, that is release engineering. Reframe your bullets using SRE terminology: "Implemented Prometheus monitoring for 12 services and defined SLOs that reduced undetected failures from 8 per month to 1" is a valid SRE bullet even if your title was "Software Engineer" or "DevOps Engineer."

Should I include a skills section or integrate tools into my experience bullets?

Both. Include a dedicated Technical Skills section grouped by category (Observability, Infrastructure, Automation, Cloud) so ATS systems can parse your tool proficiency. Then reference specific tools within your experience bullets to provide context and scale. "Prometheus" in a skills section confirms you know the tool. "Built federated Prometheus stack ingesting 18 million metrics per second across 4 regions" in your experience section proves you have operated it at production scale.

How long should a senior SRE resume be?

For engineers with 8+ years of experience, two pages is appropriate and often expected. Senior and staff SRE roles require demonstrating breadth (multi-region architecture, team leadership, cross-functional incident response) and depth (specific systems you designed, quantified outcomes you delivered). Cutting a senior resume to one page typically means removing the evidence that justifies senior compensation. Focus the first page on your most recent and impactful role, and use the second page for earlier experience and education. Every line should contain either a number or a technical specificity; remove anything that does not.

Sources

1. Bureau of Labor Statistics. "Network and Computer Systems Administrators: Occupational Outlook Handbook." U.S. Department of Labor. https://www.bls.gov/ooh/computer-and-information-technology/network-and-computer-systems-administrators.htm
2. Bureau of Labor Statistics. "Occupational Employment and Wages, May 2023: 15-1244 Network and Computer Systems Administrators." https://www.bls.gov/oes/2023/may/oes151244.htm
3. Glassdoor. "Site Reliability Engineer: Average Salary & Pay Trends 2025." https://www.glassdoor.com/Salaries/site-reliability-engineer-salary-SRCH_KO0,25.htm
4. Google. "Implementing SLOs." Site Reliability Engineering Workbook. https://sre.google/workbook/implementing-slos/
5. Google. "Error Budget Policy." Site Reliability Engineering Workbook. https://sre.google/workbook/error-budget-policy/
6. Cloud Native Computing Foundation (CNCF). "Certified Kubernetes Administrator (CKA)." https://www.cncf.io/certification/cka/
7. Google Cloud. "Professional Cloud DevOps Engineer Certification." https://cloud.google.com/learn/certification
8. HashiCorp. "Terraform Associate Certification." https://developer.hashicorp.com/certifications/infrastructure-automation
9. Rootly. "How SREs Use Prometheus and Grafana to Crush MTTR in 2025." https://rootly.com/sre/how-sres-use-prometheus-and-grafana-to-crush-mttr-in-2025
10. Coursera. "Preparing for Google Cloud Certification: Cloud DevOps Engineer Professional Certificate." https://www.coursera.org/professional-certificates/sre-devops-engineer-google-cloud