On-Call Burden measures the time commitment, alert volume, and cognitive toll experienced by engineers participating in production on-call rotations. Excessive on-call load leads to burnout, sleep disruption, and reduced productivity during regular working hours. Tracking this metric ensures that operational responsibilities are distributed fairly and that investment in system reliability reduces the human cost of keeping services running.
Stress and cognitive toll of production support. 83% of engineers report burnout from on-call.
Similar dynamics. Code ownership (CODEOWNERS) becomes more important to route incidents correctly in a large monorepo with many teams.
AMPLIFIED: Follow-the-sun on-call requires clear runbooks and context handoff between TZs. Without it, each TZ shift starts from scratch on ongoing incidents. Isolation during night pages is worse without nearby colleagues.
On-call rotation burden scales with system complexity. 83% of on-call engineers report burnout. Larger systems mean more pages and harder diagnosis.
Anxiety, sleep disruption.
52% say burnout is why peers leave.
Anticipatory anxiety prevents deep work.
More incidents = more pages.
Faster resolution, fewer false alarms.
Fewer devs = more frequent rotations.
Slow recovery = longer incidents.