Wise interview, pair programming to product round.

Updated · Sources at the end

Wise publishes how it interviews engineers, round by round, and candidate reports match it closely. After a recruiter call comes a 60-minute pair programming session on HackerRank, where you solve a practical problem together with an engineer. The problem candidates report most, from London and Italy, is a circuit breaker: wrap a request handler so repeated failures stop the calls, then extend it when the interviewer changes the requirements halfway through. Then a system design round of about an hour on money moving at volume, where Wise says it is not expecting a perfect solution and cares about your reasoning. Then the round most loops don't have: a product interview led by Product Managers, sometimes with a designer or an analyst, on how you think about customers, impact and trade-offs as an engineer.

Wise moved its primary listing to Nasdaq on 11 May 2026 and keeps a secondary listing in London. It had 99 engineering roles open on its own jobs site at the end of September 2026, across London, Tallinn, Budapest, Singapore, São Paulo, Hyderabad and Austin. The backend is mostly Java, and the loop is reported the same way from every hub.

Free · 2 minutes · no account

The questions for your exact Wise role and level.

See the questions Wise asks ↓Run a free mock interview →

Interviewing at Wise? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who Wise hires

Wise hires backend engineers (mostly Java and Spring), front-end engineers (JavaScript and React), mobile, platform, data and security engineers, and engineering managers, in its hubs and in hybrid roles. It calls its engineers product engineers and expects them to own what they build with product managers, designers and analysts as equals. The loop checks that directly: the product round is scored on customer focus, prioritisation and use of data, and every team meeting is also checking for values fit.

02

What is the Wise interview process?

Wise documents each engineering round on its jobs site. Candidates report them in this order, with the product round third, as Wise's own page says. Expect weeks between rounds; one accepted candidate put the whole process at about two months.

01
Recruiter call
Phone or video, about 30 minutes

Your experience, your motivation for Wise and the role, and what happens next. Wise says the recruiter also tells you more about the role and the team.

02
Pair programming
60 minutes on HackerRank, including an introduction and five minutes for your questions

A practical problem solved together with an engineer. Wise scores three things: technical competency (clear, maintainable, efficient code), problem solving and critical thinking, and communication and collaboration. The backend is Java, but you can usually choose your language. Reported tasks: implement a circuit breaker, a circuit breaker with response caching, a REST service with Spring.

03
Front-end pair programming
About 60 minutes, 40 of them coding in JavaScript

Modern JavaScript patterns on a shared exercise. Wise states it does not allow AI tools in this round.

Front-end roles
04
System design
About an hour on an online whiteboard

Microservices, sync and async communication between services, eventual consistency, high-volume transaction processing, concurrency, data consistency and idempotency. Reported prompts: a scalable rate limiter, a payment system, a service that publishes the total money moved in the last 24 hours.

05
Product round
45 to 60 minutes with one or two Product Managers, sometimes a designer or an analyst

How you think about product and work with other functions: customer focus, impact and data, prioritisation, cross-functional work and communication. Candidates call it the product engineering fit round and describe talking through past projects and their impact.

06
Values and HR
Conversation with the hiring manager or HR

Values fit and practicalities, including pay. One senior candidate in Italy also reported a round on computer science theory, such as databases and locks.

03

Wise pair programming interview: the circuit breaker

Reported problems and how to solve them

Wise's pair programming round is 60 minutes on HackerRank with an engineer, scored on technical competency, problem solving and communication. Wise's own page asks you to explain your thinking and treat the interviewer as a colleague. The task candidates report most is a circuit breaker, and the reports say the interviewer changes the requirements partway through. Here is what the reported versions ask and how to take each.

  • Implement a circuit breaker: Three states. Closed: calls go through and failures are counted. Open: after a threshold of failures, calls fail fast without touching the service. Half-open: after a cool-down, one trial call decides whether to close or open again. Keep the thresholds configurable and the clock injectable, so the cool-down can be tested without waiting.
  • A circuit breaker with WebClient: Wrap the reactive call rather than blocking it: count errors and timeouts as failures, return a failed result immediately when open, and let exactly one request through when half-open. Say which errors should not count, such as a 4xx that is the caller's fault.
  • A circuit breaker with response caching: When the circuit is open, return the last good response if it is fresh enough, with a clear rule for how old is too old. Keep caching separate from the breaker so each can be tested alone, and say what happens when nothing is cached.
  • When the requirements change mid-interview: Candidates report the task growing while they code. Stop, restate the new requirement, and say where it fits in your design before typing. A design with small, separate pieces makes this cheap, which is exactly what the round is watching for.
  • Talking while you code: Communication is one of the three scored areas. Say what you are about to do, why, and what you are not handling yet. Ask one clarifying question at the start about failure thresholds and timeouts.

Wise says the backend is primarily Java, but you can usually use the language you know best. Practise a circuit breaker once from scratch in 40 minutes, with a test for each state change, before the interview.

04

What Wise screens for

