What to Expect in the Wise System Design Interview

Question

Design Gurus · Accepted Answer

Expect a design problem shaped like real Wise work: moving money safely between systems. Candidates report that Wise design interviews use business cases, mostly for senior roles. You might design a transfer flow, a ledger, or an integration with unreliable bank partners. The evaluation values correctness above raw scale. A social product can lose one like without damage. A payments product cannot lose one cent.

Why Money Changes the Design Interview

Wise moves money between countries for millions of customers. Three facts shape every design discussion. First, operations must not be lost or duplicated, even when networks fail. Second, external banks are slow and sometimes unavailable, and the design must expect that. Third, regulators require complete records, so every money movement needs an audit trail. An audit trail is a permanent record of who did what and when. Mention these three facts in any question you get, even a generic one. They separate candidates who have thought about money systems from candidates who have only read about web scale.

The Question Types

Design a money transfer flow. The signature question type: a user pays in one currency, and a recipient receives another. It tests state modeling, retries, and failure handling.
Design a ledger. A ledger is an append-only record of every money movement, where entries are added but never edited. Expect questions about double-entry recording. Every movement is written twice: a debit in one account and a credit in another. With this rule, the totals always balance.
Design around unreliable partners. Bank APIs time out, return errors, or answer twice. The design must retry safely and reconcile afterward.

What Interviewers Evaluate

Four signals decide the result. First, do you ask about failure cases before designing the success case? Second, do you name correctness tools without being asked: idempotency, transactions, and reconciliation? Third, can you explain trade-offs in plain words, such as why exact-once delivery is expensive? Fourth, do you keep the customer visible: what does the sender see while a bank is slow?

The format is often collaborative. The interviewer behaves like a teammate and questions your choices as you make them. Practice designing aloud, because a silent five minutes counts against you in this format.

A Worked Example: Design an International Transfer

Requirements. A user sends dollars, a recipient receives euros. The transfer must complete or fail visibly, never silently disappear. Confirm the expected volume and the completion time target before designing.

The state machine. Model the transfer as a state machine. That means the transfer is always in exactly one named state. Examples: created, funded, converted, paid out, and failed. Every change between states is recorded with a time and a reason.

Idempotency. The client sends an idempotency key with each request: a unique value that lets the server detect retries. A retried request returns the original result instead of creating a second transfer.

The ledger. Record every movement as double-entry lines. The user's payment, the currency conversion, and the payout each produce balanced entries.

Queues and retries. Steps run through a message queue, so a slow bank delays one transfer without delaying all of them. Failed steps retry with increasing waits, and a human queue receives anything that keeps failing.

Currency conversion. Conversion happens at a recorded rate, stored with the transfer. If the payout later fails, the stored rate makes the refund exact.

Reconciliation. A daily job compares internal records with bank statements and reports every difference. Name this step: interviewers at payment companies listen for it.

Monitoring. Track transfer completion time, failure rate per partner bank, and the count of transfers stuck in one state. Alert when any of them changes suddenly.

How to Prepare

Learn the standard building blocks. Grokking the System Design Interview explains queues, databases, and caching with complete examples.
Study the patterns behind payments. Grokking the Advanced System Design Interview goes deeper into consistency and failure handling for senior loops.
Know the whole process. What is the Wise interview process like? shows where this round appears and who runs it.
Prepare the non-technical rounds. Review Top Wise behavioral interview questions and the motivation question, because the same interviewers often ask both.