PagerDuty is the canonical incident management platform — when your prod system breaks, PagerDuty is what wakes the on-call engineer. The interview emphasizes reliability engineering, 24/7 system design, and the human-systems aspects of handling alerts at scale.
Process
Recruiter screen → 60-minute coding phone (DSA medium) → onsite virtual: 2 coding, 1 system design, 1 craft deep-dive, 1 behavioral. Cycle: 3–4 weeks.
What they actually ask
- Design an alert routing system with escalation policies and overrides. Focus on the data model tying services to schedules and escalation policies, and how an unacknowledged alert climbs from the primary on-call to the next tier. Interviewers probe overrides (someone covers a shift), time zones in rotations, and deduplication so a single incident doesn’t page the whole team.
- Design a notification fanout: SMS, voice call, push, email — at sub-second latency. Talk through per-channel providers with fallback (if the SMS gateway is down, retry on another), idempotency so a retry doesn’t double-page, delivery receipts, and respecting carrier and provider rate limits. The fanout question is really about keeping latency low while a message may hop across three providers.
- Design a status page that aggregates signal from multiple integrations. The key point is that it must stay up when the systems it reports on are down, so decouple it — ingest health via webhooks or polling into its own store, and serve a heavily cached, read-mostly page. Discuss how you reconcile conflicting signals and avoid flapping.
- Coding: medium DSA, often graph or tree problems. Expect BFS/DFS, traversals, and dependency-style graphs that map to how alerts and services connect. State time and space complexity before you code and walk through one example by hand.
- Behavioral: ownership, navigating ambiguity, the customer-trust framing. Bring a real incident story — what broke, what you owned, how you kept customers informed — and structure it so cause, action, and outcome are clear.
Levels and comp (2026)
- SE II: $150K–$185K total
- Senior SE: $220K–$280K
- Staff: $300K–$400K
- Principal: $420K–$560K
Prep priorities
- Read about Tier-1 reliability practices: SRE workbook, Google SRE book. Internalize SLOs, error budgets, and blameless postmortems, and be ready to reason about why a system might choose availability over consistency during an outage.
- Be fluent in JVM languages (Scala dominates the codebase) or willing to ramp up. You won’t be quizzed on obscure Scala syntax, but show you can read functional-style code and explain how you’d get productive fast.
- Understand telephony integrations and the realities of carrier delivery latency. SMS and voice go through third-party providers with variable, sometimes multi-second delivery, which is why fallback channels and delivery confirmation matter for a paging product.
Frequently Asked Questions
Is PagerDuty remote-friendly?
Hybrid in San Francisco, Toronto, Atlanta, and Lisbon. Many engineering roles are fully remote within the supported countries.
How does PagerDuty compare to Opsgenie?
PagerDuty is the dominant brand; Opsgenie (Atlassian) is the budget enterprise alternative. PagerDuty has stronger US enterprise penetration and richer API ecosystem.
What is the engineering culture like?
Reliability-obsessed. Senior engineers do real on-call. Outages are studied with rigor. Strong post-mortem and blame-free culture.
Similar company guides
Prepping for PagerDuty? Put it to work:
