Transferwise (Wise) Software Engineer candidates report online coding and recorded assessments followed by collaborative technical interviews, with Java, REST APIs, OOP design, motivation, and communication appearing in individual accounts.
$182K
Avg. Base Comp
$220K
Avg. Total Comp
3-6 rounds
Typical Rounds
1-1 months
Process Length
Transferwise, now known as Wise, Software Engineer interview reports describe more than one route through the process, so prepare for the recurring components without assuming every candidate receives the same sequence. Two offer recipients described an initial HackerRank assessment combining a problem-solving task with a REST API exercise. One described the difficulty as easy to medium; another characterized the algorithm portion as LeetCode-style.
A Maki assessment and recorded video responses appeared in two accounts. Those candidates encountered motivation, role-interest, culture-fit, attention-to-detail, and coding questions. Prepare concise answers about your background, why Wise and the role interest you, learning style, and feedback approach, while remaining ready to complete them without a live interviewer. One other candidate reported a recorded interview with a Java problem and five behavioral questions.
Live collaboration is the clearest technical preparation theme. Offer reports describe pair programming with two engineers through HackerRank. Tasks varied: a practical OOP problem, a circuit-breaker implementation, and a money-transfer exercise; the newest report involved completing missing business logic in an existing Java skeleton. Explain your decisions as you code, inspect the surrounding structure before changing it, and deliberately cover edge cases. One reported system-design discussion focused on aggregating transfers over a time window, while another included a separate product interview. Evidence on the exact route is limited because reported processes differ.
Synthesized from 6 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Transferwise process.
The pair-programming round was conducted on HackerRank. I was given a skeleton with existing classes and method signatures, and the task was to implement the missing business logic. The focus was on writing clean Java code, understanding the existing structure, handling edge cases, and explaining design decisions while coding.
After I finished writing the implementation, they asked me to walk through my code step by step and explain the logic. They wanted me to describe how the solution worked, why I made certain decisions, and how I handled edge cases.
Prep tip from this candidate
Practice completing missing business logic in an existing Java codebase, then walk through your implementation, design choices, and edge cases aloud.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Transferwise
Write a query to show the number of users, transactions, and total order amount per month in 2020
| Question | |
|---|---|
| Client Solution Pushback | |
| Messenger Payments | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Total Spent on Products | |
| P-value to a Layman | |
| Prime to N | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Over 100 Dollars | |
| Find the Missing Number | |
| Minimum Change | |
| Scrambled Tickets | |
| Maximum Profit |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report HackerRank assessments that combined a LeetCode-style problem-solving question with a REST API task. One offer recipient described the tasks as easy to medium, while another called the assessment manageable; prepare for both practical API work and coding under assessment conditions.
Some candidates report a Maki assessment covering coding, attention to detail, culture fit, and recorded motivation responses. Another report described a recorded interview with a Java problem and five behavioral questions. Prepare concise responses because this format may not provide live clarification.
Several candidates report pair programming with two engineers. Reported work included a practical OOP problem, implementing a circuit breaker, a money-transfer task, and completing missing Java business logic in an existing code skeleton. Explain design choices and edge-case handling while coding.
One candidate reported a system-design discussion about summing transfers over a time period, plus product and behavioral interviews; another described motivation, background, learning style, and feedback discussion before pair programming. These discussions may vary by candidate route.
