Thoughtworks - interview guide

Thoughtworks interview questions - a complete guide

Thoughtworks' most distinctive round is code pairing - where your clean code, refactoring and tests count for more than how hard the problem is.

Language:EnglishHinglish

About Thoughtworks

Thoughtworks is a global technology consultancy that builds software for clients, known for agile, TDD and clean code. In India it has offices in cities such as Bengaluru, Pune, Chennai, Gurugram, Hyderabad and Coimbatore. Freshers usually join as Graduate Developers.

This guide covers 13 Thoughtworks interview questions with answers - what each question checks and how to answer it - plus the Thoughtworks interview process, round by round, a 7-day preparation plan for freshers, tips and the mistakes to avoid.

Thoughtworks hiring process

  1. Online coding test

    Reported: about 4 questions (easy-medium) on HackerRank, around 75 minutes.

  2. Code pairing

    The problem is shared in advance; you extend the code, refactor and write tests together with the interviewer.

  3. Technical interview

    Projects, OOP and problem solving.

  4. Leadership / culture and HR

    Values, your views on social issues, and fit.

Thoughtworks does not publish its India fresher interview process in detail (as of our check). This is based on candidate reports - many of them for experienced roles, so the fresher process can differ. Confirm with the recruiter.

Sources (checked 16 October 2026): Thoughtworks Careers India. Hiring processes change - read the official notice before you apply.

Thoughtworks interview questions and answers

Code pairing

According to reports, SOLID and clean design matter more here than how hard the problem is.

  1. 1.How would you spot code smells in the given legacy code?

    What they're checking
    The core of code pairing.
    How to answer
    Very long methods, duplicated code, magic numbers, one class that does everything, bad names, and deeply nested if-else. For each smell, say how you would fix it.

  2. 2.Why write tests before refactoring?

    What they're checking
    Safe refactoring.
    How to answer
    Tests show the behaviour is the same after the change - a safety net. Without tests, refactoring runs on guesswork.

  3. 3.Explain TDD's red-green-refactor cycle.

    What they're checking
    The Thoughtworks way.
    How to answer
    Red: a failing test first. Green: just enough code to pass. Refactor: clean the code while keeping the tests green. In small steps.

  4. 4.Explain the Open/Closed principle with a discount calculator.

    What they're checking
    SOLID in practice.
    How to answer
    Instead of growing an if-else for every new discount, a DiscountRule interface and a class per discount. A new discount = a new class; old code isn't touched.

  5. 5.A class creates orders, sends emails and generates reports - how would you break it up?

    What they're checking
    Single Responsibility.
    How to answer
    Separate OrderService, EmailNotifier and ReportGenerator; OrderService uses the others through interfaces. Each class has one reason to change.

  6. 6.What do the driver and navigator do in pair programming?

    What they're checking
    The round itself is pair programming.
    How to answer
    The driver writes code at the keyboard; the navigator watches the big picture, mistakes and the next step. Keep talking, switch roles, and listen to your partner.

Technical and design

  1. 7.Move a rover on a grid with L, R, M commands - give its final position and direction.

    What they're checking
    A classic OOP design exercise.
    How to answer
    Separate Position, Direction (an enum with left()/right()), Rover (move, turn) and a command parser. Ask what happens at the grid's edge. Tests for each command.

  2. 8.Fit conference talks into morning (3 hours) and afternoon (4 hours) sessions.

    What they're checking
    Modelling a problem.
    How to answer
    Talk, Session (limit) and Track classes. Sort talks longest to shortest and fit them greedily; if they don't fit, the next track. Keep parsing and scheduling separate.

  3. 9.What is the difference between a mock and a stub?

    What they're checking
    Testing basics.
    How to answer
    A stub just returns fixed answers (checking state). A mock also checks how it was called (checking behaviour).

  4. 10.What is continuous integration and why does it matter?

    What they're checking
    Agile practices.
    How to answer
    Every developer merges into the main code several times a day, with an automatic build + tests each time - mistakes are caught early.

Culture and HR

  1. 11.What is your view on diversity and inclusion in the technology industry?

    What they're checking
    Reports mention conversations on social issues.
    How to answer
    Your honest view, an example (from college or a team), and what you do or would do. No memorised answer - reports also say 'be honest'.

  2. 12.When did you change your code or work after feedback?

    What they're checking
    A learning attitude.
    How to answer
    What the feedback was, how it felt at first, what you changed and the result.

  3. 13.Why Thoughtworks?

    What they're checking
    Motivation.
    How to answer
    Something you like such as clean code, TDD, pair programming or Thoughtworks' Technology Radar - specific.

7-day preparation plan for the Thoughtworks interview

  1. Day 1: OOP and SOLID - a small code example for each principle.
  2. Day 2: Refactoring - code smells and their fixes.
  3. Day 3: Unit testing and TDD (JUnit/pytest) - a small kata.
  4. Day 4: Design exercises like the rover/conference problems.
  5. Day 5: Easy-medium DSA - six problems, timed.
  6. Day 6: A pair programming mock with a friend.
  7. Day 7: Culture and HR stories.

Preparation tips

  • Practise SOLID, refactoring and unit tests for code pairing.
  • If you get the problem in advance, clone the repo, run it and understand it.
  • Keep talking while pairing - tell your partner what you are thinking.
  • Be honest in the culture round; memorised answers get caught.

Mistakes to avoid

  • Writing code silently while pairing.
  • Refactoring without tests.
  • Ruining the design while trying to show off a hard algorithm.

Frequently asked questions

What is the Thoughtworks code pairing round?

Working on a problem together with the interviewer - refactoring, new features and tests. According to reports, the problem is sometimes shared in advance.

What is in the Thoughtworks online test?

Reports mention about 4 easy-medium coding questions on HackerRank.

Which role do freshers join at Thoughtworks?

Commonly as Graduate/Application Developers.

What is asked in the Thoughtworks culture round?

Your views on values, teamwork and social issues - reports advise answering honestly.

Similar companies - IT services

More company guides

Read next

On a live call, Cuelyte AI hears questions like these and has an answer ready in about a second, built from your resume and notes. Coding interviews: how Cuelyte AI helps

Ready for your Thoughtworks interview?

Practise these questions with Cuelyte AI: add your resume, type a question and get a clear answer in your own words - in English, Hindi or Hinglish. Free to start.

Start free - no card neededSee pricing