Skip to content

Thoughtworks Interview Experiences

These Thoughtworks interview notes are rewritten from public student posts and prep-site summaries. Your panel can still look different.

Usual flow: HackerRank online test → Code pairing → Technical interview → Cultural fit

Code-pairing round plus explicit cultural-fit interview are signature Thoughtworks steps.

Code pairing: build problem from scratch while explaining. Tech interview (~1h): projects, tree + linked list coding, SQL, concepts.

Cultural fit with situation-based questions aligned to Thoughtworks values - not a generic CTC HR chat.

Student report 1 - [gfg Thoughtworks gad dec 2024] (2024)

Section titled “Student report 1 - [gfg Thoughtworks gad dec 2024] (2024)”

Same-day process after PPT: HackerRank 4 coding/75min → code pairing → 1h tech (projects, tree, LL, SQL) → cultural fit. Selection numbers 175→19→8→2 selected for Graduate Application Developer.

These notes come from public reports and can differ by campus, year, and role. If your college placement email or the official careers/notification PDF says something different, follow that.

After technical rounds, Thoughtworks usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

EPAM · Nagarro · Publicis Sapient · Globant · Zoho