{"id":1975,"date":"2026-07-20T10:08:24","date_gmt":"2026-07-20T04:38:24","guid":{"rendered":"https:\/\/lastroundai.com\/blog\/?post_type=iq&p=1975"},"modified":"2026-07-20T10:26:52","modified_gmt":"2026-07-20T04:56:52","slug":"thoughtworks","status":"publish","type":"iq","link":"https:\/\/lastroundai.com\/interview-questions\/thoughtworks","title":{"rendered":"ThoughtWorks Interview Questions (2026), Real, With Answers"},"content":{"rendered":"

A candidate who’d cleared four rounds at a big product company in six weeks once told me the ThoughtWorks loop was the first one that made him nervous about a laptop he never had to touch alone. There’s no algorithm quiz on a shared doc. Instead there’s a real editor, and a consultant sitting next to him for close to two hours asking him to write tests first and explain every decision out loud as he types. ThoughtWorks describes its own process as “collaborative” on its careers site, built around a recruiter conversation, a technical stage that can include pair programming, case studies, and design challenges, and a separate conversation about leadership and culture fit (ThoughtWorks Careers<\/a>). For entry-level graduate hires through the STEP program, that technical stage is preceded by an aptitude MCQ round and a shorter phone screen before the onsite.<\/p>\n

Candidates on Indeed rate the overall difficulty around 6 out of 10 and the timeline close to a month end to end, with a chunk reporting it stretches past that (Indeed, ThoughtWorks interview reviews<\/a>). What makes the loop distinct isn’t difficulty in the LeetCode sense. It’s that the pairing round splits into two separate sessions, often with two different consultants, specifically so nobody’s day gets defined by one person’s read of a candidate. One session usually leans toward a coding kata done test-first; the other leans toward reading and improving code that’s already there, closer to what a real engagement with a client looks like in week one.<\/p>\n

This page collects the actual questions candidates report being asked across that loop: the MCQ-style aptitude questions from the graduate screen, DSA problems from technical phone screens, the kata-style pairing problems ThoughtWorks is known for (Bowling Game, Mars Rover, Conference Track Scheduler, and the String Calculator kata originated by Roy Osherove and widely used across TDD-focused pairing rounds, per Coding Dojo’s kata catalog<\/a>), CS fundamentals, low-level design prompts, and the values-driven behavioral questions the culture round is known for. Every question below is one you could actually be asked out loud. None of them are questions about the format of the interview itself.<\/p>\n

50<\/span>Questions<\/span><\/div>
4<\/span>Rounds<\/span><\/div>
Pair Programming<\/span>Format<\/span><\/div>
~1 Month<\/span>Timeline<\/span><\/div><\/div>\n

Online assessment: aptitude and SQL screen<\/h2>\n

Graduate and campus hires usually see this first at ThoughtWorks, before any human enters the loop. It’s short, timed, and closer to a logic test than a programming exam.<\/p>\n

<\/span>Easy questions<\/h2>19<\/span><\/div>
<\/div><\/div>\n