# Software Engineer
**Role:** Software Engineer · **Level:** TR6
**Company:** [Thomson Reuters](https://scaleengineer.com/companies/thomson-reuters)
**Difficulty:** Medium to Hard
**Salary:** US$120000 - US$160000
**Experience:** 4 - 7
**Timeline:** ~14 days
This interview process is for a Software Engineer (TR6 level) at Thomson Reuters. It assesses technical skills, problem-solving abilities, and cultural fit.
Canonical: https://scaleengineer.com/interviews/thomson-reuters/tr6-software-engineer
---
## Overall evaluation

- Technical Skills (DSA)
- Technical Skills (System Design)
- Behavioral and Cultural Fit
- Leadership and Impact

## Questions asked

- Given an array of integers, find the contiguous subarray with the largest sum.
- Design a URL shortening service like bit.ly.
- Explain the difference between a process and a thread.
- How would you design a system to handle millions of concurrent users on a social media platform?
- Tell me about a time you had to deal with ambiguity in a project.
- What are the trade-offs between using a relational database and a NoSQL database?
- Implement a function to reverse a linked list.
- Describe a situation where you had to influence a team's technical direction.
- How do you stay updated with new technologies?
- What are your strengths and weaknesses as a software engineer?

## Preparation tips

### lists

- Review core Computer Science fundamentals: Data Structures (Arrays, Linked Lists, Trees, Graphs, Hash Tables) and Algorithms (Sorting, Searching, Dynamic Programming, Graph Traversal).
- Practice coding problems on platforms like LeetCode, HackerRank, or AlgoExpert, focusing on medium to hard difficulty.
- Study system design concepts: Scalability, Availability, Reliability, Consistency, Load Balancing, Caching, Databases (SQL/NoSQL), Message Queues, APIs.
- Understand common distributed systems patterns and challenges.
- Prepare for behavioral questions by using the STAR method (Situation, Task, Action, Result) to structure your answers.
- Research Thomson Reuters' products, values, and recent news to tailor your responses.
- Be ready to discuss your past projects in detail, highlighting your contributions and technical decisions.
- Practice explaining complex technical concepts clearly and concisely.

### studyPlan

- {"title":"Data Structures and Algorithms","longDescription":"Weeks 1-2: Focus on Data Structures and Algorithms. Cover arrays, linked lists, stacks, queues, trees (binary, BST, AVL), heaps, hash tables, graphs. Practice algorithms like sorting (quicksort, mergesort), searching (binary search), dynamic programming, recursion, and graph traversal (BFS, DFS). Aim for 2-3 coding problems per day.","shortDescription":"Weeks 1-2: DSA fundamentals and practice (2-3 problems/day)."}
- {"title":"System Design","longDescription":"Weeks 3-4: Dive into System Design. Study concepts like designing for scale, load balancing, caching strategies, database choices (SQL vs. NoSQL), message queues, API design (REST, gRPC), and microservices architecture. Work through common system design case studies.","shortDescription":"Weeks 3-4: System Design concepts and case studies."}
- {"title":"Behavioral and Leadership","longDescription":"Week 5: Prepare for Behavioral and Leadership questions. Reflect on your past experiences and prepare STAR method answers for common questions related to teamwork, conflict resolution, leadership, problem-solving, and failures. Research Thomson Reuters' culture and values.","shortDescription":"Week 5: Behavioral questions (STAR method) and company research."}
- {"title":"Mock Interviews and Final Review","longDescription":"Week 6: Mock Interviews and Review. Conduct mock interviews focusing on both technical and behavioral aspects. Review weak areas identified during practice and mock interviews. Ensure you can articulate your thought process clearly.","shortDescription":"Week 6: Mock interviews and final review."}

## Location differences

- {"location":"New York","differences":{"tips":["Emphasize experience with large-scale distributed systems.","Be prepared to discuss trade-offs in architectural decisions.","Highlight any experience with high-frequency trading systems or financial data processing.","Showcase leadership potential and ability to guide technical discussions."],"interviewFocus":["System Design for scalability and fault tolerance","Deep dive into distributed systems concepts","Experience with cloud platforms (AWS, Azure, GCP)","Leadership and mentoring capabilities"],"commonQuestions":["How would you design a system to handle real-time stock price updates for a global audience?","Describe a complex technical challenge you faced and how you overcame it.","What are your thoughts on microservices vs. monolithic architectures?","How do you ensure code quality and maintainability in a large project?","Tell me about a time you had to mentor a junior engineer."]}}
- {"location":"London","differences":{"tips":["Be ready to whiteboard complex algorithms.","Demonstrate a strong understanding of SQL and NoSQL databases.","Highlight experience with RESTful API design.","Showcase your ability to work effectively in a team environment."],"interviewFocus":["Data Structures and Algorithms efficiency","Database design and optimization","API design and development","Collaboration and teamwork"],"commonQuestions":["Design a caching strategy for a high-traffic e-commerce website.","Explain the CAP theorem and its implications.","How would you optimize a database query that is performing poorly?","Describe your experience with CI/CD pipelines.","Tell me about a project where you had to work with a cross-functional team."]}}
- {"location":"Bangalore","differences":{"tips":["Prepare to discuss your understanding of ML algorithms and their applications.","Showcase experience with big data processing tools.","Be ready to articulate your thought process for solving problems.","Demonstrate maturity in handling disagreements."],"interviewFocus":["Machine Learning and Data Science concepts","Big Data technologies (Spark, Hadoop)","Problem-solving and analytical skills","Communication and conflict resolution"],"commonQuestions":["How would you design a recommendation engine for a streaming service?","Discuss your experience with machine learning frameworks.","What are the challenges of working with large datasets?","How do you approach debugging complex issues?","Tell me about a time you disagreed with a technical decision and how you handled it."]}}

## Round 1: Technical Round 1: Coding
**Type:** Data Structures and Algorithms Interview · **Difficulty:** Medium · **Duration:** 45 min
Assess core programming skills with coding challenges.
This round focuses on your fundamental programming skills. You will be asked to solve 1-2 coding problems, typically involving data structures and algorithms. The interviewer will assess your ability to write clean, efficient, and correct code, as well as your problem-solving methodology. Expect to explain your thought process and discuss trade-offs.
**Interviewers look for:** Strong grasp of DSA; Ability to translate requirements into working code; Logical thinking and systematic approach
**Evaluation criteria:** Correctness of the solution; Efficiency (Time and Space Complexity); Code clarity and style; Problem-solving approach
**Common rejection reasons:** Inability to solve coding problems efficiently.; Poor understanding of fundamental data structures and algorithms.; Code that is not clean, readable, or maintainable.; Not asking clarifying questions.
## Questions

- Given a binary tree, find its inorder traversal.
- Find the kth smallest element in a sorted matrix.

## Preparation tips

- Practice coding problems on platforms like LeetCode.
- Understand time and space complexity analysis (Big O notation).
- Be prepared to explain your code and justify your choices.
- Ask clarifying questions about the problem statement.

## Round 2: Technical Round 2: System Design
**Type:** System Design Interview · **Difficulty:** Hard · **Duration:** 60 min
Assess ability to design scalable and robust systems.
This round evaluates your ability to design scalable and robust systems. You'll be given an open-ended problem (e.g., design Twitter's feed, design a URL shortener) and expected to break it down, identify requirements, propose an architecture, and discuss trade-offs. Focus on components like databases, caching, load balancing, and APIs.
**Interviewers look for:** Ability to design complex systems; Understanding of distributed systems concepts; Pragmatic approach to trade-offs; Experience with relevant technologies
**Evaluation criteria:** Scalability of the design; Availability and reliability considerations; Choice of technologies and justification; Trade-off analysis; Clarity of explanation
**Common rejection reasons:** Lack of understanding of system design principles.; Inability to handle scalability and performance requirements.; Poorly thought-out architectural choices.; Failure to consider edge cases and failure modes.
## Questions

