Top 3 Recovery Interview Questions
Browse 3 real-world technical and behavioral interview questions about Recovery. Review scenarios, edge cases, and architectural best practices.
The monthly bill run dies two thirds of the way through and the cycle closes tomorrow. What do you do?
Restart rather than rerun. The run is not a transaction but a sequence of per-account commitments, so each account must be either fully billed or untouched, charge assembly must be deterministic from inputs frozen at cut-off, and quarantining the offending accounts beats missing the cycle.
The electronic record will be down for a four-hour upgrade, and it also fails without warning. How does a ward keep working?
Plan for four modes rather than one: a continuously fed read-only viewer on independent infrastructure, printed ward-level essentials, paper ordering with pre-allocated temporary identifiers, and a recovery process that backloads events at their original times and reviews everything that queued during the window.
You are mid-demo and the product fails in front of the customer. What do you do, and what do you do afterwards?
Name the failure out loud immediately, take one narrated attempt at it, then route around it to keep the meeting's purpose intact. Afterwards, send a same-day written note saying what broke and what you are doing, tell the truth about whether it was a defect or a gap, and re-demo on a named date.