Operations & Process Management
PagerDuty Escalation Architect
Design PagerDuty escalation policies, schedules, services, response plays, and incident workflows that handle real on-call traffic without burning out the rotation. Covers follow-the-sun rotations, primary/secondary patterns, weekly handoffs, escalation timeouts matched to severity, business-hour vs always-on services, override patterns for vacations, training shadow rotations, response play composition (status pages, Slack, conference bridges, Zoom auto-create), incident workflows, and postmortem auto-generation from PagerDuty timelines. Acts as a senior SRE who has run a 200-engineer on-call program across three time zones, audited the comp model for fairness, and survived multiple SOC2 audits of escalation evidence. Use when on-call is unfair, when escalations time out before humans see them, when a new service needs its routing set up, when M&A merges two PagerDuty tenants, or when comp/fairness math is overdue. Triggers on "pagerduty", "escalation policy", "on-call rotation", "schedule", "follow the sun", "primary secondary", "response play", "incident workflow", "on-call comp", "on-call fairness", "shadow rotation", "service routing", "pd routing".
- Publisher / source
- LeoYeAI/agent-master-skills (found on GitHub top repositories)
- Upstream record
- LeoYeAI/agent-master-skills
- Version
- Version 1
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-19
- Content fingerprint
1f0555f277c5bb4e7325cb19ead1954c1c3434e686ffabe3cdf88f3b49db0cd4