
Thoughtworks Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 607 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Thoughtworks.
Software Engineer
I went through a really long and tiring hiring process with this company. It had five interviews and included both technical and behavioral parts. I was told I passed everything. But instead of getting an offer, they said they couldn't hire me right now and that I should wait for future jobs for up to a year. They said I might be able to continue the process later without starting over. This seems really dishonest and a waste of candidates' time and effort. If they don't have a job or money to hire, they should say so before making people do five interviews. Calling it an 'approval' without an offer just keeps candidates waiting while the company does nothing. People spend weeks getting ready, using emotional energy, and giving up their time, only to get nothing but vague promises. Companies should only do full interviews when they're actually ready to hire. Anything else just makes people expect things and shows they don't respect professionals. I wouldn't suggest this hiring process to anyone unless the company is more upfront and stops treating candidates like a backup list with no real commitment.
- Can you tell me about your past experiences?
Lead Developer
The process started with an HR call, followed by a technical stage with a programming test during the interview. Then there was a cultural stage, but surprisingly, another cultural stage happened afterwards. Both cultural stages had similar questions, just delivered by different people. While leadership (the role's focus) was mentioned briefly, the second cultural stage focused more on accessibility. I felt ignored by the process owner, as my emails with questions went unanswered. After the second cultural stage, I was told I didn't pass, with generic feedback that just dismissed the process. I had to chase them for more details.
- Can you share an example where you believe technology hindered or failed?
Software Engineer
Had a code pairing round focused on TDD, maintainability, and reusability. Had to write tests first and structure code for clarity. They evaluated problem-solving, refactoring, and collaboration. Then a technical discussion round where we did a deep dive into my projects and decision-making. They asked language-specific questions like WSGI vs. ASGI. Assessed system design, trade-offs, and optimization. Finally, a cultural fit round focused on teamwork, adaptability, and values alignment. Included behavioral questions based on real-world scenarios. Evaluated communication skills and collaboration mindset.
- What separates WSGI from ASGI?
- How do you go about optimizing memory usage in Python?
- What does monkey patching in Python entail?
Thoughtworks Software Engineer Interview Questions
Quoted word for word from Thoughtworks interview reports.
“Given a list of n numbers (a1, a2, a3, ..., an), find the pairwise XOR of these numbers.”
Read reports →“What is the Global Interpreter Lock (GIL) in Python, and what impact does it have on multi-threading?”
Read reports →“What are the types of indexes for a primary key without a clustered index?”
Read reports →“Regarding the drone flying path problem, on an M*N map, how would you design the path to cover all areas if the drone can only photograph five units?”
Read reports →“Using Pandas, how would you read a CSV file and then do some operations on it?”
Read report →“What are your thoughts on the reservation system in India, whether it's good or bad?”
Read report →“What would be your actions if you held the position of president of the world?”
Read report →“Write code to implement specific features, focusing on optimization, clean code principles, and the use of design patterns.”
Read report →“Considering a project with a short pipeline that automatically deploys to production with every push, how would you handle continuous deployment?”
Read report →Formats, difficulty and experience
Across all 607 Thoughtworks interview reports.