Skip to content
Interview rounds

Observability · On-call judgement

Five engineers, one pager, and nobody is sleeping

A team of five is worn out by its on-call rotation. How would you redesign it, and what do you do when you disagree with a call during an incident?

BackendSenior14 min
Interview-style scenarioLast reviewed: Checked against official documentation

Monday 10:00 · payments-api team, retrospectiveIllustrative scenario, not a real incident

Two of the five engineers on the payments API have asked to leave the on-call rotation

Five engineers in one office share the pager for the payments API. Each carries it for a full week, day and night, one week in five, and the pager changes hands on Monday at 09:00.

At the retrospective two of them ask to come off the rotation, and a third says she has stopped making plans in her on-call week. Your manager asks you to propose a new design by next Monday.

What the dashboards and logs show

Rotation
5 engineers, one site, a week each, 24 hours a day
Pages, last 21 days
126, about half of them between 22:00 and 07:00
Extra pay or time off
none
Hiring
no new posts this half

Clarify · optional · scored under "Hypothesis before change"

Ask the interviewer

0 of 3 asked

Each question reveals a fact. What you ask before you act is part of your score.

First move · scored under "Mitigate before root cause"

The proposal is due in a week, and someone carries the pager tonight. What do you do first?

Your rubric score, the model answer, the follow-up questions and the related lessons appear once you have answered the last step.