Thomson Reuters

Associate Software Engineer

Software EngineerTR7Medium

This interview process is for an Associate Software Engineer (TR7) role at Thomson Reuters. It is designed to assess a candidate's foundational software engineering skills, problem-solving abilities, and cultural fit within the company.

Rounds

3

Timeline

~14 days

Experience

0 - 2 yrs

Salary Range

US$65000 - US$85000

Total Duration

120 min

Overall Evaluation Criteria

Technical Skills

Problem-solving skills
Algorithmic thinking
Data structure knowledge
Coding proficiency
Technical communication

Behavioral and Cultural Fit

Teamwork and collaboration
Communication clarity
Adaptability
Proactiveness
Cultural alignment

Foundational Knowledge

Understanding of software development lifecycle
Familiarity with development tools and methodologies
Ability to learn and apply new concepts

Preparation Tips

1Review fundamental data structures (arrays, linked lists, trees, graphs, hash maps) and algorithms (sorting, searching, recursion, dynamic programming).
2Practice coding problems on platforms like LeetCode, HackerRank, or GeeksforGeeks, focusing on medium-difficulty problems.
3Understand core object-oriented programming (OOP) concepts (encapsulation, inheritance, polymorphism, abstraction).
4Familiarize yourself with common software development methodologies (Agile, Scrum).
5Prepare to discuss your past projects, internships, or academic work in detail, focusing on your contributions and learnings.
6Research Thomson Reuters' products, services, and company culture.
7Practice answering behavioral questions using the STAR method (Situation, Task, Action, Result).
8Be ready to explain your thought process clearly and concisely during technical discussions.

Study Plan

1

Data Structures Fundamentals

Weeks 1-2: Data Structures (Arrays, Linked Lists, Trees) & Complexity Analysis.

Weeks 1-2: Focus on foundational data structures like arrays, linked lists, stacks, queues, and trees. Practice implementing them and solving problems related to their usage. Understand time and space complexity analysis (Big O notation).

2

Algorithm Practice

Weeks 3-4: Algorithms (Sorting, Searching, Recursion, Graph Traversal) & Problem Solving.

Weeks 3-4: Dive into algorithms such as sorting (bubble sort, merge sort, quick sort), searching (binary search), recursion, and basic graph traversal (BFS, DFS). Solve problems that require applying these algorithms.

3

Object-Oriented Programming

Week 5: OOP Concepts & Language Proficiency.

Week 5: Strengthen your understanding of Object-Oriented Programming (OOP) principles and design patterns. Review common programming languages (e.g., Java, Python, C++) and their specific features.

4

Behavioral Preparation & Company Research

Week 6: Behavioral Questions (STAR Method) & Company Research.

Week 6: Prepare for behavioral questions. Think about examples from your experience that demonstrate teamwork, problem-solving, leadership, and adaptability. Practice articulating these using the STAR method. Research Thomson Reuters.

Commonly Asked Questions

Write a function to reverse a linked list.
Explain the difference between a process and a thread.
Describe a situation where you had to deal with a difficult team member.
How would you design a URL shortener service?
What are your strengths and weaknesses?
Tell me about a time you failed and what you learned from it.
Given an array of integers, find the two numbers that add up to a specific target.
What is polymorphism?
How do you stay updated with new technologies?
Why are you interested in Thomson Reuters?

Location-Based Differences

North America

Interview Focus

Adaptability to new technologies and team environments.Understanding of core computer science principles.Communication and collaboration skills.

Common Questions

Tell me about a challenging project you worked on during your internship.

How do you handle conflicting priorities?

Describe a time you had to learn a new technology quickly.

Tips

Highlight any open-source contributions or personal projects.
Be prepared to discuss your learning process.
Emphasize teamwork and communication in your answers.

Europe

Interview Focus

Depth of understanding in specific programming languages (e.g., Java, Python).Problem-solving approach to technical challenges.Familiarity with software development lifecycle.

Common Questions

Can you explain the concept of polymorphism with a real-world example?

How would you optimize a database query?

Describe your experience with Agile methodologies.

Tips

Brush up on data structures and algorithms.
Be ready to write code on a whiteboard or shared editor.
Understand the company's core products and services.

Asia

Interview Focus

Core programming concepts and best practices.Analytical and debugging skills.Attitude towards learning and self-improvement.

Common Questions

What are the key principles of object-oriented programming?

How do you approach debugging a complex issue?

Tell me about a time you received constructive feedback and how you acted on it.

Tips

Review fundamental programming concepts.
Practice explaining your thought process clearly.
Show enthusiasm for continuous learning.

Process Timeline

