Thomson Reuters software engineer candidates report an online assessment or screen, technical conversations built around their resume and projects, and a manager or HR conversation. Fundamentals matter more than hard algorithms.
$113K
Avg. Base Comp
$135K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates who describe the Thomson Reuters software engineer interview most often say it is built around your own resume and project work more than around hard algorithm puzzles. One candidate was questioned in detail about XSLT work they had listed, and another was asked to walk through internships and every tool on the resume. Be ready to explain and defend anything you list, including how you actually used each technology.
The technical content reported is fundamentals-heavy but varies by interviewer. Accounts mention an online assessment (one with three coding problems, another with about 20 questions on development-related acronyms), a paired coding call, and short code-inspection snippets. Conceptual topics include OOP, DBMS, SQL, serialization, exception hierarchy, Git, and a case-style question about designing a search and lookup API. One candidate recalled a recursive tree traversal problem, and another was asked about converting a stack to a queue.
Behavioral and fit conversations appear in nearly every account, usually with a hiring or engineering manager and sometimes HR. Expect to explain why Thomson Reuters and why you fit the role. Reported formats differ, so confirm each round with your recruiter. One candidate said the panel can include people from development, DevOps, QA, and business analysis, and another said extra rounds were added after they expected to be finished.
Timelines are not consistently reported. One candidate said the process dragged on longer than expected, and another found the interview count grew beyond what HR first described. Plan for variation, and keep a clear project story and fundamentals review ready throughout.
Synthesized from 20 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.
The process spanned about a month and a half from application to final decision. I started with a phone screening, which felt like a standard conversation covering my background and relevant experience. The second round was a whole-day assessment—the most intensive part. This included both an online coding component and technical questions grounded in Python fundamentals. I remember working through a linked list reversal problem where I had to explain time and space complexity, and there were some data structure and algorithm questions testing basic problem-solving ability. The third round was behavioral, where they asked about my internship and school organization experiences to get a sense of how I worked in team settings. The final round was with the potential manager, and it felt more like a conversation about fit and what I'd bring to the role. Throughout the process, the questions really zeroed in on practical knowledge relevant to their tech stack rather than abstract algorithmic trivia. Nothing felt trick-heavy; the difficulty was moderate but consistent. The whole experience was smooth and well-organized, which made the multi-week timeline feel manageable.
Prep tip from this candidate
Focus on Python DSA fundamentals—especially linked lists and tree traversals with complexity analysis—and prepare concrete examples from your internships and school projects to illustrate teamwork and problem-solving. The emphasis is on practical knowledge tied to their stack, not memorized LeetCode solutions.
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 | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Subscription Overlap | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| String Shift | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Google Maps Improvement | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Sum to N |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial call with HR or a recruiter covering your background, interest in the role, and sometimes compensation expectations. Have a concise account of your experience and a specific reason for choosing Thomson Reuters.
Several candidates describe an online assessment. Reports range from three coding problems to about 20 questions on development-related acronyms, and another candidate completed HackerRank-style exercises on Git, JavaScript and React. Questions are described as fundamentals-focused, and the format may vary by team.
Technical rounds reportedly focus on your resume projects and core concepts such as OOP, DBMS, SQL, serialization, Git, and data structures. Some candidates describe a paired coding problem, short code-inspection snippets, or a case-style API design question. Questions often depend on the interviewer's area, so expect variation.
Candidates typically describe a conversation with a hiring or engineering manager covering strengths, weaknesses, teamwork, and why you want the role. One candidate says the panel can include developers and people from other roles. Prepare examples of collaboration and be ready to ask about the team's day-to-day work.
Some candidates describe a brief HR conversation near the end to confirm details before an offer, while others heard back after the manager stage. Reported outcomes are mixed, and one candidate said the process dragged on longer than expected. Ask your recruiter about expected timing.
