The On-Call Rotation
What you'll learn: How engineering teams organize on-call schedules to ensure someone is always ready to respond to production incidents.
Understanding On-Call Responsibilities
An on-call rotation is a schedule that determines which engineer is responsible for responding to alerts and incidents during specific time periods. Think of it like a hospital emergency room—someone must always be available when urgent issues arise, but no single person can or should be on duty 24/7.
When you're on-call, you're the first responder for production incidents. This means:
- Acknowledging alerts when they fire
- Investigating the immediate issue
- Taking action to restore service
- Escalating when you need additional expertise
- Documenting what happened for post-incident review
Rotation Schedules and Structures
Teams organize rotations in various ways:
Duration: Common shifts include one week, two weeks, or even 24-hour periods. Longer shifts provide more context continuity; shorter shifts reduce individual burden.
Coverage: Teams might split by time zones (follow-the-sun), weekdays versus weekends, or business hours versus after-hours. Global teams often pass the on-call duty across regions.
Primary and Secondary: Many teams designate a primary on-call engineer and a secondary backup who escalates if the primary doesn't respond or needs help with complex issues.
The Purpose: Shared Ownership
The on-call rotation embodies you build it, you run it. It ensures engineers understand production impact, creates accountability for system reliability, and distributes operational burden fairly across the team. No one should carry the pager alone indefinitely—that leads to burnout.
The rotation also provides learning opportunities: junior engineers see production patterns, and everyone develops operational maturity.
Key Takeaway: The on-call rotation ensures continuous incident response coverage while distributing responsibility fairly, connecting engineers directly to their code's production behavior and promoting shared ownership of system reliability.