PagerDuty Engineer Interview Questions and Answers (2027)

45 PagerDuty engineer interview questions: Events API v2, dedup_key, escalation policies, schedules, Event Orchestration, Terraform and incident response.

Sep 18, 2025 - 18:11
Nov 5, 2026 - 15:38
 0  102
PagerDuty Engineer Interview Questions and Answers (2027)

PagerDuty engineer interviews test whether you can build and run an on-call system: services and integrations, the Events API v2, escalation policies and schedules, urgency and priority, Event Orchestration, alert grouping, incident workflows, the REST API and Terraform, plus how you run an incident and reduce noise afterwards. This page has 45 questions with direct answers.

Facts about limits, endpoints and payload fields were checked against the PagerDuty documentation in November 2026.

Key takeaways

  • Know the object model cold: an event becomes an alert on a service, alerts become incidents, incidents follow the service's escalation policy, and escalation rules point to schedules or users.
  • Events API v2 sends to https://events.pagerduty.com/v2/enqueue with event_action set to trigger, acknowledge or resolve, and a dedup_key of up to 255 characters.
  • An escalation policy can have up to 20 rules and repeat up to nine times; the default timeout is 30 minutes.
  • Change events show recent deploys on a service but never notify anyone.
  • Senior rounds focus on noise: Event Orchestration, urgency rules, alert grouping and a review loop that removes pages nobody acts on.

How this page fits with the other PagerDuty guides

This is the main PagerDuty question set, written for engineers who configure and automate PagerDuty. For incident drills read real-time PagerDuty interview questions and scenario-based PagerDuty questions. For a study plan use the PagerDuty interview preparation guide. To see how PagerDuty compares with other tools, read 12 on-call management tools for SRE and DevOps.

ObjectWhat it isInterview angle
ServiceSomething you own and get paged forHow fine grained should services be?
IntegrationHow events reach a service (key, email, built-in)Which integration key to use where
AlertA normalized event on a serviceDeduplication and grouping
IncidentWork that needs a humanUrgency, priority, assignment
Escalation policyWho gets notified, in what orderTimeouts, repeats, round robin
ScheduleWho is on call whenLayers, overrides, handoffs

PagerDuty questions for freshers

1. What is PagerDuty?

PagerDuty is an incident management platform. It takes signals from monitoring tools, decides whether they need a human, notifies the right on-call person through push, SMS, phone or email, escalates if nobody responds, and records the response. It also offers status pages, automation and analytics.

2. What is a service in PagerDuty?

A service represents an application, component or piece of infrastructure that a team owns. Events arrive at a service through integrations, and the service decides how to handle them: which escalation policy to use, what urgency, and how alerts group. Good services map to something a responder can act on.

3. What is the difference between an alert and an incident?

An alert is a record of a problem signal on a service, created from an event. An incident is the unit of work a person is notified about and responds to. Several alerts can group into one incident, so a database outage that fires twenty checks pages someone once.

4. What is an escalation policy?

An escalation policy is an ordered set of rules that says who is notified for an incident and when to move to the next level. Each rule targets users or schedules and has a timeout. If the incident is not acknowledged before the timeout, PagerDuty escalates to the next rule.

5. What is an on-call schedule?

A schedule defines who is on call at any time. It is built from layers, each with a rotation (for example weekly), a handoff time and a list of users. Higher layers override lower ones where they overlap, and overrides let someone cover a shift without changing the rotation.

6. What does acknowledging an incident do?

Acknowledging tells PagerDuty and the team that someone is working on it. It stops further escalation and notifications for that incident. If the service has an acknowledgement timeout, the incident returns to triggered after that time if it is still open, so it is not forgotten.

7. What is incident urgency?

Urgency is high or low. High urgency notifies responders right away using their high-urgency notification rules and escalates. Low urgency uses quieter rules and does not escalate in the same way. Services can set urgency always high, always low, by support hours, or dynamically from event severity.

8. What is incident priority, and how is it different from urgency?

Priority (for example P1 to P5) describes business impact and is used for reporting, filtering and triggering workflows. Urgency controls how people are notified. A P1 is almost always high urgency, but they are separate fields that you set for different reasons.

