A practice prompt we wrote. No company or candidate report names it, so it carries no company tag.
How to answer
The word that is easy to skip is “chose”. The interviewer wants a deliberate bet, with the downside named and the containment in place before you started. In customer work the downside lands on the customer, not on you, so a bet only counts as chosen if someone at the customer chose it with you.
- The bet and the safe option. What you chose to do, and the path you passed on.
- Why the payoff was worth it. What the safe path could not deliver. A bet with no payoff worth having is not brave, just risky.
- The downside, named. What failure would look like, who would pay for it and how much. Say it as concretely as the payoff.
- The containment, set before you began. A time box with a kill criterion the customer’s owner agreed to in writing, a fallback kept buildable, and a limit on the blast radius: a copy of the data, one site, a switch back to the old path.
- What happened, including whether containment fired. A story where the went off and the fallback held is often stronger than a clean win.
- What you would change.
Say the kill criterion out loud as you set it: “If it can’t parse five days of production data with no mismatches by the end of week three, we build the fallback instead.” That sentence is most of the answer.
The trap is the heroic rewrite that worked out, with no fallback and no limit. It tells the interviewer you would bet a customer’s operations on your confidence.
Follow-ups
What the interviewer may ask next, once your first answer is on the table.
- Your fallback depended on the old path still working. Who kept it running, and when did you let it go?
- Did anyone else know the kill criterion before you started, and did it ever fire?
- Looking back, was the risk bigger or smaller than you thought when you took it?
Where answers go wrong
- Describes a bet with no containment, such as a rewrite shipped straight to production, which reads as recklessness rather than judgment.
- Picks a risk so small or so shared that there was no real downside, or one that happened to the speaker rather than one they chose.
Answer this in two minutes
Write the answer you would say out loud. The clock starts with your first word.
Illustrative answer about a fictional project
The biggest one was at a food wholesaler that had just launched online ordering for restaurants. Stock on the portal came from a nightly export of their inventory system, a twenty-year-old midrange application, so by afternoon it was hours stale.