I interviewed at Thoughtworks (Porto Alegre, Rio Grande do Sul)
Interview
Foram seis entrevistas cobrindo de problemas de programação de nível fácil e médio, fit cultural, live coding, dinâmica em grupos. O processo em geral foi um pouco mais longo do que o usual, demorou em torno de 4 meses até a oferta.
Other Associate Developer Interview Reviews for Thoughtworks
I applied through a recruiter. I interviewed at Thoughtworks (Pune) in Feb 2026
Interview
I interview at TW for graduation application developer role or associate developer, I was referred by 1 recruiter first got assessment of hackerrank had 4 q easy level only had to complete small functions then secondly recruiter connected for intro them third was coe pairing got 1 problem have to solve that while using Opps principal interviewer was supportive technical was also combined in last 20-25 min they asked technical questions final was behavioural it's more like conversation and to know about you . I got offer but couldn't join because of 90 days notice period of current company, so recruiter told they will give me joining in next feasible batch . Let's see what happens
I applied through college or university. I interviewed at Thoughtworks (Mysore) in Oct 2025
Interview
The interview process involved a code pairing round with a senior engineer. It focused on writing clean, testable, and maintainable code while explaining the thought process clearly. The interviewer encouraged discussion about different approaches, code readability, and refactoring. Collaboration and problem-solving were key aspects of the round. Overall, it tested both technical and communication skills in a real-world scenario.
Interview questions [1]
Question 1
They asked me to implement an inventory stock balance function. I responded by modeling the domain with small, single-responsibility classes (e.g., Product, Inventory, and StockTransaction), exposing methods to adjust stock (add, remove, transfer) and to compute current balance (get_stock_balance). I validated inputs, documented behavior for negative/oversell attempts, considered concurrency (locking or atomic updates) and wrote unit tests that cover normal flows, boundary cases, and concurrent updates. I emphasized readability, testability, and how the design allows adding features like per-location inventory or reservations without changing the core logic.