Thoughtworks Lead Software Developer interview questions
based on 11 ratings - Updated Apr 19, 2026
Averageinterview difficulty
Mixedinterview experience
How others got an interview
38%
Employee Referral
Employee Referral
38%
Applied online
Applied online
13%
Recruiter
Recruiter
13%
Staffing Agency
Staffing Agency
Interview search
11 interviews
Viewing 1 - 5 of 11 Interviews
Thoughtworks interviews FAQs
Lead Software Developer applicants have rated the interview process at Thoughtworks with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 83.8% positive. This is according to Glassdoor user ratings.
Common stages of the interview process at Thoughtworks as a Lead Software Developer according to 2 Glassdoor interviews include:
Phone interview: 50%
One on one interview: 50%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Thoughtworks (Singapur) 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
Thoughtworks response
2w
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.
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
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