The business wants faster shipping, your on-call team is burning out from incidents. How do you resolve that?
What they are really testing: Whether you can turn a values argument into a data-driven agreement. The strongest answers refuse the false choice and introduce a mechanism that decides objectively.
A real interview question
The business wants faster shipping, your on-call team is burning out from incidents. How do you resolve that?
What most people say
drag me
“Explain to the business that we need a feature freeze to focus on stability for a quarter.”
It concedes the false choice and spends political capital on a pause that does not fix the causes. Work resumes at the same rate afterwards, the underlying fragility is unchanged, and the team learns that stability requires stopping.
The follow-ups they ask next
The business agrees the budget then wants to override it during a launch. What do you do?
Make the risk explicit and let them decide with eyes open, since it is a legitimate business call. Record it. Repeated overrides mean the target is wrong and should be renegotiated honestly rather than ignored.
How do you set the target without guessing?
Work backwards from user impact and cost: what downtime is actually noticed, what it costs, and what each extra nine costs to achieve. Targets should come from the business consequence, not from a round number.
What the interviewer is listening for
- Rejects the false trade-off with evidence
- Introduces a mechanism deciding in advance
- Acts on burnout immediately, not after the strategy
What sinks the answer
- Asks for a feature freeze
- Frames it as engineering versus business
- No data behind the position
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“I reject the trade-off, since [high performers are faster AND more stable]. I get [change failure rate and grouped incident causes], then propose [an error budget with an agreed consequence, decided in advance]. That [lets the business ship freely while in budget]. Meanwhile [fix the rota and delete noisy pages now, since fatigue causes incidents].”
Keep going with strategy
Principal
You join a 200-engineer company where every team built its own deployment tooling. What is your strategy?
Principal
When would you tell a company not to use Kubernetes?
Principal
Your team wants to build an internal developer platform. A vendor sells one. How do you decide?
Principal
Tell me about a time you argued against your own proposal or changed your mind on a significant technical decision.
Principal
One slow dependency takes down your entire system. Why does that happen and how do you prevent it?
Principal
Design multi-region failover for a system that currently runs in one region, targeting 15 minutes recovery.
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free