Wise has four core values and says its interviews assess values fit. The product round's customer focus maps straight onto the third.

  • This isn't just a job, we're a revolution: the mission of making money move cheaply and quickly
  • We get it done: shipping and owning the result
  • Customers > team > ego: the order Wise asks you to decide in
  • No drama. Good karma: disagree well and move on
05

Wise interview questions

Candidate-reported themes

The technical questions candidates report are practical and close to what Wise runs in production. The product and values questions are about impact, customers and how you work with product people.

Behavioural & motivation

  • Walk me through a project you shipped and the impact it had on customers.Listening forThe customer problem · Impact in numbers · Their own part
  • Tell me about a time you pushed back on a product decision.Listening forWhy they pushed back · How they did it · What happened
  • How did you decide what to build first when everything seemed important?Listening forThe criteria · What they cut · How they checked
  • Tell me about a mistake that reached customers, and what you did.Listening forOwnership · Specificity · Learning

Technical

  • Implement a circuit breaker around a request handler: after a number of failures it stops calling the service for a while, then lets a trial request through. Talk through your states and how you would test it.Pair programming: the circuit breakerReported by four candidates, London and Italy, December 2024 to September 2025: implement a circuit breaker, one with WebClient, one with response cachingListening forClosed, open, half-open · Handles the changes · Tests and time
  • Design a system that publishes the total amount of money moved in the last 24 hours, updated continuously, across currencies.System design: money at volumeReported prompts: a scalable rate limiter; a payment system; a system to publish the total money moved in the last 24 hoursListening forThe rolling window · Counted once · Currencies and scale
  • Design a rate limiter for Wise's public API that works across many instances of a service.System design: the rate limiterReported by a senior candidate in London, April 2025Listening forAlgorithm · Shared state · When it fails
  • Build a small REST endpoint that accepts a money transfer request and returns its status. Talk through validation, errors and how you would test it.Practical backend codingReported in Austin: build a REST service with Spring. Wise's own tips list sorting, divide and conquer, dynamic programming and recursionListening forAPI shape · Validation and errors · Tests

These are the reported themes — your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level.

Predict my Wise questions →
06

Pay

Engineer L1, London£43K–£64K total
Engineer L2, London£65K–£89K total
Senior engineer L3, London£92K–£142K total

Ranges from Levels.fyi's Wise software engineer pages for Greater London, read on 30 September 2026; the London range across all levels runs from about £50K to £184K. Wise shares trade on Nasdaq and the London Stock Exchange, so equity is listed stock. Tallinn, Budapest, Singapore and the other hubs pay on local bands; ask the recruiter for the hub's range.

07

How to prepare for a Wise interview

  1. Write a circuit breaker from scratch once, in the language you will use, with a test per state change and an injectable clock. Then add response caching on top without rewriting it.
  2. Prepare a design for money moving at volume: a payment system and a rolling 24-hour total, both with idempotent ingestion and a clear answer on currency conversion.
  3. Read Wise's own page for each round before it; the scored areas are listed there.
  4. Bring two projects to the product round with the customer problem, the metric that moved and your own part in it.
  5. Prepare one story per value, especially Customers > team > ego: a time you put the customer ahead of your team's preference.
  6. For front-end roles, practise without an AI assistant: Wise does not allow AI tools in that pair programming round.

This guide covers Wise's software engineering loop. Product, analytics, operations and compliance roles have their own processes; Wise may use a case study, a take-home or a test for them. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Robinhood, HSBC or Goldman Sachs? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a Wise mock: spoken answers, coached on the spot. Your first mock is free.

Run a Wise mock →
08

FAQ & sources

What is Wise's interview process?

Wise documents each engineering round on its jobs site. The stages, in order: Recruiter call; Pair programming; Front-end pair programming; System design; Product round; Values and HR.

What does Wise look for in candidates?

Wise has four core values and says its interviews assess values fit. This isn't just a job, we're a revolution; We get it done; Customers > team > ego; No drama.

What questions does Wise ask in interviews?

The technical questions candidates report are practical and close to what Wise runs in production. Technical themes: Pair programming: the circuit breaker; System design: money at volume; System design: the rate limiter; Practical backend coding.

What is the Wise pair programming interview?

Wise's pair programming round is 60 minutes on HackerRank with an engineer, scored on technical competency, problem solving and communication. Wise's own page asks you to explain your thinking and treat the interviewer as a colleague. Covered on this page: Implement a circuit breaker; A circuit breaker with WebClient; A circuit breaker with response caching; When the requirements change mid-interview; Talking while you code.

How do I prepare for a Wise interview?

Write a circuit breaker from scratch once, in the language you will use, with a test per state change and an injectable clock. Then add response caching on top without rewriting it. Prepare a design for money moving at volume: a payment system and a rolling 24-hour total, both with idempotent ingestion and a clear answer on currency conversion.

Prep for a real Wise role

Practise your Wise interview, out loud.

Paste a real Wise posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Wise prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Wise Interview: Circuit Breaker, Product Round — Calibrd