Buying time and repairing misunderstandings: pause out loud, ask for what you lost, correct at once
Pause out loud, ask for exactly what you lost, and correct your own slip at once.
Predict first
Before you read: predict
ExamHall mock round, on a video call. The interviewer asks: “How would you stop a candidate —” the audio drops for a second — “— the same exam twice?” You caught every word except one.
Which reply do you give?
The 30-second version
Need time? Say so, with a length and a plan, then keep to it. Lost part of a question? Name the part and ask for it; if it has two readings, name both. Never guess the question. Misspoke? Mark the correction straight away, then restate every figure that rested on the slip.
Pause out loud, ask for exactly what you lost, and correct your own slip at once.
How it works
Step 1 of 10
Analogy: The ambulance call handler on a bad line
A caller says her neighbour has collapsed at “fourteen Mill…”, and the line breaks. The handler doesn't send the crew on a guess, and doesn't ask for everything again: “You broke up after ‘Mill’: is that Mill Lane or Mill Road?” While the system finds a crew, she says “Stay with me; give me ten seconds while I type”, because a silent line makes callers think they were cut off. Reading the address back, she hears herself say “forty”, and at once: “Correction: one-four, fourteen”. Then she updates the crew's address and arrival time, which rested on it.
| On the call | In the interview |
|---|---|
| “Mill Lane or Mill Road?” | Naming the lost part, with both readings |
| “Give me ten seconds while I type” | An announced, bounded pause |
| “Correction: fourteen”, said at once | Marking your repair straight away |
| Updating the crew's route | Restating the figures that rested on the slip |
Breaks down when: the handler runs a script and a wrong address can cost a life, while an interviewer leads the talk and can wait. The handler also sees the caller's location on screen; you have only what you heard. Wrong inference: "every unclear word needs a check." Ask only for what your answer depends on.
In real terms: before you answer, check you heard the question you're answering; before you go on, check nothing you said rests on a slip.
Try it
Answer first, then check. Nothing is saved.
Question 1 of 7
Payments-ledger round. The interviewer asks: “How would you reconcile our ledger against the bank's end-of-day statement?” You know what goes into the answer, but not yet how to lay it out.
What do you say first?
Question 2 of 7
Payments-ledger round, on a video call. Our service takes card payments from its iOS and Android apps and, each night, loads the bank's statement file into the ledger.
The interviewer asks: “How would you deal with duplicates?” Which reply do you give?
Question 3 of 7
Payments-ledger round, sizing the ledger's database. You said: “Peak is about 2,400 ledger writes a second. One Postgres primary takes 500 writes a second, so we need five primaries and we shard the ledger across them, and a peak hour writes 8.64 million rows.” Then you realise the peak is 1,200 writes a second.
Which repair do you give?
Question 4 of 7
Payments-ledger round. You explained: “Each transfer posts balanced entries, so the sum over the ledger is invariant.” The interviewer says she didn't follow and asks you to rephrase.
What do you say?
Question 5 of 7
Three situations, one line each. Pause: you are asked to design the monthly merchant statement and need a moment; say how long, and the parts you will cover. Check: the interviewer asks how you would handle a failed payout, which could mean a payout the bank rejected or one our sending job crashed on; ask which. Repair: you said a peak of 3,000 card authorisations a second needs 6 authorisation servers at 500 each, but the peak is 1,500; correct it.
Write the three lines, each starting with its label.
Question 6 of 7
Payments-ledger round, a week later. You said refunds are allowed for 30 days, then went on: “So the refund reserve holds 30 days of card volume: at £300,000 of card payments a day, that's £9 million. The nightly job re-checks each merchant's last 30 daily bank statements, one for each day a refund can still arrive. Ledger entries are kept for 7 years. A chargeback can come up to 120 days after the payment. And 40 refund disputes are opened a day, each open until its refund window closes, so the team works a queue of about 1,200 open disputes.” The window is 14 days. You noticed the slip right after the nightly-job figure, but you carried on and repair it at the end.
Besides the 30 days itself, which of your figures does that repair have to take back?
Question 7 of 7
Payments-ledger round, a week later. The interviewer asked how you would handle a chargeback, and you have spent a minute on how a merchant's refund reverses the ledger entries. She stops you: she meant a chargeback, which the card scheme raises against the merchant, not a refund the merchant gives.
What do you say?
Go deeper
Pro tip
Practise with a partner who, without warning, mumbles one word of a question, asks one with two readings, or plants a wrong figure in your notes. Under stress you reach for what you have rehearsed, and an unrehearsed phrase comes out as filler.
Related lessons
- Related: Clarify, then plan, then code
- Related: Narrating while you code
- Related: I don't know, but here's how I'd reason
- Related: Climbing the follow-up ladder: a mechanism, a number or a signal on every rung
- Related: Mechanism vocabulary: the precise term, then what the system does
- Related: Back-of-envelope estimation
- Related: Fillers and pacing under stress: count the fillers, pause at the edges, slow down where it matters
- Related: Calibrated confidence language: word each claim as sure as its evidence
Checked against the tools and docs as of 2026-10-07.