Measure the load and treat pages as defects. Track pages per shift, out of hours pages and how many were actionable, then set a threshold that triggers reliability work rather than tolerating the noise. Keep the rotation wide enough that shifts are infrequent, require handover notes and a runbook per alert, give time back after a bad night, and let the team that ships a service carry it.
Why interviewers ask this
On call is where teams quietly burn out, and interviewers want a manager who treats it as a measurable system rather than a rite of passage. They listen for page volume as a tracked metric, an explicit threshold that triggers investment, recovery time or compensation, runbook discipline, and the ownership principle. Vague reassurance that you would look after people is not an answer here.
How to structure your answer
- Measure the load with specific numbers.
- Set a threshold where noise triggers engineering work.
- Protect recovery time and make the cost visible.
- Tie ownership to the team that builds the service.
Example answer
I measure it, because everybody says they care about on call health and very few teams can tell you their pages per shift. I track total pages, out of hours pages, and how many were actionable. My rule is that more than two out of hours pages in a week is a defect in the system rather than bad luck, so it goes into the next sprint as reliability work carrying the same weight as a feature. That single rule took my last team from about nine night pages a month to under two within a quarter, mostly by fixing three noisy alerts everybody had learned to ignore, which is its own kind of danger. Practically: a rotation of at least six so nobody is on more than one week in six, mandatory handover notes, a runbook per alert or the alert gets deleted, and if somebody was up at three in the morning they start late and I do not want a discussion about it. The team that ships the service carries it, because separating those two guarantees nobody fixes the noise.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What do you do if the team is too small for a sustainable rotation?
- How do you handle on call for a service nobody wants to own?
- Should on call be paid separately, and why?
Related engineering manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions