We use analytics cookies.We use cookies to analyze site traffic and improve your experience.
Loading...
System Design Masterclass · Reliability Resilience
Free preview: the first 2 parts of this 7-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design courseread the rest of this lesson in
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design coursein Reliability Resilience
This lesson is part of the full System Design Masterclass. Unlock it along with 769 other lessons for a one-time payment.
One-time payment by card or PayPal
Get Lifetime AccessOne-time payment: UPI, card or netbanking
Get Lifetime Access18 Foundation lessons are free, no payment needed. Try them now
It is easy and good
“It is really nice and good Please join the course”
On-call schedules define who responds. Rotation patterns decide how often each person carries that burden. Get the rotation wrong and your best engineers quit. PagerDuty's 2023 State of Digital Operations report found that teams with fewer than 5 people in a rotation see 30 percent annual attrition on the on-call roster. That is not a staffing inconvenience. That is a death spiral: fewer people means more shifts per person, more shifts means more burnout, more burnout means more resignations, fewer people.
Google's SRE book puts a hard ceiling on it: no more than 2 shifts per quarter per engineer. Exceed that and you start losing people. But staying under that ceiling gets complicated when you factor in time zones, follow-the-sun models, vacation coverage, and the handoff protocols that keep context from evaporating between shifts. A rotation is not just a spreadsheet. It is a system that either protects your team or slowly destroys it.
Most production teams run one of three rotation patterns. The choice depends on team size, geographic distribution, and tolerance for night pages.
| Pattern | How It Works | Team Size | Night Pages? |
|---|---|---|---|
| Weekly | One engineer carries the pager Mon 09:00 to Mon 09:00 | 4-8 | Yes |
| Biweekly | Same as weekly, 14-day shifts | 10+ | Yes |
| Follow-the-sun | Three regions chain shifts so on call is always daytime | 12+ per service | No |
Weekly rotation is the most common pattern across the industry. Biweekly reduces handoff overhead for larger teams but increases individual burden per shift. Follow-the-sun eliminates night pages entirely but requires 3x the headcount and a disciplined handoff protocol. The right choice is almost always dictated by headcount, not preference.