Wise Coding Interview Questions: Practical Coding and Money Movement

Wise, formerly TransferWise and headquartered in London, moves money across borders for people and businesses and runs the Wise Platform that banks use to offer the same transfers. Its technical process is unusually well documented: Wise publishes a guide to its pair programming interview, and that hour of collaborative coding is the first technical step for engineers. This page covers what Wise builds and who it hires, the process candidates commonly report, the technical depth the teams care about, representative problem types, what interviewers score, and a three-week prep plan.

What Wise builds and who it hires

Wise's back end is mostly Java, with Kotlin also in use, built as Spring Boot microservices that talk over Kafka and store data in PostgreSQL. A notable piece of its history: in 2018 the Bank of England announced that TransferWise was the first non-bank payment provider to join the UK's Faster Payments scheme as a direct participant, and Wise has since connected directly to payment systems in other countries. That direct access is why money-movement engineering, from pay-ins to payouts and currency conversion, sits at the centre of most teams.

• Back-end engineers: pay-ins, payouts, currency conversion and the platform banks build on.
• Mobile engineers: the Android and iOS apps.
• Front-end engineers: the web app and onboarding flows.
• Platform and reliability engineers: infrastructure, observability and developer tooling.

What the process tends to look like

Processes differ by team, level and office and change over time, so treat this as the common shape candidates report and confirm the specifics with your recruiter.

Inside the pair programming round

What Wise says it assesses. Wise's own guide lists three things: technical competency, meaning clear, maintainable and efficient code; problem solving, meaning how you clarify requirements, break the task down, handle edge cases and adapt; and communication and collaboration, meaning how you explain your thinking and respond to the interviewer's suggestions.

What it leaves out. The same guide says the session does not include system design, riddles or logic puzzles, or general questions about your past projects. Those come later, so spend the hour on the code.

Practical problems. Candidates describe problems shaped like real engineering work rather than puzzles, such as a token manager with expiry, a circuit breaker or a small state machine, with follow-ups that change the requirements. Readable structure and testable code matter as much as finishing.

Money correctness in the design round. When system design comes, expect Wise-shaped topics: an idempotent payment API, a ledger that never loses a cent, or currency conversion with quotes that expire.

Representative problem types

These are the kinds of problems candidates describe, not a leaked question list. Practice the category, not the exact question.

1. Implement a token manager that issues, renews and expires tokens.
2. Build a circuit breaker around a flaky dependency.
3. Model a transfer as a state machine with valid transitions.
4. Convert and round currency amounts without floating-point errors.
5. Process a batch of transactions and report failures clearly.
6. Design an idempotent endpoint for creating a payment.
7. Medium hash map, queue and interval problems.

What interviewers score

• Working code: a solution that runs, handles edge cases and is readable by the next engineer.
• Practical judgment: the trade-offs you name and the simplest design that meets the requirement.
• Product sense: understanding who the user is and what failure looks like for them.
• Ownership: examples where you shipped, measured and fixed things yourself.

The behavioral side

Technical rounds decide most outcomes, but every Wise loop also asks about how you work. Prepare a short story for each of these, with a result and what you learned:

• Something you shipped end to end. Cover the user problem, your decisions, what you measured and what you would change.
• A disagreement with a teammate. Show how you made the decision on evidence and kept the relationship.
• Why this company? Connect its product and engineering problems to the work you want to do next.

Structures and sample answers for the common questions are in our software engineer behavioral answers guide.

A three-week prep plan

1. Week 1: practical coding: build small features against an API, parse and transform data, and write tests, in the language you will interview in.
2. Week 2: system design for the company's domain, plus two behavioral stories about shipping and fixing something under pressure.
3. Week 3: timed mixed problems, a mock interview every other day, and research into the product and its engineering blog.

For practice lists, use LeetCode company-tagged questions; compare the European style of Booking.com and Spotify; and for design rounds, read system design building blocks.

Where CoPilot Interview fits

Most of a Wise loop is spoken: you explain an approach, defend a trade-off and talk through your past work. CoPilot Interview is an AI interview assistant whose free AI mock interview builds technical and behavioral questions from your résumé and the job description, reads them aloud and scores each spoken answer out of ten, so you can rehearse the explanation as well as the code. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Online assessments and many coding rounds forbid outside help, so practice beforehand and follow your employer's rules on the day.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

What programming language should I use in a Wise interview?

Wise's back end is mainly Java and its own guide says it tries to let you use the language you are most comfortable with. If you will not use Java, say so on the recruiter call.

Does Wise send an online assessment?

For engineers, Wise describes the pair programming session as the first technical step rather than a standalone online assessment. Some roles and graduate programmes can differ, so confirm with your recruiter.

Is it a problem if I forget exact syntax in the Wise pair programming interview?

Wise's guide says it is fine to say you have forgotten a method's exact syntax and that the interviewer will help. What counts is that you clarify the problem, narrate your thinking and keep the code clean and testable.

How should I prepare for Wise coding questions?

Practice practical problems under time limits, build small features against an API in your interview language, and prepare one system design in Wise's domain. Explain every solution out loud, because follow-up questions about trade-offs matter as much as the first answer.

Can I use AI tools in a Wise interview?

Only if the instructions you receive say so. Online assessments and live coding rounds generally forbid outside help, and some companies now state their AI policy in the invitation. Use AI to practice beforehand, and follow your employer's rules.