Technical interview guide

On-Call & Alerting Design

Designing alerts that page for what actually needs a human, and structuring on-call sustainably.

Read: 28 min
Practice MCQs: 25
Interview QA: 25
Edition: v5
Editorial status: Reviewed
Relevant for: AI EngineerDevOps EngineerForward Deployed Engineer (FDE)Site Reliability Engineer

Scope: Google SRE, Prometheus, Alertmanager, OpenTelemetry, and NIST guidance current 2026-08-31.

Interview QA

Treat each question like a live interview question: answer out loud first (structure, assumptions, tradeoffs), then open the model answer to spot gaps and rehearse a tighter follow-up.

Curated: 2026-10-05 · Written: 2026-10-05 · Reviewed: 2026-10-03

QA-1

Design on-call and alerting for a growing service.

QA-2

Decide whether a condition should page, ticket, or remain telemetry.

QA-3

Design multiwindow burn-rate alerts for an SLO.

QA-4

Investigate an alert that fires on every deployment.

QA-5

Reduce a page storm during a shared dependency outage.

QA-6

Design a safe silence workflow.

QA-7

Test the full alert delivery path.

QA-8

Design a sustainable on-call rotation.

QA-9

Handle an unacknowledged critical page.

QA-10

How do you implement alert deduplication, grouping, and rate-limiting at scale during an alert storm?

QA-11

Respond when monitoring data disappears.

QA-12

Tune an alert with high false-positive volume.

QA-13

Find and fix a missed incident alert.

QA-14

Design low-volume correctness alerts.

QA-15

Govern alert labels and annotations safely.

QA-16

Design alert routing for a multi-team platform.

QA-17

Review on-call fatigue and staffing risk.

QA-18

Design an on-call handoff for an active incident.

QA-19

Protect sensitive security-alert evidence.

QA-20

Migrate a legacy threshold-alert catalog.

QA-21

Measure alerting-program effectiveness.

QA-22

Test alerting during a provider outage.

QA-23

Design alerts for queues and asynchronous work.

QA-24

Review an alert rule before production rollout.

QA-25