I applied online. The process took 2 months. I interviewed at Thoughtworks (Dallas, TX) in Feb 2014
Interview
It was a very involved process spanning a few months. Phone interview -> Coding Project -> Code Review -> Second phone interview -> All day in person interview -> Negotiation. The motto of their interview is show us what you can do. I would use this model if I ever run my own company.
Interview questions [1]
Question 1
The volume and variety questions asked by several different people.
I applied through college or university. The process took 1 day. I interviewed at Thoughtworks
Interview
First Round : Machine coding (Patterns)- 20 minutes; out of 400 students, 40 shortlisted for the next round
Second Round: Machine coding (Airplane seating problem)- 2 hrs, it was a pairing round where the employees helped you to code out the problem. Out of 40, 8 shortlisted for the next round.
Third Round: Face to Face Interview - Most difficult round, need to have a strong technical base and questions were based on what you have quoted in resume. Tip: Mention only those skills in your resume which you are confident of.
I applied through a recruiter. The process took 3 months. I interviewed at Thoughtworks (São Paulo, ) in Sep 2012
Interview
The process is too long, and starts with a day-time event, in which some collaborators present the company, its values and its culture, before start with the actual process, with tests for notions of mathematics and basic pattern recognition. A logic test, which was very difficult to make due to the need of keeping track of the stack of execution and then came a technical interview with one of the technical leaders, which is the best part of it, once it turns out to be a change of experiences.
Later there is a value interview, when the company tries to find out if your culture is compatible with theirs. A very complex code test is sent by e-mail. You have to choose among 3 problems to solve, but both 3 are equally difficult to solve.
At last, a time with the whole team so they can know about you, what is your style of work, and a session of pair-programming.
Interview questions [1]
Question 1
The most difficult part was both logic and code test.