I applied online and the process took 2 months - interviewed at ThoughtWorks.
Interview Details –
First, I want to say that I walked into this interview *very* intimidated! I was told TW has one of the hardest interview processes in North America, and I am by no means a programming whiz. I think what got me though the process was my interest in writing quality, maintainable code (again, not to say that I'm an expert in it, but good enough to have a sense of where my code looked wrong), and my moral compass being aligned with theirs.
- Applied online, received an email a few days later asking me to complete one of three little programming assignments, and a questionnaire asking a bunch of 'random' questions (non-technical). The programming assignments aren't hard, but I think showing knowledge of OOP concepts and having rigorous testing is important.
Just a note, for me, after submitting the above assignments, I waited about a month before the next step. I sent a follow-up email 2 weeks in, and they responded to it, but yeah, it took a while for the next step, so I wouldn't worry too much if it takes a long time for you, too!
- The next step was a phone screen (non-technical). Pretty standard behavioural questions, as well as questions about social issues (ThoughtWorks cares about this things, it's important to have opinions on these issues that are aligned with ThoughtWorks').
After that was an in-person interview. This process took two days.
Day 1 (besides the logic tests, everything here was done in a group with 5 other interviewees):
- General info about ThoughtWorks
- Logic test (answer 50 questions in 13 minutes, I got around 39 questions before I ran out of time and started putting random numbers for the rest)
- Logic test #2 (13 flow chart questions, these questions made me feel like I was debugging a C-array, I think I got all of these correct)
- We were asked to prepare a little speech about a topic, then revise it based on a video they showed us.
- Finally, we were split into groups of 3 and asked to design a house for 'pugs.' The requirements were split amongst us, and we were supposed to communicate the important requirements as they came up. My group BOMBED this one as we didn't communicate an extremely important requirement properly and ended up with a non-functional design. That being said, we were able to communicate to the interviewers what our flaw was and how that impacted our design, and how we would fix it.
Day 2 (2 different ThoughtWorkers interviewed me for each stage)
- Pair-programming! (1.5hrs). I explained my programming assignment, and as I explained, talked about some of the design flaws that I noticed and how I'd change them. They showed me some TDD concepts and helped me refactor some of the code.
- Technical interview (1 hr). Prepared a 5 min presentation on a STEM topic of my choice. Got asked about some OOP concepts, design patterns, and was given a simple tic tac toe problem to solve.
- Values interview (1 hr). Very similar to the phone screen. Standard behavioural questions, and then questions about social issues and my opinions on them. This interview was the most intimidating for me, the only one where I felt like I was being "grilled"
Interview Question –
- What's your favorite programming book?
- What is Composition? Answer Question
I applied through a recruiter and the process took 4+ weeks - interviewed at ThoughtWorks.
Interview Details –
The interview process for ThoughtWorks is something that I have not experienced at other companies. I handed in my resume at Grace Hopper and pair coded with a few engineers before they reached out to me for an interview.
The first step is completing one of the three coding challenges they send you in any language you choose. I didn't write any tests for mine, but the code worked and I was moved on to a non-technical phone interview with a recruiter. We discussed the company culture, how I felt about pair coding, how I felt I fit in the technological world. This interview really got at the core of who I am as a person, and on the phone I was told I would be scheduled for an onsite in the next few weeks. The recruiter sent me a questioner which I filled out and returned. It had some fun questions about what I would do if I was president of the world etc.
I had my onsite in NYC with a few other candidates. It was two days, the first day consisted of tests, a group dialog, and a game. The second day was all interviews with the various teams.
The technical questions were not too hard, its mostly logic and reasoning skills. The most interesting interview was definitely the values interview, during which I spoke about some of my answers on the questioner they gave me, and had some spirited talks about education, underrepresented peoples in computing, and ways I'd overcome difficult situations in my life.
This is a company with a strong social justice mindset, and if that doesn't seem to align with you this may not be the place you want to work.
Interview Question – Describe your experience with gender discrimination in computing. View Answer
Negotiation Details – They don't do negotiations for JCs
I applied through a recruiter and the process took 4 months - interviewed at ThoughtWorks in November 2013.
Interview Details –
I first gave my resume to a TW recruiter at Grace Hopper a year ago. About four months ago (beginning of the school year), another recruiter contacted me asking if I would like to start the process.
The whole process took about four months, mostly because of the busy recruiting season. In the middle of it all I was afraid they had forgotten about me, but I sent a couple of emails just to keep myself on their radar and each time they assured me that they were getting to me.
Started with a questionnaire containing "fun" questions like "If you were president of the world, what five things would you change?" Definitely don't dismiss this, because they care a lot about your views on social justice. A coding problem was given at the same time. You pick one out of three options and you have three days to do it. Make sure to write some tests.
About a month or two later, I had a 45 minute phone interview with a recruiter discussing my background and passion for technology and social justice. Some behavioral questions were asked as well. Based on my performance here, I was flown out to San Francisco for a two day interview. From here everything progressed pretty quickly.
On day one I took two assessments, one 12 minutes long (answer as many basic math/reading comprehension problems as accurately as possible) and one hour long (lots of logic, flow chart based). I noticed that another candidate was asked to retake one of these at the end of the day, so you need to do well enough here to have a chance. Then there was a group mock consulting session. This was pretty fun.
On day two I had three interviews. First I was given an hour to prepare a five minute presentation on any STEM topic. They want to see passion here. Then my two interviews asked me a bunch of technical questions related to OOP and algorithms. I actually don't think I did very well here. The second was the values interview where you talk about the company and social justice. Passion and a genuine interest in some cause is important here. Third interview was pair programming with two developers where we worked together on improving my solution to the coding problem. This was a lot of fun. It was very relaxed, the two developers were really nice to work with, and I learned quite a bit too.
Less than a week later I got a call with the offer!
Interview Question – Most of the technical questions stemmed from projects I had put on my resume. Definitely should have refreshed my knowledge there. Answer Question
Negotiation Details – I was told that negotiation wasn't really an option for JCs.
I applied online and the process took 2 months - interviewed at ThoughtWorks.
Interview Details – First step involved a programming assignment, after which I spoke with the recruiter, and then I flew out to the NYC office. The office was super nice, but they were in the middle of some construction so there was a bit of clutter. Everyone there was very friendly, and the culture there didn't give off any sense of a large corporation. In the first day of interviews I took two assessments. For the second day, I had three one hour long interviews. The first was a pair programming session, the second was also technical but we mostly discussed and did a couple (very easy) problems on the white board, the third was the values interview.
Interview Question – What have you done that demonstrates you care about making a social impact? Answer Question
Negotiation Details – I am actually still considering their offer. I don't think they're open to any sort of negotiation.
I applied online and the process took 2 weeks - interviewed at ThoughtWorks.
Interview Details – I got an email asking me to do a small programming task (pretty easy I think it is to weed out people who just claim they can program). After completing that I had to complete a questionnaire online. Next I got a phone interview with an HR person where we discussed my background to try to get to know me better. They also ask that you complete a couple of personality tests to figure out who you are as a person. After this I got confirmation that I made it to the next step which was an in person 2 day interview process. The first day was looking at your submitted code and modifying it with people who work there, a small presentation (5 minutes) and an ethics interview (they are big on helping to create a better world). The second day was logic + flowchart tests and a group activity. After the interview I went home, and a couple of days later they called and informed me that I did not get the job.
Interview Question – On the questionnaire: Congratulations! You are now the president of the world, what are the first 5 things you would do? Answer Question
I applied online and the process took 3 months - interviewed at ThoughtWorks in June 2013.
Interview Details –
Applied online, received a online coding challenge. Completed it and did a phone interview with one of the recruiters. I was asked to fill out a survey and a personality test.
They asked general questions, about my experience, why I was interested in TW and what social justice meant to me, very laid back.
Then I was invited for assessment day, where they gave a company tour and had us do a wonderlic test and the logic test and a group assignment.
The group assignment was a made up consulting scenario where you were to build a house for some pugs and each person was given a bunch of requirements from the pugs, the goal was to create a floor plan and make it as cheap as possible.
After assessment day was the technical interviews. The first interview being pair programming with two TW devs. This went OK, one dev seemed very annoyed while the other was very helpful in answering questions.
The 2nd part of the interview is with another pair but they were more on the HR/recruiting side where they asked you about your values and thoughts on social justice, and what the 3 pillars of TW were. They also go over the questions you answered in the questionnaire they sent out. The question they went over for me was the "what would you do as president of the world?" I was also asked about what I have done for social justice.
After that was a short break and the last interview would be the technical interview with two different TW devs. Here they gave me a hour to prepare a 5 minute presentation on a STEM (science, technology, engineering or math) topic and there would also be a 5 minute q&a. This seemed incredibly hit or miss. One dev would be interested and the other would have absolutely no clue what I would be talking about and just be totally disengaged. After that they wanted me to whiteboard the mars rover problem and talk them through it.
The wonderlic was 50 questions in 12 minutes. I must have done poorly because they asked me to do it twice (once at assessment, once at the technical interview). The logic test is not very hard, but I recommend you look at some example problems: http://freshnerpaper.blogspot.com/2012/01/thought-works-placement-paper.html has some. READ the directions very carefully because sometimes it will try to trip you up. IE go to the box number in box 10 (so if box 10 had the number 5, you would go to box 5). Also for the last 3 tests you treat them like a maze it so draw the route that matches the condition and figure out what satisfies that path.
The interview was not stressful, but the emphasis is really on object oriented programming. Does the name of your classes and methods make sense? Can you explain the program you wrote?
Personally, I felt the whole social justice stichk was incredibly pretentious. The folks I talked with were taking credit for the companys efforts when they themselves do not sound like they contributed anything to the cause. Just seemed really full of it. You can't participate in any social justice causes until 2 years into employment or so anyways.
If you're considering TW because you're new at programming and have heard of the great things about TW university, I was told it was more of a consulting crash course where you are thrown into a big simulation. There would be some mandatory classes after TW university for building/deploying applications but a lot of learning will be up to you to do alone. So my advice is don't take this program/career path as the silver bullet that is the only way that will get you up to a professional level - do not get discouraged at all if you get declined. No mentor or teacher will ever get you there, you got to learn it yourself - they can help but remember it is you that crosses the line, stay persistent and passionate. This was a good learning experience for sure and I definitely took the opportunity to ask developers some technical questions of my own - that I always wanted answered. At the end of the day, I was probably not what they were looking for technically (I think I nailed the logic test but bombed the wonderlic and I felt like my OOP knowledge was lacking) but also I don't think it was an exact cultural fit. The interviews were always in pairs and it felt like one person was geninuely interested but another would not be. The interviewers were very professional and kept the atmosphere laid back so I did not feel like I was being grilled or anything.
Best of luck to any future candidates.
I applied online and the process took 4+ weeks - interviewed at ThoughtWorks in July 2013.
Interview Details –
Applied for the Junior Consultant position online and received the 3 programming questions a few weeks later. Completed the Mars Rover example (without JUnit, in case anyone is wondering if its necessary) and received the "positive feedback on your assignment" email with the questionnaire about a week after.
A week after sending in the questionnaire I received an email with details for a phone interview with a recruiter. The phone interview was HR based with no technical questions. Unfortunately I stumbled at this part but the process as a whole was a great experience.
Good luck guys!
I applied through other source and the process took 7 months - interviewed at ThoughtWorks in July 2013.
Interview Details –
Just as previous entries on here, the interview process ran as follows:
1) Brief phone call (to see if I was still looking for employment, etc)
3) Coding challenge
4) Another phone call (mostly the recruiter discussing details of the job)
5) Invitation to Chicago HQ to complete:
(a) Logic assessment
(b) STEM presentation
(c) Technical interview (Pair-programming)
(d) Non-technical interview (Discuss the values of the company, your values and how the two align)
My biggest advice is to be super well-versed in your contribution to the non-technical portion - for instance, don't make a passing remark about how we should aim to eliminate poverty unless you have some ideas on how to achieve it. They don't drill or interrogate you aggressively, but they do expect you to be able to (have and) communicate personal ideals and ideas.
The technical portion is very straight-forward. It consisted of very basic OOP questions. As for the pair-programming, my interviewers (of which there were two) were friendly and helpful with refactoring my submitted code. It was like a mini seminar on TDD.
(The interview process took a very long time for me - it ran on and off because I was still in school full-time)
Interview Question – Tell us about the political state of _______ (where you're from). Answer Question
Negotiation Details – No negotiation as this was an entry-level position.
I applied through college or university - interviewed at ThoughtWorks in July 2013.
Interview Details –
1. questionnaire and oop assignment
2. phone interview
first day: assessment
second day: technical and value inteview
Interview Question – the value interview three pillars and questions on questionnaire Answer Question
I applied through a recruiter - interviewed at ThoughtWorks in June 2013.
Interview Details – A met a recruiter at a job fair. I was scheduled to take an aptitude test and a logic test. Few days later, I was sent 3 coding problems and asked to solve any one of my choice and send the solutions. I was instructed to use Java,C# or Python. About a week later, I received an email from the recruiter saying there was a positive response about my code. In the one week I was waiting to hear back, I also had to completed a questionnaire with somewhat weird questions(e.g "8. After a hard-fought campaign, you are now President of the World. Congratulations! What are the first five things that you change? "). I was scheduled for an hour of interview with the recruiter and was asked background question. The recruiter called me to tell me that unfortunately I won't be moving forward unto the next stage. Apparently, she did not understand why I want to be a developer. But overall, it was a nice experience. The recruiter was very cool and funny.
Interview Question – Why do you want to be a developer? Answer Question
OK, let’s get the corporate stuff out of the way first. ThoughtWorks is a global IT consultancy providing Agile-based systems development and consulting services. We've pioneered many of the most advanced and successful… — Full Overview
Provided by employer [?]
This is the employer's chance to tell you why you should work for them. The information provided is from their perspective.
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –