Thomson Reuters Data Analyst interview typically runs 3 rounds: phone screen, technical interview, HR round. The process usually takes 2-3 weeks and is fairly standard, with a practical, business-focused style.
$83K
Avg. Base Comp
$89K
Avg. Total Comp
3-4
Typical Rounds
2-3 weeks
Process Length
Our candidates report that Thomson Reuters is less interested in flashy theory and more interested in whether you can explain how you actually work. The recurring prompts were about due diligence investigations, the tools you’ve used, and how you think through analysis from start to finish. That tells us the team is screening for judgment, not just output: they want analysts who can make sense of messy business questions and communicate a defensible approach without overcomplicating it.
A second pattern is that the technical bar is real, but it stays grounded in day-to-day analyst work. Multiple candidates mentioned SQL as the core technical signal, with some Python and resume-based follow-ups, plus interpreting query results rather than just writing syntax. We’ve also seen that the broader interview can feel friendly and straightforward, which makes it easy to underestimate how much they care about clear reasoning under pressure. If your answers sound polished but vague, that tends to be a miss here.
The non-obvious thing is how much they seem to value fit for a regulated, client-facing information business. Questions about strengths and weaknesses, open-source versus proprietary tools, and analytical problem-solving all point to a team that wants analysts who are practical, careful, and credible. In our view, the strongest candidates are the ones who can connect their analysis choices to business impact and show they understand the difference between doing analysis and delivering trusted answers.
Synthesized from 2 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 Thomson Reuters process.
A recruiter reached out to me about four months after I had submitted my resume online, which was already a good sign because I had mostly forgotten about the application. The process started with a phone screen and then moved to a panel interview over Teams. That part felt pretty standard and the questions were more about how I think through the work than anything overly tricky. I was asked to walk through my approach to a due diligence investigation, and there was also a question about what open source and proprietary tools I had used. Nothing felt out of the ordinary, and the interview itself seemed to go well, but I never got an offer. I followed up with the recruiter about 10 days later and didn’t hear back, then reached out again about a month after the interview and was told that some of the Analyst roles had been filled while others were on hold.
The other process I went through was a bit more structured: a three-round loop with a HackerRank OA, a technical interview, and an HR round. The technical interview was mostly SQL, with a little Python and some resume-based questions, and the HR round leaned into analytical questions to check problem-solving. There wasn’t a separate technical test beyond the OA, but the SQL portion did include writing queries and interpreting outputs, so I would not treat it as a casual screen. Overall the process was friendly and moved quickly, usually within two to three weeks, but the bar seemed to be on being able to explain your analysis clearly and handle SQL comfortably under pressure.
Prep tip from this candidate
Be ready to explain a due diligence or investigation workflow clearly, since that came up directly in the panel. Also practice SQL output questions and writing queries from scratch, plus a few concise examples of tools you’ve used in analysis work.
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 Thomson Reuters
The role of A/B testing in measuring the success rate of an analytics experiment
| Question | |
|---|---|
| Bias vs. Variance Tradeoff | |
| Data Preparation for Imbalanced Data | |
| Boosting Instagram Stories | |
| Your Strengths and Weaknesses | |
| WhatsApp Metrics | |
| Docs Metrics | |
| Time Series Discrepancies | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Comments Histogram | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Slacking Employees Salaries | |
| Experiment Validity | |
| Subscription Overlap | |
| Compute Deviation | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| Prime to N | |
| 500 Cards | |
| Session Difference | |
| Department Expenses | |
| Last Transaction | |
| Rain in N Days | |
| Like Tracker | |
| P-value to a Layman |
Synthesized from candidate reports. Individual experiences may vary.
A recruiter typically reaches out after an online application, sometimes months later. Once contact is made, the process tends to move quickly.
The first live conversation is a standard phone screen with a recruiter. It focuses on your background, interest in the role, and whether your experience aligns with the Data Analyst position.
Some candidates go through a HackerRank assessment before the live technical rounds. This step appears to be used to screen for SQL and basic analytical ability.
The technical round is mostly SQL-focused, with some Python and resume-based questions. Candidates may be asked to write queries, interpret outputs, and explain how they approach analysis work.
In some processes, candidates meet with a panel over Teams instead of or in addition to a single technical interviewer. Questions are practical and business-focused, including how you would approach a due diligence investigation and what open source or proprietary tools you have used.
The final round in the more structured process is an HR interview. It leans into analytical and problem-solving questions to assess judgment, communication, and fit before a final decision.
