Site Reliability Engineering
SLOs, error budgets, incident response and blameless postmortems — reliability as an engineering practice, not a hope.
// uptime is a feature
Hey, I'm Devesh Saini 👋
🟢 Open to audits, projects and retainers · book a call →
I design, automate and run production infrastructure — Kubernetes, AWS, Terraform, CI/CD and observability. When I'm off-call, I build small mobile apps for fun.
// about

I'm a site reliability engineer who treats production like a product: measured, automated, and boring in the best way. Over the years I've moved workloads to Kubernetes, rebuilt CI/CD pipelines, and put observability in place before incidents demanded it.
Off-call, I ship small mobile apps — partly for fun, partly because building the whole thing keeps my empathy for developers sharp.
// services
SLOs, error budgets, incident response and blameless postmortems — reliability as an engineering practice, not a hope.
AWS and GCP design, multi-region setups, migrations and cost optimization that pays for itself.
Cluster design, autoscaling, hardening and the boring operational discipline that keeps workloads healthy.
Pipelines, GitOps and release engineering — from commit to production without human toil.
Metrics, logs and traces with Prometheus, Grafana and OpenTelemetry. See problems before customers do.
Terraform and Ansible for infrastructure that is reviewed, versioned and reproducible.
// career
Bridge engineering and customers for a leading work-management platform — designing technical solutions, building proof-of-concepts, and translating reliability and integration requirements into working implementations. The engineer in the room when the answer has to actually run in production.
Site reliability for enterprise data pipelines — kept large-scale ETL and analytics workloads healthy for global clients. Built Grafana dashboards and alerting that caught pipeline failures before business reports broke, and automated recurring incident toil across the platforms I supported.
Ran production Java web applications on Linux — deployments, monitoring, incident response, and root-cause fixes. Automated routine operations with scripting and hardened the environments I supported, keeping the applications I owned stable and boring in the best way.
// selected work
// off-call builds
IOSA mindful digital mala for naam jap and mantra jap — count, track, and reflect on your daily practice.
iOSOn-call schedules that hand themselves off. Live countdowns, auto-built rotations, and reminders before every handoff.
IOSThe offline DevOps toolkit — cron, CIDR, JWT, YAML and cheat sheets, one tap away.
// live from github
Python-Based Log Analysis & Auto-Remediation Tool
// git journal
Single-node to 3-node HA. Etcd snapshots to S3-compatible MinIO. Longhorn for storage.
They must agree or you drop requests on deploys. Wrote a preStop sleep hook into our base chart.
Handoff notifications now respect quiet hours. First feature built entirely from user feedback.
1,200 rps on a $5 VPS thanks to SQLite + one Node process. Boring tech wins again.
// education & certs
Cloud Native Computing Foundation · Score 94/100
Amazon Web Services
HashiCorp
Quantum University
// author

Self
Your service went down at 2 a.m. Was that acceptable? Nobody knows — because nobody ever defined what "reliable" means.
// cooperation
“Devesh rebuilt our deployment pipeline and our on-call stopped being a nightmare within a month. The postmortem culture he introduced outlasted his contract.”
“Rare mix: deep infrastructure knowledge and the patience to teach it. Our cloud bill dropped 40% and the team understood why.”
“Handed him a fragile legacy stack; got back Terraform, runbooks, and a team that ships daily.”
// engagements
// writing
#SRE6 minMost postmortems produce a document nobody reads. Here is the structure that produces fixes instead.
Teams drowning in Grafana panels usually skipped one step: deciding what reliability actually means for their users.
Corrupted state, a deleted workspace, and one very bad force-unlock. What each incident taught me about safe IaC.
// faq
Cloud migrations, Kubernetes setups, CI/CD pipelines, observability rollouts and reliability audits. Anything from a one-week infra audit to a multi-month migration.
Yes — I work with teams worldwide, async-first, with overlap hours agreed up front.
We start with a short call, I scope the work into a fixed plan with milestones, and every project ends with documentation, runbooks and a handover session for your team.
Yes. The SRE Retainer covers ongoing reliability work, incident support and monthly reviews — or 30 days of support is included with every project.
// contact