Thoughtworks interview questions

I sent in my resume on a Thursday, received a phone interview request (with an availability calendar attached) on the following Monday, scheduled a call for Friday the same week, so roughly one week between my application and our first talk. Emails were very friendly and almost casual (but still professional), and so was the phone interview. My interviewer briefly introduced herself, then asked me to do the same. We talked about the position, the reasons for my being interested in it, about team sizes and culture, and she asked some questions here and there. The overall feel wasn't very much like a strict, structured interview (although I am sure it was in fact very structured), but it felt more like a conversation in which my interviewer was genuinely interested in what I had to say. She explained the next steps (a QA assignment via email, and then potentially an on-site interview) and asked for any remaining questions. I had none because she had answered all of them in the course of the interview already. Right after the phone call, I got the QA assignment (which basically asks you to describe how you would do QA on a specific object). I didn't end up finishing the assignment because I got another offer that I took. When I communicated this to my interviewer, she was very friendly about it. Overall very friendly, professional and positive interviewing experience.

The whole process was very pleasant. Literally everyone I've met during the process was very nice and friendly. It was a rather smooth experience. I felt the recruiter was very frank and transparent with me. I first saw ThoughtWorks on Martin Fowler's blog and later when I learned that Selenium was originally developed at ThoughtWorks, I became kind of curious and did a bit of research on the company. What I found was quite interesting and positive and I felt like it could be an inspiring place to work at so I applied online. I wrote a pretty genuine cover letter detailing how I found out about ThoughtWorks and why I think it's a good fit for me. The recruiter actually read it and I think it might have helped my chances. Next thing they gave me a take-home technical assignment. I took it pretty seriously and spent a weekend working on it. Some time later I got on a phone screening with a ThoughtWorker. It was supposed to be a technical call but it really wasn't that technical (in comparison to the other technical interviews I've had). But it was a great conversation. We kind of just talked about software craftsmanship in general. Then, they had me travel to the New York city office (it's the closest one to me) for the on-site interview. Again, the people I met during the interview were really nice. There were 4 on-site interviews, an hour each. They were not particular technical. No whiteboard coding. There was, however, one actual coding session on a computer.