The True Cost of Being On-Call: Engineer Hours, Burnout, and Retention in 2026

Minutes per page multiplied by pages per week multiplied by hourly rate. Includes: reading the alert, opening the runbook (or searching without one), investigating, attempting resolution, documenting the outcome. At MTTA + 23 minutes per page and 42 pages per week, this is 24.5 hours per week of engineering time per on-call engineer. That is more than half a working week consumed by alerts.

Gloria Mark (UC Irvine, 2023) found that after an interruption, engineers require an average of 23 minutes to return to full cognitive engagement with the prior task. A 5-minute alert investigation actually costs 28 minutes of productive time. For engineers doing complex distributed-systems work (incident investigation, capacity planning, architecture), this penalty is severe.

Night and weekend pages carry a cost premium beyond the direct time. Sleep disruption degrades next-day cognitive performance (Stanford research: one night of disrupted sleep reduces complex problem-solving ability by 30-40%). The 62% weekly sleep disruption rate from incident.io 2024 means most on-call engineers are operating below cognitive capacity on a chronic basis.

The SHRM replacement-cost formula puts senior technical talent replacement at 1x-1.5x annual salary, covering: recruiter fees (20-30% of base), interviewing time (40-80 engineering hours), offer overhead, signing bonus, new hire ramp (6-9 months to full productivity). At a $200K senior SRE base, replacement cost is $200K-$300K. With 41% attrition intent in the population, every team of 10 engineers has roughly 4 in the at-risk cohort.