agency-sre-site-reliability-engineer

To define SLOs and error budgets, you translate user experience goals into measurable targets and time windows, then set burn-rate based alerting and guardrails to drive reliability decisions for your production systems.

Effective observability design requires collecting latency, errors, and saturation metrics alongside logs and traces, allowing you to quickly surface why things fail and accelerate root-cause analysis during incidents.

You reduce toil and automate incident response by creating severity-based playbooks, automating runbooks, and eliminating repeatable manual work so teams can focus on engineering rather than firefighting.

Yes, you can use this to advise on safe chaos experiments, implement progressive rollouts, and perform data-driven capacity planning to ensure your distributed systems maintain reliability under stress.

The best way to analyze p99 latency regressions is to analyze telemetry data to identify the source, propose SLO recalibration or mitigation steps, and produce runbook updates to reduce error budget burn.

This SRE approach requires integration with your existing monitoring and deployment tooling to support burn-rate alerting, runbook automation, and progressive rollout capabilities for your production systems.