9. What are notification rules?

Each user sets personal rules for how and when to be contacted, for example push immediately, SMS after two minutes, phone call after five, with separate rules for high and low urgency. Interviewers like candidates who say they test their own rules before their first shift.

10. What is an integration key?

An integration key (routing key) identifies where events go. A service integration key sends events to one service. An Event Orchestration routing key sends events to a global orchestration that routes them to services by rules. The monitoring tool includes the key with every event.

11. What is a maintenance window?

A maintenance window is a period during which a service does not create incidents from new events. You use it for planned work so alerts during the change do not page anyone. Remember to scope it to the services affected rather than the whole account.

12. What is a business service?

A business service represents a capability customers recognize, such as "Checkout", built on technical services through service dependencies. It lets stakeholders see impact without reading technical alerts, and it can drive status updates.

PagerDuty questions for 2 to 5 years of experience

13. How do you send an event with the Events API v2?

POST JSON to https://events.pagerduty.com/v2/enqueue with the routing key, the event action and a payload containing summary, source and severity:

{
  "routing_key": "YOUR_INTEGRATION_KEY",
  "event_action": "trigger",
  "dedup_key": "checkout-api/high-error-rate",
  "payload": {
    "summary": "checkout-api error rate above 5%",
    "source": "prometheus-prod",
    "severity": "critical",
    "component": "checkout-api",
    "custom_details": { "error_rate": "7.2%" }
  },
  "links": [{ "href": "https://grafana.example.com/d/checkout", "text": "Dashboard" }]
}

A 202 means accepted. Severity must be critical, error, warning or info.

14. How does dedup_key work?

Events with the same dedup_key and routing key apply to the same open alert. A new trigger with the same key adds to the existing alert instead of creating a new one, and acknowledge or resolve events with that key update it. If you leave it out on a trigger, PagerDuty generates one and returns it, so store it if you plan to resolve automatically. The key can be up to 255 characters.

15. What happens if you send resolve for an alert that does not exist?

Nothing is created. PagerDuty documents that acknowledge or resolve events without a currently open alert do not create a new one, and acknowledge or resolve events sent with a different routing key from the original trigger are dropped.

16. How should a client handle Events API errors?

Do not retry 400: the JSON is invalid and needs fixing. Retry 429, 5xx responses and network errors with backoff. PagerDuty's rate limits change dynamically, so build retries into the sender rather than assuming a fixed rate. Payloads can be up to 512 KB.

17. What are change events?

Change events record changes such as deployments or config updates on a service. They appear in the incident context so responders can see "what changed recently", but they never create incidents or notify anyone. Send them from your CI/CD pipeline after each deploy.

18. What is Event Orchestration?

Event Orchestration processes events before they become alerts. Global orchestration receives events through one routing key, applies rules and routes them to services; service orchestration applies rules within one service. Rules can change severity, set priority, add notes, suppress, or route based on event fields.

19. What happens to events that match no routing rule in a global orchestration?

They hit the catch-all rule. By default unrouted trigger events create suppressed alerts, which do not notify anyone, but you can route them to a specific service instead. A good practice is to route them to a triage service so new sources are not silently ignored.

20. How do you decide when to use global versus service orchestration?

Use global orchestration when one event stream feeds many services, for example a shared monitoring platform, or when the rule applies across many services. Use service orchestration for rules specific to one team's service. Events sent directly to a service integration bypass global rules.

21. What are the limits on escalation policies?

A policy can have up to 20 escalation rules and can repeat up to nine times. The minimum timeout is one minute when a rule has one target and three minutes with multiple targets; the default is 30 minutes. With round robin scheduling enabled on the account, a rule can assign targets in turn.

22. How do you design a schedule for a team across time zones?

Use a follow-the-sun setup with one layer per region, each restricted to working hours in that region, so nobody is paged at night. Add a backup schedule as the second escalation level. Keep rotations long enough for context (often one week) and plan handoffs at a time both sides are awake.

23. How do support hours and urgency work together?

You can set a service to use high urgency during support hours and low urgency outside them, so non-critical alerts wait until morning. There is an option to raise unacknowledged low-urgency incidents to high when support hours start. Critical services should stay high urgency at all times.

