Transferwise Software Engineer candidates report online coding and recorded-response assessments, followed in some cases by collaborative programming focused on practical implementation, design choices, and communication.
$143K
Avg. Base Comp
$220K
Avg. Total Comp
3-6 rounds
Typical Rounds
1-1 months
Process Length
Transferwise Software Engineer candidates commonly describe a process that tests practical coding alongside communication. Several candidates started with a HackerRank assessment containing an algorithmic problem and a REST API task; reported difficulty ranged from easy to medium. Some then encountered a Maki assessment with recorded video responses, culture- or motivation-focused questions, attention to detail, and coding questions.
For the live technical portion, collaborative problem solving is a recurring theme. Candidates report pair programming with two engineers on practical OOP work, including a circuit-breaker implementation in one account and a money-transfer implementation in another. One candidate also described system design around summing transfers over a specified time window. Be ready to explain decisions, respond to input, and keep the discussion moving while you code.
Preparation should cover concise answers about your background, motivation, learning style, and feedback, because those topics appeared in recruiter, recorded, and live discussions. Practice a medium-level coding problem, a hands-on REST API task, and a small design exercise that makes your tradeoffs explicit. The exact sequence varies across reports, including one account describing six rounds.
Synthesized from 5 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.
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 | |
| Employee Salaries | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Prime to N | |
| Cumulative Distribution | |
| Hurdles In Data Projects | |
| Over-Budget Projects | |
| Top 3 Users | |
| Google Maps Improvement | |
| Total Spent on Products | |
| Find the Missing Number | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Minimum Change | |
| Maximum Profit | |
| Rectangle Overlap |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report either an early recruiter conversation about prior experience and motivation or a HackerRank assessment. Reported assessment content includes an easy-to-medium algorithmic problem and a practical REST API task, with Java mentioned by some candidates.
Some candidates report a Maki assessment that combined coding questions, attention to detail, culture-fit prompts, and recorded video responses. Prepare concise explanations of why you want the role, what you hope to gain, and how you approach work and feedback.
Candidates who reached a live technical stage describe working with two engineers in a HackerRank-style environment. Reported exercises include practical OOP work, implementing a circuit breaker, and a money-transfer scenario; one account also mentions designing transfer aggregation over a time window.