On a regulated broking platform, the business head of derivatives wants a new basket-order feature and its margin-calculation changes live the night before the monthly derivatives expiry, the highest-volume day of the month. A marketing campaign is already booked. Engineering has evidence that the release is risky: a load test regression, an irreversible database migration and an untested rollback.
The interviewer asks“Tell me about a time a senior business stakeholder wanted to ship something you believed wasn't safe. How did you push back, what options did you give them, and what happened? And if they had overruled you, what would you have done?”
I separate the goal from the plan: the business needs the feature in clients' hands for a campaign, not necessarily this exact release on this exact night. I bring data, not opinion: the load test result, the irreversible migration, the untested rollback, and I turn them into money and client impact compared with the cost of a short delay. Then I offer options, ship dark behind a flag, ship a subset, ship with extra guardrails, or delay a specific number of days, with my recommendation. It is the business owner's call within risk appetite, escalated if it is outside it; the decision is written down, and if I'm overruled on something that is not a control or regulatory line, I commit fully and make it as safe as I can.
A free account unlocks the rest of it, and saves your progress across every track.