Thomson Reuters Business Analyst interview typically runs 3 rounds: HireVue screening, Zoom with two hiring managers, and an in-person interview. The process took about a few weeks and was straightforward but somewhat inconsistent.
$85K
Avg. Base Comp
$109K
Avg. Total Comp
4
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Thomson Reuters is less interested in a deep technical grilling for Business Analyst roles than in whether you can quickly make sense of an ambiguous, metrics-driven environment. The strongest signal in the experience we saw was the repeated focus on understanding the job requirements and being able to explain how your background fits a business-facing, measurement-oriented team. Even the screening leaned on written and recorded responses about working with metrics, which suggests they want people who can communicate clearly and operate comfortably with structured business data.
A recurring theme, though, is that the process can feel uneven. One candidate noted that the recruiter conversation seemed to shift the role away from the posting, and another said the hiring managers only spent a short time on the conversation despite a longer slot. That inconsistency matters: it tells us the company may be testing for adaptability, but it also means candidates need to be alert to whether the role is being described consistently across conversations. We’ve also seen that basic company awareness is expected — not as a trivia check, but as a way to confirm you understand Thomson Reuters’ professional-services context.
The non-obvious make-or-break factor here is clarity. The candidate who shared this experience specifically called out the lack of a salary range and uncertainty about whether the opening had been reopened. In our view, that means candidates should treat the process as a two-way diligence exercise: if the role description, reporting line, or scope feels fuzzy, that’s not a small detail. At Thomson Reuters, the interview may be simple on the surface, but alignment on the actual job appears to be a major signal.
Synthesized from 1 candidate report 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.
The interview process at Thomson Reuters moved along smoothly, and the HR team was genuinely helpful early on—when I had to reschedule one round due to illness, they accommodated without any pushback. That said, once I was deep in the pipeline, communication became sparse, and I never got meaningful feedback after being rejected.
It started with a HackerRank assessment covering multiple-choice questions and some output-based debugging problems. Then came a recruiter phone screen focused on my background and job fit. After that, I had a manager review conversation about my experience and resume, followed by a hiring manager interview that dug into similar territory—mostly behavioral and resume-based questions.
The pivotal day was the technical round, which compressed two interviews into one session. First was a live coding problem I'd classify as medium difficulty, but here's what threw me: I'd prepped extensively on LeetCode-style algorithmic questions, but they asked a competitive programming problem instead. I could reason through the logic, but I didn't have the coding patterns down fast enough, which cost me. The system design round was more project-focused—they asked me to walk through something I'd built, then expanded it by adding new features and asking about RAG implementation, chunking strategies, and overall cloud architecture workflow. That was a different kind of pressure, less about algorithm speed and more about design thinking under constraint.
I didn't clear those technical rounds, so the final job fit interview never happened for me. When I asked HR for feedback multiple times afterward, they didn't respond. It stung a bit, but in hindsight the misalignment between my prep and their question style was the real issue.
Prep tip from this candidate
Don't assume LeetCode classic problems will dominate—Thomson Reuters asked a competitive programming-style coding question, so practice problems that require unfamiliar algorithms and patterns under time pressure. Also prepare to discuss your own project work in depth for system design, especially if RAG or cloud architecture applies to the role.
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 | |
|---|---|
| Boosting Instagram Stories | |
| Your Strengths and Weaknesses | |
| Docs Metrics | |
| Time Series Discrepancies | |
| WhatsApp Metrics | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Cumulative Distribution | |
| Rolling Bank Transactions | |
| 500 Cards | |
| Subscription Overlap | |
| Employee Salaries | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| Prime to N | |
| Comments Histogram | |
| Closest SAT Scores | |
| Button AB Test | |
| Size of Joins | |
| Top Three Salaries | |
| Total Spent on Products | |
| P-value to a Layman | |
| Monthly Customer Report | |
| Paired Products | |
| Top 3 Users | |
| Google Maps Improvement | |
| Third Purchase | |
| Slacking Employees Salaries | |
| Experiment Validity |
Synthesized from candidate reports. Individual experiences may vary.
The process appears to start with a recruiter conversation to align on the role, though the candidate noted the description of the position could shift from what was originally posted. This stage may also cover basic logistics and compensation, but the experience suggested the salary range was not always ready at this point.
Candidates complete an asynchronous HireVue assessment with recorded video responses and typed written answers. The questions are fairly high-level and focus on experience working in a metrics-driven environment, serving more as an initial filter than a deep interview.
A Zoom interview with two hiring managers focuses on the candidate’s background, understanding of the job requirements, and basic knowledge of Thomson Reuters as a company. Although scheduled for 30 minutes, this conversation may be shorter and remains relatively broad rather than technical.
The final round described was an in-person interview at the office with the person the candidate would potentially work with. This stage was conversational and centered on experience and role fit, with no heavy technical testing reported.
