Transferwise (Wise) software engineer candidates report a HackerRank assessment, often a Maki video assessment, and a pair-programming round on practical OOP tasks. One describes a longer loop with system design and product rounds.
$108K
Avg. Base Comp
$125K
Avg. Total Comp
3-6 rounds
Typical Rounds
1 month
Process Length
Reports on the Transferwise (Wise) software engineer interview describe a process that mixes practical coding with real attention to motivation and how you work with others. Accounts often open with a HackerRank assessment that pairs an easy-to-medium algorithm problem with a REST API task, and Java comes up in a few of them.
Several candidates then describe a Maki assessment with culture-fit questions, an attention-to-detail section, a coding quiz and recorded video answers. Prompts included why you want to join Wise, why this role, and what you hope to gain. One candidate who was rejected after a recorded stage had a Java problem and five behavioral questions, with three recording attempts and no interviewer on the other end.
The pair-programming round is the best-documented technical stage. Candidates worked with engineers on practical object-oriented tasks: a circuit breaker, a money-transfer scenario, and filling in business logic in an existing Java skeleton on HackerRank. One candidate was allowed to use Google or ChatGPT. In several accounts, interviewers cared about explanations, edge cases and collaboration as much as the final code.
Longer loops show up too. One candidate describes six rounds, including a recruiter call, live coding, a system design question about summing transfers over a time window, a product-mindset interview and a behavioral round. One three-stage process took about a month. Ask your recruiter what your loop looks like, and practice walking through your reasoning aloud.
Synthesized from 11 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.
2 rounds
Questions asked:
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 | |
|---|---|
| Messenger Payments | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Payments Received | |
| Merge Sorted Lists | |
| Total Spent on Products | |
| Top 3 Users | |
| String Shift | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Comments Histogram | |
| Last Transaction | |
| Get Top N Frequent Words | |
| Like Tracker | |
| Google Maps Improvement | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Maximum Profit | |
| Prime to N | |
| Cumulative Distribution | |
| Over-Budget Projects |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe an initial recruiter or HR call. One report has the recruiter asking about previous roles and experience, and another describes common HR questions about motivation. Come with a concise summary of your background and a clear answer on why Wise.
Several candidates report a HackerRank assessment with an easy-to-medium, LeetCode-style algorithm problem and a REST API task. Java appears in some accounts, and one candidate called the difficulty manageable. Practice a medium problem and a practical API task under timed conditions.
Some candidates describe a Maki assessment with culture-fit questions, an attention-to-detail section, a coding quiz and video answers on motivation, why Wise and why the role. One candidate rejected after a recorded stage had a Java problem and five behavioral questions with three recording attempts. Rehearse short answers aloud.
Candidates describe pair programming with engineers on practical object-oriented tasks. These included a circuit breaker, a money-transfer scenario and completing logic in a Java skeleton on HackerRank. One candidate had a one-hour session with about 15 minutes of background discussion. Expect to explain decisions and edge cases.
One candidate describes six rounds, including live coding on a money transfer system and a system design question on summing transfers over a time window. That loop also had a product-mindset interview and a behavioral round, and the interviewers were described as supportive. Confirm the format with your recruiter.
