Referred by a friend. Recruiter reached out asked some screening questions. Did a pair programming remotely with a principle. Had a 4 hour onsite interview day in which I did pair programming again, a card game, and a presentation. The biggest issue with the interview process is the presentation and card game. You get developers asking you soft skills questions, when clearly they are coming in with plenty of bias and personality issues. For example, one php developer claimed she hated computer science and developer culture, but thoughtworks has the culture she likes. She provided no reasoning behind the claim, but her bias was one in which if she deems you a member of a culture she does not like, you're cooked. The mission of ThoughtWorks claims to be one of inclusion, but you get individuals who clearly are more focused on exclusion. The presentation was convoluted. You're asked to come with something you're passionate about. I had two developers at the presentation, one who was not very technical and another who thought he knew everything. The presentation is very limiting, and the interviewers assume it's the only thing you know or have ever worked on. They do not have a process for asking questions, and assume your enterprise is a vacuum in which you could have done anything that makes sense to them. About 45 minutes into the one hour presentation, the technical developer stated "oh wow we're only 30% into what we should have asked". The pair programming problems were straight forward. The technical principals were the most informed and pleasant part of the interview process. Overall negative experience. Would not recommend unless you want to work with people who say things like "the only thing in my life are plants, thats why thoughtworks is for me".

Frustrating and inconsistent interview process (code pairing felt like a trap This was honestly one of the more frustrating interview experiences I have had for a senior/lead role. The process included a code pairing session, which was presented as collaborative. In reality, it felt highly directive and inconsistent. I followed the interviewer’s instructions during the exercise and explicitly called out technical trade-offs while doing so. Despite that, the feedback later claimed I had “overlooked” those exact trade-offs. That’s simply not true. So the situation becomes: * follow the interviewer → get penalized * don’t follow → probably get penalized for not being collaborative There’s no clear or fair evaluation path there. Another red flag: I was initially told during interview that two additional interviewers would join, but then midway it changed to them being “unavailable.” For a company that emphasizes professionalism, that felt disorganized and poorly coordinated. Also surprising for a senior-level interview , a noticeable amount of time was spent checking whether I had previously coded something using basic commands like git diff. That’s not a meaningful signal for a Lead role and felt like a poor use of interview time. If they are doubting the candidate using poor tactic like this, the company should consider switching strategy to test the candidate rather than giving problem upfront. What makes this worse is the follow-up. When these inconsistencies were raised, the response from recruit team didn’t actually address them. Instead, it was reframed as “testing adaptability” and “responding to guidance,” without explaining how that aligns with feedback that contradicts what was explicitly discussed during the session. On paper, the feedback listed several strong positives, which makes the final decision even harder to reconcile. It feels like the outcome was decided first, and the reasoning was fitted afterward. Overall, the people were polite, but the process itself felt inconsistent, poorly aligned, and not reflective of what actually happened in the interview.