Thomson Reuters ONESOURCE India Engineering Manager Interview: Rounds, Questions and Preparation

What the job involves

An Engineering Manager at a global tech product company in India, such as a tax and accounting software firm, leads a team of 5 to 10 software engineers to deliver reliable, scalable features. Day to day, they balance people management, technical design reviews, sprint planning, and cross-functional coordination with product and QA teams. Freshers usually enter as Associate Software Engineers or Graduate Trainees and grow into this role after several years, so preparation should focus on foundational engineering and early leadership behaviours.

Role and Technical Knowledge

1. 1

   What does an Engineering Manager do in a product company that builds tax and accounting software?

   A strong answer covers leading a team, owning delivery of features, conducting code and design reviews, and collaborating with product managers and QA. Mention balancing technical depth with people growth.

2. 2

   How would you explain the difference between a monolithic architecture and a microservices architecture to a new intern?

   Use simple analogies: a monolith is one large application, while microservices are smaller independent services. Highlight trade-offs in deployment, scaling, and team ownership.

3. 3

   What is the role of a database index, and when would you avoid using one?

   Explain that an index speeds up reads but slows writes and uses extra storage. Avoid indexes on columns with low selectivity or tables with heavy write loads.

4. 4

   How does version control help a team of engineers working on the same codebase?

   Cover branching, merging, pull requests, and conflict resolution. Mention code review and traceability as key benefits for team collaboration.

Practical Scenarios

1. 5

   A critical bug is found in a tax calculation module two days before a release. How would you handle it as a team member?

   Prioritise reproducing the bug, writing a failing test, fixing it, and getting a peer review. Communicate status early to the manager and avoid last-minute risky changes.

2. 6

   You are asked to add a new report feature that depends on data from three different services. How would you approach the design?

   Discuss API contracts, data consistency, error handling, and performance. Mention starting with a simple synchronous approach and considering async or caching if load grows.

3. 7

   Your team's build pipeline is taking 40 minutes and slowing down everyone. What steps would you take?

   Suggest profiling the pipeline, parallelising independent steps, caching dependencies, and running only relevant tests per change. Emphasise measuring improvement.

4. 8

   A product manager asks for a feature that you think will add technical debt. How do you respond?

   Acknowledge the business need, explain the trade-offs clearly, and propose a phased approach or a follow-up refactor. Show willingness to collaborate, not just say no.

Behavioural and Teamwork

1. 9

   Tell me about a time you had to learn a new technology quickly for a college project or internship.

   Use the STAR method: describe the situation, the technology, your learning approach, and the outcome. Highlight resourcefulness and persistence.

2. 10

   Describe a situation where you disagreed with a teammate on a technical approach. How did you resolve it?

   Focus on listening, presenting data or prototypes, and reaching a consensus. Show respect and a willingness to change your mind if the evidence supports it.

3. 11

   How do you prioritise tasks when you have multiple deadlines in a short period?

   Mention assessing impact and urgency, communicating with stakeholders, and breaking work into smaller chunks. Give a concrete example from academics or a project.

4. 12

   Give an example of a time you took ownership of a mistake. What did you learn?

   Be honest about the mistake, explain how you fixed it, and state the lesson learned. Show accountability and a growth mindset.

HR and Company Fit

1. 13

   Why do you want to work for a global product company in the tax and accounting domain?

   Connect your interest in building reliable, high-impact software with the domain's need for accuracy and scale. Mention willingness to learn domain concepts.

2. 14

   Where do you see yourself in three years as an engineer?

   Show a path from strong individual contributor to mentoring or leading small initiatives. Align your growth with the company's engineering career ladder.

3. 15

   How do you handle feedback that you disagree with?

   Explain that you listen fully, ask clarifying questions, and reflect before responding. Give an example where feedback improved your work.

4. 16

   What do you know about our engineering culture or products, and why does it appeal to you?

   Research the company's tech stack, values, and any public engineering blogs. Connect specific points to your own interests and working style.