- Design a system like Google Maps.
- Design an API rate limiter.

## Preparation tips

- Study common system design patterns.
- Practice designing various popular applications.
- Understand concepts like CAP theorem, eventual consistency, and ACID properties.
- Be prepared to draw diagrams and explain your design choices.

## Round 3: Behavioral and Managerial Round
**Type:** Behavioral Interview · **Difficulty:** Medium · **Duration:** 45 min
Assess behavioral competencies and cultural fit.
This round focuses on your behavioral competencies and how you handle various workplace situations. You'll be asked questions about your past experiences, teamwork, conflict resolution, leadership, and how you align with the company culture. Use the STAR method to provide structured and specific answers.
**Interviewers look for:** Good communication and interpersonal skills; Evidence of teamwork and collaboration; Ability to learn and adapt; Alignment with Thomson Reuters' values
**Evaluation criteria:** Communication skills; Teamwork and collaboration; Problem-solving approach in past experiences; Cultural fit; Self-awareness
**Common rejection reasons:** Lack of clear communication.; Inability to provide specific examples using STAR method.; Appearing arrogant or uncooperative.; Not demonstrating alignment with company values.; Lack of enthusiasm or interest.
## Questions

- Tell me about a time you failed and what you learned from it.
- Describe a situation where you had to work with a difficult colleague.
- How do you prioritize your work when you have multiple competing deadlines?

## Preparation tips

- Prepare examples for common behavioral questions using the STAR method.
- Research Thomson Reuters' values and culture.
- Be honest and authentic in your responses.
- Show enthusiasm for the role and the company.

## Round 4: HR Round
**Type:** HR/Offer Discussion · **Difficulty:** Easy · **Duration:** 15 min
Discuss offer details, compensation, and answer final questions.
This is typically the final stage where HR discusses logistics, compensation, benefits, and answers any remaining questions you might have about the offer or the company. It's also an opportunity for them to gauge your overall interest and fit.
**Interviewers look for:** Enthusiasm for the role and company; Clear understanding of the role and expectations; Professionalism and good communication
**Evaluation criteria:** Candidate's interest and enthusiasm; Alignment of expectations (role, team, career); Professionalism during discussion
**Common rejection reasons:** Lack of clarity on career goals.; Unrealistic salary expectations.; Poor communication during the offer negotiation phase.; Not asking relevant questions about the role or team.
## Preparation tips

- Prepare questions about compensation, benefits, team structure, and career growth.
- Be ready to discuss your salary expectations.
- Reiterate your interest in the role and the company.