24. What are the alert grouping options?

Time-based grouping puts alerts into one incident for a set window. Content-based grouping groups alerts that share field values you choose. Intelligent grouping uses machine learning on past behaviour. Availability depends on plan and add-ons, so check what the account has before you promise a design.

25. What are incident workflows?

Incident workflows automate response steps. They start from a conditional trigger (for example when priority becomes P1) or a manual trigger from the web app, mobile app, Slack, Microsoft Teams or API. Actions can add responders, create a Slack channel or video bridge, post status updates or call webhooks.

26. How do you call the PagerDuty REST API?

Send requests to https://api.pagerduty.com with an API key in the Authorization: Token token=... header and Accept and Content-Type set to JSON. Some write calls require a From header with a valid user email. Use pagination parameters for lists.

curl -s https://api.pagerduty.com/incidents?statuses[]=triggered \
  -H "Authorization: Token token=$PD_API_KEY" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json"

27. How do you manage PagerDuty as code?

Use the PagerDuty Terraform provider to define services, escalation policies, schedules, teams and orchestration rules in Git. Changes go through review, environments stay consistent, and you can recreate configuration if someone deletes it by mistake. Keep API keys in your secret store, not in the repository.

resource "pagerduty_service" "checkout" {
  name              = "checkout-api"
  escalation_policy = pagerduty_escalation_policy.payments.id
}

28. How do you connect Prometheus Alertmanager to PagerDuty?

Add a pagerduty_configs receiver in Alertmanager with the integration key as routing_key, route critical alerts to it, and let Alertmanager send resolve messages when alerts clear. Group alerts in Alertmanager by labels such as alertname and service so PagerDuty does not get a flood.

receivers:
  - name: pagerduty-critical
    pagerduty_configs:
      - routing_key: "<integration-key>"
        severity: critical

29. How do you link PagerDuty with Slack?

Install the PagerDuty Slack integration, connect services to channels, and let responders acknowledge, resolve or add notes from Slack. Use incident workflows to create a dedicated channel for major incidents. Keep the source of truth in PagerDuty so the timeline is complete.

30. What are auto-resolve and acknowledgement timeouts on a service?

Auto-resolve closes incidents left open for a set period, useful for alerts that have no resolve signal. Acknowledgement timeout moves an acknowledged incident back to triggered after a period so it is not parked forever. Use both carefully: auto-resolve can hide real problems if set too short.

31. How do you add context so responders can act fast?

Include a clear summary, the component, custom details with the values that fired, links to dashboards and runbooks in the event, and change events from deploys. A responder should know what broke, how bad it is and where to look first from the notification alone.

PagerDuty questions for senior engineers

32. How do you decide service boundaries?

Create a service for each thing a single team owns and can fix, usually per application or major component, not per host or per check. Too few services send everyone every page; too many make routing and reporting messy. Model dependencies with business services so impact still rolls up.

33. How do you reduce alert fatigue?

Measure first: pages per shift, night pages, and incidents resolved without action. Then remove or downgrade alerts nobody acts on, move symptom alerts to user-facing signals tied to SLOs, use orchestration to suppress known noise, group related alerts, and review the list every week with the on-call team.

34. How do you design an alerting strategy around SLOs?

Page on fast error budget burn that threatens the SLO soon; send slower burns as low-urgency incidents or tickets. Keep cause-based alerts (disk full, queue backing up) for things that will become user impact without action. This approach is described in the Google SRE workbook chapter on alerting on SLOs.

35. What roles do you assign during a major incident?

An incident commander who coordinates and makes decisions, subject matter experts who investigate, a communications lead who updates stakeholders and status pages, and a scribe who keeps the timeline. PagerDuty publishes its own incident response guide that describes these roles.

36. How do you run a postmortem?

Write a blameless review within a few days: timeline, impact, contributing causes, what went well, and action items with owners and dates. Use the incident timeline from PagerDuty as the starting point. Track action items to completion, because a review without follow-up does not prevent the next incident.

37. How do you keep on-call sustainable?

Limit how often each person is on call, track night pages per person, give time off after heavy shifts, make sure there is always a backup, and give new engineers shadow shifts before they go primary. Interviewers want to hear that you treat on-call load as an engineering metric.

