Live counter vs settlement report
A payments company shows merchants a 'today's volume' counter that must update within seconds, AND a finalized end-of-day settlement report that must be exactly correct to the cent (it triggers payouts). Transactions can be retried, reversed, or disputed hours later. ~30k txns/sec peak. Design how you serve the live counter and the authoritative report. Decide whether you run one pipeline or two, and how the two numbers reconcile so merchants don't see the live counter contradict the official report.
What a strong answer looks like
Clarify scale and constraints first. Propose a clean component breakdown, then go deep on the hard parts (data model, bottlenecks, consistency, failure modes) and name the trade-offs you are making.
Clarify5:30 left
Estimate5:30 planned
Design16:30 planned
Deep dive13:30 planned
Failure9:00 planned
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.