domains / families / devops / pagerduty-escalation-architect

pagerduty-escalation-architect

separate

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", "sc…

When to use

• Designing escalation policies
• Creating on-call schedules
• Configuring service routing
• Composing response plays
• Auditing on-call fairness
• Setting up follow-the-sun rotations
• Managing vacation overrides
• Generating postmortems from timelines

When not to use

• Writing detection logic
• Running incidents
• Configuring monitoring stack

Skill page

Source