1
Data Structures and Algorithms Assessment45m
2
Behavioral and Situational Assessment30m
3
System Design Fundamentals45m

Interview Rounds

3-step process with detailed breakdown for each round

1

Data Structures and Algorithms Assessment

Coding challenges to assess problem-solving and algorithmic skills.

Technical Interview (Data Structures & Algorithms)Medium
45 minSoftware Engineer

This round focuses on assessing your core technical skills through coding challenges. You will be asked to solve one or two problems related to data structures and algorithms. The interviewer will evaluate your approach to problem-solving, your ability to write clean and efficient code, and your understanding of time and space complexity. You'll typically use a shared coding environment or whiteboard.

What Interviewers Look For

Logical thinkingAbility to translate requirements into codeUnderstanding of fundamental data structures and algorithmsClean and maintainable code

Evaluation Criteria

Correctness of the solution
Efficiency of the solution (time and space complexity)
Code clarity and readability
Problem-solving approach
Ability to communicate technical ideas

Questions Asked

Given an array of integers, return indices of the two numbers such that they add up to a specific target.

ArrayHash TableTwo Pointers

Implement a function to check if a binary tree is a valid Binary Search Tree (BST).

TreeDepth-First SearchBinary Search Tree

Preparation Tips

1Practice coding problems regularly.
2Focus on explaining your thought process as you code.
3Be prepared to discuss trade-offs between different solutions.
4Test your code thoroughly, including edge cases.

Common Reasons for Rejection

Inability to articulate thought process.
Incorrect or inefficient algorithmic solutions.
Poor coding practices (e.g., lack of comments, poor variable naming).
Failure to handle edge cases.
2

Behavioral and Situational Assessment

Assessing soft skills, teamwork, and cultural fit.

Behavioral InterviewMedium
30 minHiring Manager or Senior Team Member

This round focuses on your behavioral and situational responses. You'll be asked questions about your past experiences, how you handle teamwork, challenges, and learning. The goal is to understand your personality, work ethic, and how well you would integrate into the team and company culture. Use the STAR method to structure your answers.

What Interviewers Look For

How you handle challenges and conflicts.Your ability to work in a team.Your learning attitude and adaptability.Your passion for software development and the company.

Evaluation Criteria

Communication skills
Teamwork and collaboration
Problem-solving approach in non-technical scenarios
Motivation and enthusiasm
Cultural alignment with Thomson Reuters values

Questions Asked

Tell me about a time you faced a significant challenge in a project and how you overcame it.

BehavioralProblem Solving

Describe a situation where you had to collaborate with someone with a different working style. How did you manage it?

BehavioralTeamwork

What are your career aspirations for the next 3-5 years?

BehavioralCareer Goals

Preparation Tips

1Prepare specific examples using the STAR method.
2Be honest and authentic in your responses.
3Show enthusiasm for the role and the company.
4Ask thoughtful questions about the team and work environment.

Common Reasons for Rejection

Lack of clarity in explaining past experiences.
Inability to provide specific examples.
Appearing unenthusiastic or not a good cultural fit.
Not demonstrating teamwork or collaboration skills.
3

System Design Fundamentals

Assessing ability to design scalable software systems.

System Design InterviewMedium
45 minSenior Software Engineer or Architect

This round, often called an Architecture or System Design round, is more common for mid-level roles but can be introduced for strong junior candidates. It assesses your ability to think about how software systems are built at a higher level. You might be asked to design a simplified version of a common application (e.g., a URL shortener, a social media feed). Focus on requirements gathering, component design, data modeling, and identifying potential bottlenecks.

What Interviewers Look For

Ability to think about larger systems.Understanding of scalability, reliability, and performance.Pragmatic approach to design.Ability to break down complex problems.

Evaluation Criteria

Understanding of system design concepts
Ability to design scalable and reliable systems
Consideration of trade-offs
Communication of design decisions
Problem decomposition

Questions Asked

Design a URL shortening service like bit.ly.

System DesignScalabilityDatabase Design

How would you design a system to count the number of unique visitors to a website?

System DesignScalabilityData Processing

Preparation Tips

1Study common system design patterns and concepts.
2Practice designing various types of systems.
3Focus on clarifying requirements and making reasonable assumptions.
4Discuss trade-offs for different design choices.

Common Reasons for Rejection

Lack of understanding of basic system design principles.
Inability to scale solutions.
Poor communication of design choices.
Not considering trade-offs effectively.

Commonly Asked DSA Questions

Frequently asked coding questions at Thomson Reuters

View all
Roman to IntegerEASYLongest Substring Of All Vowels in OrderMEDIUMMinimum Time to Type Word Using Special TypewriterEASY