
Thoughtworks Management Consultant Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 22 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Thoughtworks.
Strategy Consultant
It was great working as a summer strategy consultant. I got great exposure to BFSI, healthcare & Telco sectors. Learned about strategy frameworks and their application in the business world. Brainstorming sessions gave a lot of exposure
- Case Study - Estimate the demand for pizza ordered through an app in a day.
- Estimate the demand for EV motorcycles?
Associate Consultant
There was an initial info session which was a video call with a bunch of other candidates and two recruiters where they answered questions. Then there was a questionnaire that was like 3 pages long to check for culture fit. After that, a simple coding exercise in Java where you had two options to pick from. The last round was a video call interview with a recruiter, less than 30 minutes. I only got to this fourth round (the video interview). I was really interested in the AC program and thought the company was awesome. But dealing with the recruiting process, I got a bad impression of the company's operations and HR team. They were pretty unorganized, not doing what they said they would, within the time they said. For instance, I had to ask them to send me the questionnaire, and I had to ask twice. They also stopped talking to me for 6 weeks after the video interview even though they said they'd get back to me in a week, and I had sent them two follow-up emails. All in all, it was an unorganized and unprofessional process.
- Regarding the coding exercise, can you explain your approach?
Associate Consultant
So I interviewed with ThoughtWorks and it was pretty much like everyone says. I first met a recruiter at a job fair. About 4 weeks later, they sent me a questionnaire and a coding challenge, I had 3 days to do it. The questionnaire was really long, asking stuff like what I'd change if I were president and when I got into tech. The coding challenge was the usual Sales Tax/Rail path/Mars Rover problems (pro tip: add unit tests if you can, they really like TDD). About 1 1/2 weeks later, the recruiter called for a phone interview. It was mostly behavioral questions like convincing someone or talking about my resume, plus questions about ThoughtWorks' "three pillars" and social justice issues. They also asked about salary, office preference, and other companies I was applying to. I managed to avoid ranking the companies. Since I had another offer deadline, they moved fast and set up an onsite interview within a week. The onsite was also as expected. My advice is to have your 5 min STEM presentation topic ready and be up-to-date on current events/social causes. Also, brush up on OOP, I kind of struggled with the terminology there. The interview was on Thursday/Friday, and the recruiter called Monday to say no offer. He gave detailed feedback, mentioned the team was split, and encouraged me to reapply in 4-6 months after working on my weak spots. Just remember they're a consulting company, so even though they're casual and friendly, maintain professionalism.
- Can you share an instance where you experienced failure?
- What's a piece of criticism you found particularly difficult to accept?
Thoughtworks Management Consultant Interview Questions
Quoted word for word from Thoughtworks interview reports.
“Estimate the demand for EV motorcycles?”
Read reports →“How would you design a tic-tac-toe game so the computer can't lose?”
Read reports →“What distinguishes a tree, a linked list, and an array?”
Read reports →“Where do the poor and oppressed people in your city live, and who are they?”
Read reports →“Could you code a calendar in python?”
Read report →“Can you name individuals or groups you believe are subjected to oppression?”
Read report →“Who do you consider oppressed?”
Read report →“Name five distinct things that help a team succeed and five distinct things that cause it to fail.”
Read report →“Could you design a program that takes directional input and tells you where those inputs would lead you on an n x m grid?”
Read report →Formats, difficulty and experience
Across all 22 Thoughtworks interview reports.