Transferwise Data Scientist interview typically runs 3 rounds: online behavioral assessment, HackerRank assessment, final live interview. It usually takes over 3 hours and is heavily online with very little human interaction.
$117K
Avg. Base Comp
$161K
Avg. Total Comp
3
Typical Rounds
1-2 weeks
Process Length
We've seen TransferWise lean hard on breadth, and the candidate experience here makes that clear. The process feels less like a single deep technical screen and more like a series of filters for whether you can move comfortably across product judgment, statistics, coding, and applied modeling. One candidate described the online work as a mix of scenario-based judgment, coding, CS knowledge, probability, and a notebook exercise with exploratory analysis and a simple model. That combination suggests the company is looking for someone who can connect the dots across disciplines, not just someone who can optimize one narrow skill set.
A recurring theme is the lack of scaffolding. The notebook exercise reportedly came with no documentation, which turned it into a test of whether you already know the workflow and tools well enough to operate independently. That matters because it hints at what TransferWise likely values in data scientists: practical fluency, speed of execution, and comfort working without hand-holding. Candidates who expect a guided case study or a collaborative whiteboard discussion may be caught off guard by how self-contained the assessment is.
The live conversation then shifts the bar in a different direction. Rather than drilling into algorithms, it probes how you define data science, how you distinguish a Data Scientist from a Machine Learning Engineer, and how you think about one project you care about. We've seen that kind of questioning reward candidates who can explain their judgment clearly and defend their choices with real examples. In other words, TransferWise seems to care as much about how you frame your work as the work itself.
Synthetized from 1 candidates 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 whole thing felt very time-spending and a bit impersonal, and I ended up spending well over 3 hours on it. It started with an online behavioral assessment that was basically a multiple-choice website with short video scenarios, so it felt more like reacting to workplace situations than having a real conversation. After that came a HackerRank assessment that bundled several different parts together: a coding section, a general computer science knowledge section, a math section focused on probability and stats, and then a full Jupyter notebook exercise where I had to do exploratory analysis and train a simple model with scikit-learn. There was no documentation to lean on, so you were expected to know the code and workflow by heart, which made it feel more like a memory test than a guided data science task.
The final round was the only live interview, and it was surprisingly non-technical. They asked about my beliefs around data science, including how I would describe data science and what I think the difference is between a Data Scientist and a Machine Learning Engineer. Then they asked me to walk through one project I was proud of and explain why it stood out to me, followed by a few follow-up questions digging into that work. I appreciated that it was more reflective than algorithmic, but it also meant the process was pretty broad and a little hard to prepare for in a standard way. I didn’t get an offer, and my main takeaway was that you should be ready for a long, multi-part online process with very little human interaction, plus a final conversation that tests how you think about the role rather than your technical depth alone.
Prep tip from this candidate
Be ready to explain your view of data science versus machine learning engineering, and have one project you can defend in detail, since the final round focused on that more than technical grilling. For the HackerRank portion, practice doing exploratory analysis and training a simple scikit-learn model without documentation, because the notebook section expected you to know the workflow cold.
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
How would you negotiate and resolve disagreements when a client rejects your proposed solution?
| Question | |
|---|---|
| Incentive Scheme | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Comments Histogram | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Cumulative Distribution | |
| Experiment Validity | |
| Button AB Test | |
| String Shift | |
| Last Transaction | |
| Alphabet Sum | |
| Prime to N | |
| Paired Products | |
| Bank Fraud Model | |
| P-value to a Layman | |
| Swipe Precision | |
| Unique Work Days | |
| Bagging vs Boosting | |
| Over-Budget Projects | |
| Third Purchase | |
| Top 3 Users | |
| Hurdles In Data Projects | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Variable Error | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
The process starts with a multiple-choice behavioral assessment delivered through a website with short video scenarios. It focuses on how you react to workplace situations rather than on live conversation.
Candidates then complete a long, multi-part HackerRank test that combines coding, general computer science knowledge, probability and statistics, and a Jupyter notebook exercise. The notebook portion includes exploratory analysis and training a simple model with scikit-learn, with little or no documentation provided.
The only live round is a broad, mostly non-technical interview about your beliefs around data science and the differences between a Data Scientist and a Machine Learning Engineer. You also walk through a project you are proud of and answer follow-up questions about your work.