Site reliability engineer — SLOs, observability and incidents that end with a better system
Staff Site Reliability Engineer · Paylane
divya@example.com | Bengaluru, India | zenoprofile.com/divya | github.com/example | linkedin.com/in/example | example.com
Eight years of reliability work for payment and marketplace platforms: SLOs and error budgets, Kubernetes at scale, OpenTelemetry end to end, incident command and the engineering that follows. 99.99 % over the last eighteen months, with the receipts.
Reliability lead for a payments platform; team of six; SLO platform, observability, incident process.
Reliability for a marketplace with festival-season peaks of 30× normal traffic.
Services for a lending product; became the person who got paged, then the person who fixed why.
SLOs and error budgets, Incident command, Capacity planning, Chaos engineering, Prometheus / Thanos, Grafana, OpenTelemetry, Loki / Tempo, Kubernetes, Kafka, PostgreSQL, Terraform, Go, Python, PromQL
SLO definitions as code, burn-rate alerts, error-budget reports to every team lead on Monday morning. 210 SLOs, 140 services.
Opens the channel, pages the right people, keeps the timeline, drafts the postmortem. Nobody writes the timeline by hand any more.
Quarterly game days with real failure injection in production-like environments; 31 findings fixed so far.
English (Fluent), Malayalam (Native), Kannada (Conversational)