
Tower Research Capital Data Scientist interview typically runs 10 rounds: take-home, technical screens, and onsite. The process takes several weeks and is highly technical, with a strong emphasis on practical ML experience.
$124K
Avg. Base Comp
$226K
Avg. Total Comp
10
Typical Rounds
3-5 weeks
Process Length
Our candidates report that Tower Research Capital is far less interested in polished theory alone than in whether you can connect models to trading decisions. The recurring pattern is a mix of hard statistical reasoning and very concrete implementation detail: one candidate was pushed on correlation edge cases, regularization choices, and the difference between random forest and gradient boosting, but the conversation didn’t stop there. The team then drilled into the exact features, datasets, and model choices behind prior work, and how those predictions were turned into trades. That combination tells us Tower is screening for people who can reason rigorously and also explain the operational path from data to signal.
A second theme is that the bar seems to rise when the discussion shifts from textbook ML to practical judgment. Multiple candidates described the questions as repetitive across interviews, but the ones that mattered most were the ones that tested whether the candidate had real hands-on ML experience rather than just familiarity with concepts. We also saw signs that Tower may use vague or under-specified exercises to see how candidates handle ambiguity, so the strongest responses are the ones that make clear assumptions and show disciplined thinking. In short, this process rewards candidates who can defend a modeling choice, justify why it fits the problem, and speak fluently about what happened after the model was built.
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 Tower Research Capital process.
I went through a pretty long process with Tower Research Capital, and the most memorable part was how much it mixed theory with practical ML discussion. In total there were 10 rounds, though in my case it also included a Hackerrank take-home that was a 3-hour notebook-style test with multiple research problems. The instructions were pretty vague, and one of the coding prompts even had an incorrect description, so it felt a bit under-specified for the amount of work expected. It also came across more like something aimed at a new grad than an experienced candidate.
The live interviews were mostly technical and fairly repetitive across rounds: linear regression, probability, coding, and general ML fundamentals. A few of the regression questions were genuinely hard, not just standard textbook stuff. One that stood out was a correlation puzzle: given Corr(X,Y) > 0, Corr(Y,Z) = 0, and Corr(X,Z) > 0, they asked which coefficient would be bigger between Y ~ X and Y ~ X, Z. I also got asked about L1 vs L2 regularization, lasso versus ridge, and the difference between random forest and gradient boosting. There was one brain teaser style question too, including a banana-transport puzzle. The final round was onsite, and they seemed to care a lot about whether I had real hands-on ML experience. They asked very concrete questions about what features I had built, which dataset I used, which models I chose, and how I converted predictions into trades. I heard back fairly quickly after most rounds, but the final round took longer. In the end they said I didn’t have enough practical ML experience for the role, so I didn’t get an offer. My main takeaway is to be ready for both tricky regression/statistics questions and very specific questions about how your past ML work actually translated into production decisions.
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 Tower Research Capital
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Employee Salaries | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Subscription Overlap | |
| Experiment Validity | |
| Find the Missing Number | |
| Cumulative Distribution | |
| Compute Deviation | |
| Maximum Profit | |
| Prime to N | |
| Bagging vs Boosting | |
| Last Transaction | |
| String Shift | |
| 500 Cards | |
| Session Difference | |
| Random SQL Sample | |
| Rain in N Days | |
| Paired Products | |
| Alphabet Sum | |
| Bank Fraud Model | |
| Hurdles In Data Projects | |
| Swipe Precision | |
| Rectangle Overlap | |
| Unique Work Days | |
| Over-Budget Projects |
Synthesized from candidate reports. Individual experiences may vary.
An initial conversation to review your background, interest in the role, and overall fit for Tower Research Capital. Based on the experience, this likely serves as the first filter before the more technical rounds.
A notebook-style take-home with multiple research problems and coding prompts. The instructions were described as vague, and at least one prompt had an incorrect description, so candidates should expect an under-specified assignment that tests both coding and problem-solving.
Several live technical interviews focused on linear regression, probability, coding, and core machine learning fundamentals. Questions could be repetitive across rounds and included harder-than-standard regression/statistics problems, regularization concepts like L1 vs L2, model comparisons such as random forest vs gradient boosting, and at least one brain-teaser style puzzle.
The final round was onsite and emphasized practical machine learning experience. Interviewers asked detailed questions about past projects, including what features were built, which datasets and models were used, and how predictions were turned into trading decisions.