4 rounds - 1. Recruiter call and screening (~45 min) - This was much longer than some other recruiter calls. Began with discussing background, availability etc. Then a lot of behavioral questions and past experiences. 2. Pair programming (90 min) - They'll give you repository link to a project in the language of your choice. You're expected to set it up in your favorite IDE and understand how it works. Nothing crazy, it's a very simple web application. Search online for JOI energy TW and you should be able to find it (this might change in the future). Since it's your favorite IDE, make sure you're able to navigate the code seamlessly and know the shortcuts, kepmaps etc. They love it. Also, it won't go well if you don't have something working and they have to spend interview time to help you with setup. During the interview, they'll pull up a Trello story board and you get to choose which story you want to implement. The stories have scope (either in form of story points or T-shirt sizes). Pick up the easiest one (no judgement there). You'll not be based on completion but rather the approach. Heavy emphasis on TDD (read it up). Even if you haven't used it, they'll push for it. Bonus points if you already know it and can implement it to begin with. Other simple things to keep in mind; no duplication, meaningful method names, no long methods/classes, properly writing test cases for all scenarios, you don't need to implement design patterns but mention a few if you get opportunity to. It will show you know about those. Even better if you're able implement one or two simple ones (I implemented singleton). Simplicity goes a long way in this interview. 3. Technical interview - 1 hr 4. Leadership interview - 1 hr So, these are supposed to be two separate rounds, but they had some kind of a 'Fantastic Friday event' going on, based on which they were clubbing these 2 together into a single 1 hr interview (15 min behavioral, 45 min technical) aimed at reducing the interview process time for a few potential candidates. So it helps to do really well and communicate properly on pair programming round. This is something experimental and could change in the future. Even you get these 2 as separate rounds, they're pretty relaxed and won't contain any crazy programming challenges. The focus is on your past experiences and projects, and asking how you'd tackle some real life situational technical challenges. It'll help immensely to know your projects well. ThoughtWorks is infamous for lengthy interview process. But it's good to see that they've narrowed it down to just 4 rounds instead of 6-7 as a few reviews here suggest. The Fantastic Friday event reduced it even further to just 3 rounds for me and the quick turnaround was a huge factor in me accepting the offer (since I was actively searching and had multiple offers). Overall a very positive experience. All interviewers and very relaxed and make you feel at ease; zero stress. Also it's very refreshing to see that there is a lot of transparency between rounds and you get exact feedback of each round; something they should be commended for. I'll highly recommend their interview process, regardless of whether or not you get selected and whether or not you decide to accept the offer.