What to Expect in the Airwallex System Design Interview

Question

Design Gurus · Accepted Answer

Expect at least one design round of about 45 to 60 minutes, based on Airwallex's own problems. Candidates report design questions about multi-currency wallets, double-entry ledgers, idempotent transaction engines, end-of-day reconciliation, and event-driven payment flows. Reports differ on whether design appears in one round or in two.

You will not get a generic photo sharing question. You will get money moving between accounts, currencies, and countries, and correctness is graded as strictly as scale.

The Question Types

Multi-currency wallets and ledgers: design the store of balances for a business that holds several currencies at once. A ledger is the record of every money movement, and double-entry bookkeeping means each movement is written twice, so every transaction sums to zero. The hard parts are precision, currency conversion, and a history you can still explain months later.

Idempotent transaction engines: idempotent means a repeated request produces the same result as a single request. Reports name this topic directly, because a retry must never send a second payment. Expect questions about request keys, stored results, and what happens when the caller times out.

Reconciliation and end of day: reconciliation means matching your own records against a bank partner's records, and a record that does not match is called a break. Expect questions about daily files, matching rules, and who is alerted when a break stays open.

Event-driven payment flows: reported topics include cascading failures in asynchronous payment flows, where asynchronous means the caller does not wait for the final result. Job posts name Kafka and gRPC, so expect questions about queues, retries, and message ordering.

Latency across jurisdictions: a jurisdiction is a country or region with its own financial rules, and Airwallex works under many of them at once. This topic is typical for a payments company of this type, not confirmed as a reported question. Expect questions about where data is stored, and how one region can fail while the others keep running.

What the Interviewer Grades

Four things decide this round.

The requirements, before any drawing. Agree on the customers, the volumes, and the money flows before you draw a single box.
The rules that must always be true. State them early: the records always balance, no payment is ever sent twice, and every balance can be explained from its history.
Trade-offs named out loud. Connect each one to money rather than to elegance. Airwallex job posts list security and data integrity as responsibilities, so say how your design protects both.
Depth under follow-up questions. Reports say interviewers ask repeated follow-up questions about consistency, so defend every choice with a reason.

A Walkthrough: A Multi-Currency Wallet and Payout Service

Requirements, about five minutes: business customers hold balances in several currencies, and they receive money, convert it, and pay suppliers in other countries. Two rules apply at all times. The records balance, and no payout is ever sent twice.
The data model: create one account per customer per currency, and record every movement as a transaction with two or more entries that sum to zero. Store the entries append-only, so nothing is ever edited. A balance is then the sum of its entries, kept fast with a periodic snapshot.
Idempotency: every write includes a client key, and you store that key with the result of the first attempt. A retry then returns the stored result.
The payout flow: model the payout as a state machine with created, funds reserved, submitted to the network, and then settled or failed. Reserve the funds first, so the same balance cannot be spent twice, and write ledger entries at every state change.
Currency conversion: quote a rate with an expiry time, hold that rate while the transaction completes, and record the rate used on the entries. Never convert at a rate you cannot reproduce later.
Failure handling: publish events to downstream services through an outbox table, which is a table of pending events written in the same transaction as the data. No event is then lost when a write succeeds. Make every consumer idempotent, and send repeatedly failing messages to a separate queue for human review. To correct a mistake, write a reversing entry rather than deleting history.
Reconciliation: load each bank partner's daily file, match it against your ledger by reference and amount, and report the records that do not match. Alert a person when a break stays open past a limit you set.
Scale and regions: partition by customer, because one customer's transactions belong together, and keep regulated data inside the region that requires it. Run currency conversion and payout submission as separate services with their own limits.

Common Mistakes in This Round

Updating a balance in place. A balance column that you overwrite destroys the history an audit needs.
Skipping idempotency. Networks retry, so without request keys a retry becomes a second payment.
No reconciliation story. If you cannot say how you would prove the records are right, the design is unfinished.
Choosing eventual consistency for balances. Two withdrawals can then pass at the same time, so keep strong consistency inside one account and explain the cost.
Ignoring rules per country. Payment methods, settlement times, and data rules differ, so mention this early, before the interviewer asks.

How to Prepare

Learn the building blocks. Grokking the System Design Interview covers queues, caches, databases, and consistency, which every ledger question depends on.
Study the harder cases. Advanced System Design Interview, Volume II helps with replication, partitioning, and failure handling across regions.
Rehearse the walkthrough. Practice the eight steps above out loud, in under 40 minutes, without notes.
See the full loop. This round is one part of the Airwallex interview process, alongside the motivation question, and the reported waits are in how long it takes to hear back.