38. How do you migrate from another paging tool to PagerDuty?

Inventory existing alerts, teams, schedules and escalation paths; clean them up rather than copying noise; define services and policies in Terraform; run both tools in parallel for a period with the new one in a test mode; then switch integrations service by service and confirm every critical alert reaches a human.

39. How do you test that paging actually works?

Send test events through each integration to a test service, confirm the right person is notified within the expected time, and check each user's contact methods. After schedule or policy changes, verify who is on call in the schedule view. Some teams run regular synthetic pages for critical paths.

Scenario-based PagerDuty questions

40. You got paged at 3 a.m. for an alert that cleared on its own. What do you do the next day?

Check how often this alert fires and clears, and whether anyone ever took action. If it is noise, raise the threshold, add a duration condition, lower its urgency or remove it. Record the change and tell the team. One false page is a bug in the alerting.

41. A critical alert fired in monitoring but nobody was paged. How do you investigate?

Follow the path: did the monitoring tool send the event (check its logs for a 202), which routing key did it use, did orchestration suppress or route it elsewhere, was the service in a maintenance window, did the escalation policy have an empty schedule layer, and did the user's notification rules work? Fix the gap and add a test.

42. One deployment produced 300 incidents in ten minutes. How do you prevent this next time?

Group alerts by service or content so one failure produces one incident, set a consistent dedup_key in the sender, and add orchestration rules that recognize the pattern. Send a change event for the deploy so responders link the incidents to it at once.

43. The primary on-call did not acknowledge and the secondary was asleep too. What do you change?

Review the escalation timeouts and add a third level (for example the team lead or a manager rotation), enable repeats, and check both users' notification rules include phone calls for high urgency. Talk about why nobody answered without blame; it may be a load problem.

44. A service owner wants every warning to page them. How do you respond?

Ask which warnings required action in the last month. Agree that only alerts needing immediate action page as high urgency, and send the rest as low urgency, a ticket or a dashboard. Offer to revisit after two weeks of data.

45. You need to auto-remediate a known disk-full alert. How would you build it?

Trigger a workflow or automation action when the alert arrives, run a safe and tested cleanup script, then let the monitoring tool send resolve when the disk recovers. If the cleanup fails or the alert returns, escalate to a human. Log every automated action on the incident.

How to prepare for a PagerDuty engineer interview

  1. Create a free trial account and build one service, one schedule and a two-level escalation policy.
  2. Send trigger, acknowledge and resolve events with curl using the same dedup_key.
  3. Connect Alertmanager or Grafana to the service and fire a test alert.
  4. Define the same service in Terraform and apply it.
  5. Write a one-page postmortem for an imaginary outage using the format above.

PagerDuty usually sits behind a monitoring stack, so review Prometheus and Grafana together and 10 incident management tools too. For the bigger SRE picture see the role of SREs in DevOps teams. Our Prometheus and Grafana training covers alert rules and Alertmanager routing, in our Kharadi, Pune classroom and live online.

Official references

FAQs

What is the Events API v2 endpoint?

Alert events go to https://events.pagerduty.com/v2/enqueue with a routing key, an event_action of trigger, acknowledge or resolve, and a payload with summary, source and severity.

How many levels can a PagerDuty escalation policy have?

Up to 20 escalation rules, and the policy can repeat up to nine times. The default escalation timeout is 30 minutes.

Do change events page anyone?

No. Change events add context about recent deploys or changes to a service, but they never create incidents or notifications.

What is the difference between urgency and priority?

Urgency (high or low) controls how responders are notified. Priority (such as P1 to P5) describes business impact and is used for reporting and workflows.

Can I manage PagerDuty with Terraform?

Yes. The PagerDuty Terraform provider manages services, escalation policies, schedules, teams and Event Orchestration rules as code.

What happens to events that match no Event Orchestration rule?

They go to the catch-all rule, which by default creates suppressed alerts that do not notify anyone. You can route them to a service instead.

Is there a PagerDuty certification?

PagerDuty has offered training and certification through PagerDuty University. Check PagerDuty's site for the current programs before listing one on your CV.

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.