Site Reliability Engineer

DO:

• •Include SLO/SLI/SLAs achieved.
• •Mention MTTR or downtime reductions.
• •Highlight failover or chaos engineering practices.
• •Show self-healing or automation improvements.

DON'T:

• •Leave out error budget impact.
• •Ignore traffic scale.
• •Use vague 'maintained uptime' without percentages.
• •Skip incident response leadership.

DO:

• •Include on-call leadership contributions.
• •Show MTTR reduction strategies.
• •Mention observability stack improvements.
• •Quantify RCA or failure drill impact.

DON'T:

• •Skip alerting accuracy metrics.
• •Forget to mention postmortem practices.
• •Ignore game days or reliability reviews.
• •Exclude automation scripts for incident resolution.

DO:

• •Include Kubernetes, Terraform, or Helm usage.
• •Highlight capacity planning or progressive rollouts.
• •Show cost optimization impact.
• •Mention CI/CD contributions for infra updates.

DON'T:

• •Overload with unused infra tools.
• •Ignore multi-region failover contributions.
• •Forget to list proactive monitoring enhancements.
• •Skip cross-team collaboration (security, product).

Performance Metrics:

• •Improved service reliability by 45%
• •Reduced MTTR from 75 mins to 18 mins
• •Increased deployment success rate to 98%
• •Maintained SLO compliance of 99.99%

Scale Metrics:

• •Managed 20M+ user-facing systems
• •Defined SLOs across 15+ microservices
• •Led 30+ RCA sessions
• •Conducted monthly chaos testing drills

Business Metrics:

• •Achieved <1% monthly downtime
• •Enhanced platform RTO to <5 minutes
• •Improved alert accuracy by 65%
• •Supported 5x traffic spikes during launches

SRE Practices:

SLAs/SLIs/SLOs, Error Budgets, Chaos Engineering, Capacity Planning

Infrastructure & Tools:

Kubernetes, Terraform, Helm, Ansible, Prometheus, Grafana

Incident Management:

PagerDuty, Datadog, Blameless Postmortems, On-call Leadership, Progressive Rollouts