Thoughtworks Interview Questions
& Process

I interviewed at TW for a graduation application developer role or associate developer. A recruiter initially referred me, and I first took a HackerRank assessment with 4 easy-level questions, where I only had to complete small functions. Then, the recruiter connected for an intro call. Next was a COE pairing session where I was given one problem to solve using OOP principles; the interviewer was supportive. The technical part was also combined in the last 20-25 minutes, where they asked technical questions. The final round was behavioral, more like a conversation to get to know me. I received an offer but couldn't join due to my current company's 90-day notice period. The recruiter mentioned they would offer me a spot in the next feasible batch. Let's see what happens.

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.

The interview process had about 4 rounds, though the scheduling system and documents didn't quite match up. It started with a recruiter screening, followed by a technical screening, then an office interview (which was online) that included a case study, and finally a leadership and culture interview. The HR team was generally helpful and responsive, typically replying within 1-2 business days, but this seemed to be the case only if they were interested. Unfortunately, after my last interview, I was ghosted and never heard back, which felt like a typical way things are handled. The sessions themselves went fine, but during the case study interview, the interviewer spent a lot of time sharing his own career journey and asking a lot of background questions. When it came time for my case study presentation, he interrupted me partway through, asking me to focus on just 1-2 slides, which forced me to rush through the rest. I don't think I was given the full 30 minutes, and this led to feedback that I didn't present the content in enough detail later on. Throughout the session, it felt like he was looking for a very specific type of PM who was just like him. I don't believe my presentation was poorly done, especially considering the significant effort I put into the deck. When I asked for feedback at the end, he initially said it was thorough and had great visuals (referring to the journey and future experience parts), but then mentioned the later sections felt rushed (which was his doing because he told me to hurry). I never heard from anyone, even after reaching out to HR. I was ghosted.

The interview process was great and pretty unique. Recruiters were professional and clearly explained what to expect in each round, even sharing blogs from Thoughtworkers related to my profile. The whole process took about 1 month and 10 days from the initial contact to the offer. Patience is key! There were 4 rounds: 1. Recruiter Screening: They asked some standard questions, and good communication and relevance to the role were important. 2. Technical Screening: You could even choose your preferred time for this interview with a Senior Consultant (the level depends on the role you're applying for). It was quite thorough, covering all aspects of the job description, though not in extreme detail, and the questions were challenging. 3. Office Interview 1: Although called 'office interview,' it was online. This was a more in-depth technical interview with a Lead Consultant. You really needed to have hands-on experience with what you claimed; bluffing probably wouldn't work unless you were an expert. 4. Office Interview 2: This wasn't technical; a Principal Consultant conducted it, focusing more on how well you'd fit into their diverse culture (DEI). Being genuine and confident was important here.