Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Thoughtworks

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Thoughtworks reviews | Thoughtworks jobs | Thoughtworks salaries | Thoughtworks benefits | Thoughtworks conversations
      Thoughtworks interviewsThoughtworks Lead Developer interviewsThoughtworks interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Lead Developer Interview

      7 Apr 2022
      Anonymous interview candidate
      Santiago

      Other Lead Developer interview reviews for Thoughtworks

      Lead Software Engineer Interview

      19 Apr 2026
      Anonymous interview candidate
      Singapore
      No offer
      Negative experience
      No offer
      Negative experience
      Average interview

      Application

      I applied online. The process took 4 weeks. I interviewed at Thoughtworks (Santiago) in Mar 2022

      Interview

      Very bad and sad experience with recruiter, technical people was wonderful. In summary I shared to recruiter that I had another offer that was about to expire in a couple of days, Thoughtworks accelerated the last two interviews which was great. I asked for feedback, recruiter told me that all was good, even ask for my id number to move into the offer letter part. On the very date when my other offer was going to expire, the recruiter of thoughtworks assured me that she the offer was going to be approved in a matter of minutes, so my mistake was to believe it and I declined the other offer. After this episode the offer never came, every day I had to ask about the offer to recruiter, which never was real or in words of recruiter had not the final approval. Final interview was innecesarily delayed for 4 days. I was told that I had technical gaps and that we could be back in the process in a couple of months. I was offered a feedback e-mail with the things I had to learn to fill the gaps I had. This e-mail was a lie too, never came up. Learned Lesson: never believe in recruiters if the offer is not formalized by e-mail. The process was: 1. Recruiter Interview 2. Coding Activity 3. Technical Interview 4. Culture Conversation. 5. LeaderShip interview. 5.5 hours in total, hundred of questions. Good experience in general, some questions about social matters, diversity and inclusion.

      Interview questions [1]

      Question 1

      Q: what would you do if ... (situational questions) there is discrimination at work ? Q: Tellme about agile methologies you have used. Q: Experience in Pipelines? Deployments? Q: Experience in Unit testing ? Q: Tell me about confllicts on your team and how do you resolve them ? Technical Part (was fun): - Pair programming - build a web service in express/nodejs to calculate usage cost of a electricity system. - refactoring - create a node js module to encapsulate the solution.
      Answer question
      4
      Easy interview

      Application

      I applied online. I interviewed at Thoughtworks (Singapore) in Apr 2026

      Interview

      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.
      2
      avatar
      Thoughtworks response
      3w
      Thank you for sharing your feedback and for taking part in our interview process. Insights like yours help us continue improving how we engage with candidates. Wishing you the best in your next steps.

      Lead Software Engineer Interview

      13 Nov 2025
      Anonymous employee
      Madrid
      Accepted offer
      Positive experience
      Average interview

      Application

      I interviewed at Thoughtworks (Madrid)

      Interview

      4 entrevistas: Recruiter screening, pairing interview, Tech interview, Culture aligment, Manager interview. Un proceso muy cuidado, auqneu es largo no se hace tedioso y el feedback es rápido y de calidad.

      Interview questions [1]

      Question 1

      En la de pairing se trabaja en una nueva feature en una base de codigo que se comparte antes de la entrevista. En la entrevista técnoca se profundiza en experiencias previas
      Answer question

      Lead Developer Interview

      3 Dec 2025
      Anonymous interview candidate
      No offer
      Negative experience
      Average interview

      Application

      I applied through an employee referral. The process took 4 weeks. I interviewed at Thoughtworks in Nov 2025

      Interview

      Durante o processo, tive uma primeira etapa com uma pessoa do RH, em seguida uma etapa técnica realizando um teste de programação durante a entrevista, em seguida tive uma etapa cultural, porém novamente tive outra etapa cultural depois da primeira, ambas as peguntas foram parecidas mudando apenas a entonação pois eram pessoas diferentes, mesmo comentando um pouco sobre liderança (foco da vaga) houve uma pressão maior em pontos de acessibilidade na segunda etapa cultural, vi um certo descaso comigo pelo responsável do processo, pois em algumas etapas enviei e-mails com dúvida mas não obtive retorno nenhum, e após a segunda etapa cultural fui informado que reprovei, porém foi um feedback genérico apenas descartando o processo, após ir atrás de um feedback obtive um

      Interview questions [1]

      Question 1

      Um case que eu acho que a tecnologia atrapalhou/falhou
      Answer question
      1