Thomson Reuters Software Engineer candidates report assessments or coding exercises, fundamentals-focused technical discussions, and resume- or scenario-based manager conversations.
$117K
Avg. Base Comp
$141K
Avg. Total Comp
4-5 rounds
Typical Rounds
2-5 weeks
Process Length
Thomson Reuters Software Engineer interviews reported here lean toward practical engineering fundamentals and clear discussion of prior work, although the exact format differs by candidate. One candidate began with an online assessment on development acronyms, then discussed DBMS, OOP, cloud/backend concepts, internships, and the tools listed on their resume. Another completed basic HackerRank-style work in Git, JavaScript, and React, plus SQL and a case discussion about building a search-and-lookup API.
A separate account describes three coding problems in an assessment followed by paired coding, with questions on choosing a data structure for sortable inserts, converting a stack to a queue, and a SQL query. That candidate also encountered OS fundamentals, Git, and AWS CLI. An earlier report included code inspection, a coding/tree-traversal problem, and interviewer-specific questions tied to the candidate's background, such as XSLT and Java backend concepts. Prepare to explain your own projects, internships, and tools with the same precision as a coding answer.
Manager or cultural conversations may cover fit, team experience, strengths and weaknesses, and why Thomson Reuters. One candidate reported being told to expect four conversations but ultimately experiencing four or five as further interviews were added; another described an assessment, technical discussions, and a manager call. The available reports are limited, so use the sequence as preparation context rather than a fixed template.
Synthesized from 6 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 felt pretty structured and professional overall, but it also dragged on longer than I expected and the follow-up wasn’t great. I came in through a staffing agency, and the first step was a call screen that was pretty straightforward. After that, I had a live coding round and then met with a few people in New York, with each meeting lasting about an hour. The technical part was more concept-heavy than I expected, and there were also a couple of coding problems mixed in. One round focused on pure technical knowledge and included two programs, while another was more process-oriented and scenario-based, so it wasn’t just about writing code but also about how I’d handle real work situations. They also spent time on my background and asked me to explain my job experience and what made me a strong candidate, which made the conversations feel more like a mix of technical screening and fit assessment. The interviewers were nice and the atmosphere was calm, so it never felt aggressive or strange, just a bit more formal than a typical startup-style interview. I also got a question around prior knowledge of ONE tools, so there was some stack-specific discussion as well. In the end, I declined the offer, but the process itself was clear enough that I knew what to expect at each stage. My main takeaway is to be ready for a polished, process-driven interview with both technical concepts and practical scenario questions, plus some discussion of your past experience and tools you’ve used.
Prep tip from this candidate
Be ready for a concept-heavy technical round with two coding problems, and practice explaining your past job experience clearly since that came up directly. Also review any ONE tools or similar internal systems you’ve used, because that specific knowledge was tested.
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 | |
| Bagging vs Boosting | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Total Spent on Products | |
| Maximum Profit | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Size of Joins | |
| Top 3 Users | |
| Google Maps Improvement | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Sum to N |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report either an online assessment or practical coding work near the start. Examples include development acronyms, three coding problems, and basic HackerRank-style Git, JavaScript, and React exercises; the exact assessment format varies across accounts.
Technical conversations may combine live or paired coding with questions on data-structure choices, DBMS, OOP, SQL, operating-system fundamentals, and code inspection. Candidates also reported Git, AWS CLI, web applications, and role-relevant backend or cloud topics.
Later conversations were often experience-based. Candidates report questions about internships, projects, tools, teamwork, strengths and weaknesses, why Thomson Reuters, and how they would approach a practical scenario such as a search-and-lookup API.
