惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

A
About on SuperTechFans
人人都是产品经理
人人都是产品经理
量子位
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 三生石上(FineUI控件)
小众软件
小众软件
月光博客
月光博客
T
Tailwind CSS Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
V
Visual Studio Blog
博客园 - 叶小钗
博客园 - 司徒正美
美团技术团队
博客园_首页
宝玉的分享
宝玉的分享
Apple Machine Learning Research
Apple Machine Learning Research
Hugging Face - Blog
Hugging Face - Blog
WordPress大学
WordPress大学
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
The Cloudflare Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
有赞技术团队
有赞技术团队
D
DataBreaches.Net
Google DeepMind News
Google DeepMind News

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
On-Call Wellness: Protecting Your Engineers from Burnout
Samson Tanimawo · 2026-06-27 · via DEV Community
Cover image for On-Call Wellness: Protecting Your Engineers from Burnout

Samson Tanimawo

The On-Call Burnout Epidemic

I watched three senior SREs leave our team in six months. Exit interviews all said the same thing: on-call was unsustainable.

We were spending $500K+ recruiting replacements for a problem that could have been fixed with $0 and better practices.

The Warning Signs

Before someone quits, they show these signals:

  1. Cynicism in post-mortems — "This will never get fixed"
  2. Alert numbness — Slow to respond, missed pages
  3. Vacation avoidance — "I can't take time off, who would cover?"
  4. Scope creep rejection — "That's not my problem"
  5. Meeting silence — Previously engaged, now checked out

If you see three or more of these in someone on your team, they're already halfway out the door.

What We Changed

1. Hard Cap on Pages

We set a maximum of 2 pages per 8-hour on-call shift. If someone gets paged more than that, the secondary automatically takes over and the incident is escalated as a process failure.

on_call_policy:
  max_pages_per_shift: 2
  shift_duration_hours: 8
  overflow_action: "escalate_to_secondary"
  overflow_review: "weekly_ops_review"

2. Follow-the-Sun Rotation

We stopped asking people to be on-call at 3am. With team members across US timezones, we created overlapping business-hours shifts:

Shift A (Eastern):  6am - 2pm ET
Shift B (Central):  11am - 7pm CT  
Shift C (Pacific):  2pm - 10pm PT
Overnight:          Managed by alert automation + escalation

Nobody gets paged between 10pm and 6am unless it's a true P1.

3. On-Call Compensation

We implemented:

  • $500 flat fee per on-call week
  • $200 per off-hours page
  • Comp day after any overnight incident > 30 minutes
  • On-call swaps require zero management approval

4. The "Toil Budget"

Each engineer gets a toil budget: maximum 30% of their time on operational work. If toil exceeds 30%, they're pulled from on-call until the team automates the excess.

Weekly toil tracking:
  Alert response:     4 hours
  Manual deployments: 2 hours  
  Config updates:     1 hour
  Ad-hoc debugging:   3 hours
  ─────────────────────────
  Total:              10 hours (25% of 40hr week) ✓

5. Quarterly On-Call Reviews

Every quarter, we review:

  • Pages per person
  • Off-hours disruptions
  • Toil percentages
  • Team sentiment survey
  • Attrition risk signals

The Results

Metric Before After (6 months)
Attrition rate 40%/year 8%/year
Pages per shift 4.7 1.2
Off-hours pages 12/week 2/week
Team NPS -15 +45
Recruitment cost saved - ~$400K/year

The Key Insight

On-call wellness isn't a perk. It's a business decision. Replacing a senior SRE costs $150-200K in recruiting, onboarding, and lost productivity. Preventing burnout costs almost nothing.

If you're looking to reduce on-call toil and protect your team from burnout, check out what we're building at Nova AI Ops.


Written by Dr. Samson Tanimawo
BSc · MSc · MBA · PhD
Founder & CEO, Nova AI Ops. https://novaaiops.com