Reconciliation interview questions — and how to answer them

1. “Walk me through how you investigate a reconciliation break.”

A strong answer shows a method, not just effort. Describe your sequence: first confirm the break is real by checking timing differences and re-running the data, then categorize it — is it quantity, price, fee, corporate action, or settlement? Then gather evidence from both sides of the record, identify which side is wrong, and either correct your book or contact the counterparty with the specific discrepancy documented.

Close by explaining how you track the break until it clears and what you do to stop it recurring. The key phrase is “root cause”: interviewers want to hear that you fix causes, not just individual breaks.

2. “How do you prioritize when you have fifty breaks and two hours until a deadline?”

This tests judgment under pressure. Good answers start with triage criteria: financial exposure first, then regulatory or client deadlines, then age of the break, then count. Explain that you would quickly scan for clusters — breaks from one counterparty or one security often share a single cause — and that you escalate early when a break cannot be resolved before a cutoff.

Mention that you communicate the plan: the desk and your manager should know which breaks are covered, which are at risk, and who owns each. Never say you would just work faster. They are testing whether you manage the queue or let the queue manage you.

3. “Tell me about a time you found an error that nobody else had caught.”

Use the situation, task, action, result format. Pick a story — from any industry — where a small discrepancy led you somewhere important. The structure that works: what the numbers showed, what made you suspicious, what evidence you gathered, what the root cause turned out to be, and what changed afterward. End with the control or process improvement that came out of it.

If you have no finance example, a retail inventory story or a billing discrepancy story works perfectly. The interviewer is grading your detective instinct and your follow-through, not the dollar amount.

4. “What is the difference between a timing break and a true error, and why does it matter?”

This is the classic domain check. A timing break happens when both sides are correct but booked an event in different periods — a trade confirmed today that settles tomorrow, a corporate action processed on different dates. A true error means something is genuinely wrong: a wrong quantity, a missing booking, a bad price.

It matters because chasing timing breaks wastes everyone’s time and annoys counterparties, while ignoring true errors lets real risk sit on the books. Strong candidates explain that they verify timing first before escalating, and that they document which category each break falls into.

5. “How do you handle a counterparty who disagrees that the break is theirs?”

Operations is a relationship job. A good answer stays factual and calm: restate the specific discrepancy with evidence — trade reference, confirmation, the exact field that differs — and ask for their supporting record rather than arguing conclusions. If the records genuinely conflict, escalate through the agreed channel with both sets of evidence, and keep your own book accurate in the meantime rather than forcing a match.

Mention that you keep the tone professional because you will work with the same counterparties for years. Interviewers are listening for emotional steadiness and evidence-first communication.

6. “Describe a control you would put in place to prevent breaks.”

Now they are testing whether you think like an owner. Pick something concrete: a pre-settlement matching check that flags quantity mismatches before value date, a daily tolerance report that surfaces only breaks above a threshold so the team focuses on what matters, or a maker-checker step on manual journal entries.

Explain what the control catches, who acts on it, and how you would know it is working — for example, a falling count of aged breaks from a particular source. The best answers connect the control to a real pain point you have seen.

7. “Why do you want this role?”

Do not improvise this one. Connect your background to the work honestly: what you have done that resembles it, what specifically attracts you — the detective work, the market rhythm, the responsibility — and what you want to learn in the first year. Interviewers can tell the difference between “I need a job” and “I understand this job and want it.” A sentence about the team or the desk’s reputation shows you did your homework.