Academic snapshot
Marks: 80% UG on several GAD mailers; else drive-specific
Degree: B.E./B.Tech CS/IT (AI-ML on some tiles)
Backlogs: None on strict lists
Year: Final year / named batch
Thoughtworks Placement Papers 2026
Thoughtworks is a global agile software consultancy helping clients build custom software products and platforms. India delivery hubs span Bengaluru, Pune, Chennai, Coimbatore, and Gurugram. Thoughtworks is known for strong engineering culture and recruits campus graduates for developer and consultant developer roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Thoughtworks in 2026?
Thoughtworks does not publish one forever CGPA for every India graduate drive. Campus mailers and off-campus tiles disagree. Treat numbers below as candidate-reported as of August 2026.
Who this hub is for
- For: Final-year CS/IT students targeting Graduate Application Developer (GAD) or Associate Developer. Joining cities: Bengaluru, Pune, Chennai, Coimbatore, Gurugram.
- Not the same track: Experienced consultant / principal loops, or design-only roles. This hub is the graduate filter: HackerRank + pair + tech + values.
- AI-ML / related: Some 2026 off-campus tiles list AI-ML with core CS/IT. ECE is not a default yes.
Degree, marks, backlogs
- Degree: B.E./B.Tech, typically Core CS/IT. Dual degrees: read the mailer.
- Marks: Several 2025-2026 GAD notes print 80% in UG and no backlogs. Older chatter said “no strict public floor.” If your mailer says 80%, that is your floor.
- Batch: Locked to a year (2025 campus, 2026 off-campus “ready to join Sep 2026” style). Wrong batch is an auto no.
- Backlogs: None on the strict mailers.
- Languages: One of Java, Kotlin, Python, Ruby, JavaScript you can pair in. Exposure to GitHub/LeetCode/HackerRank is often listed as a plus, not a certificate hunt.
Who usually fits and who struggles
Good fit: You already explain while you type. You like tests and small methods. You have a project you can defend without a slide deck. You can talk about feedback and inclusion without sounding like a brochure.
Harder path: You only practise silent LeetCode. You refuse to pair. You listed five languages. You treat cultural fit as “HR fluff.” A 9.2 who cannot narrate a refactor loses to an 8.1 who pairs calmly.
80% myth: Some drives are 80%. Others never print it. Do not skip applying if your college mailer has no percentage, and do not argue 75% into an 80% list.
On-campus vs careers
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | PPT, same-day loop possible, college 80% list | Pair + values |
| Off-campus / careers | HackerRank invite, slower calendar | Same technical flavour |
| Referral | Visibility | You still pair |
Off-campus does not mean easier pairing. It often means a denser mix of people who cleared HackerRank and then went silent in the pair.
CGPA / percentage: printed floor vs selected cluster
Is there a CGPA cutoff? Sometimes a percentage (80%) rather than a 7.0 CGPA line. After the screen, Thoughtworks weighs DSA + clean code + pairing + values.
| Hiring route | Typical filter (reports) | What actually filters you |
|---|---|---|
| Campus GAD | 80% UG, CS/IT, no backlogs on several notes | College list + HackerRank + loop |
| Looser drives | No public floor | Resume + coding |
| Selected cluster | Strong pairing, not max CGPA | Communication under a shared editor |
Selection chances by academics
| Band | Rough chances | Reality check |
|---|---|---|
| Below printed 80% | Low if that rule exists | Other drives only |
| At 80% / 8.0 | Medium | HackerRank completeness decides |
| Above, with projects | High if you can pair | Grades never save a silent pair |
| 9.5, no Git, no talk | Low | This company interviews live |
Skills they actually filter
Primary: DSA, clean code, TDD/agile thinking
Languages: Java, Kotlin, Python, Ruby, JS
Exam filter: HackerRank + pair interview
Thoughtworks is a consulting XP hire. Clearing 80% only gets you a HackerRank link. Treat complete coding as the cut, pairing as the offer conversation, and cultural fit as the culture gate seniors skip until the night before.
Thoughtworks previous year papers & PDFs
Download 2026 Thoughtworks placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Thoughtworks previous year papers actually train
Thoughtworks does not publish a permanent official paper. “Previous year papers” on this site are pattern trainers for HackerRank-style DSA, OOP katas, and interview prompts. They are not leaked live tests.
| Round (typical) | What to practice |
|---|---|
| HackerRank | 3-4 mediums under 75 minutes |
| Pair | Incremental design, names, tests |
| Technical | Trees, lists, SQL, projects |
| Cultural fit | STAR, not puzzle dumps |
Think of papers as simulators for a 75-minute coding clock. Thoughtworks reuses families (arrays, hashing, trees, clean OOP) more than exact clones. If you can finish three of four in a 2024-style set, a 2026 HackerRank will feel familiar even when the last prompt is new.
Themes that keep repeating (2024-2026)
- Campus Dec 2024 (GFG GAD): Same-day after PPT. HackerRank 4 problems / 75 min. Candidate solved 3 fully + 1 partial. 175 → 19 after OA, 8 after pairing, 2 selected. Tech (~1h): projects, tree, linked list, SQL. Cultural fit: situation-based values, not CTC.
- 2025 campus Associate: HackerRank date on the JD; CTC ₹11.10 LPA; 80% UG, core CS/IT, no backlogs; Bengaluru and Pune.
- 2026 Medium Associate Developer: Online coding then pair on an existing repo (not always from scratch). Last 15-20 minutes allowed AI tools to see prompting quality. Tech with two interviewers. Leadership/cultural fit. No separate HR. Selected for Associate Developer.
- 2026 off-campus tiles: GAD, ₹11-13.2 LPA, 80%, CS/IT/AI-ML, join Sep 2026, TDD/SOLID/pair language in the JD.
How to use one paper set in a single sitting
- Timed: 75 minutes, 4 problems. Stop and submit at 75.
- Untimed review: rewrite the cleanest solution with better names.
- Map each problem to a theme; pull cousins from coding questions.
- Re-solve one problem out loud as if pairing.
- Log one values story the struggle reminded you of (asking for help, giving feedback).
Related problems to practice
| Theme you saw in a set | What to drill next | Why Thoughtworks asks it |
|---|---|---|
| Move zeros / two pointers | In-place + tests | OA completeness |
| Rotate array | Reverse-three-times | Same |
| First unique character | Frequency maps | Hashing mediums |
| Min stack | Design + edges | Clean OOP |
| Tree / linked list | Recursion narration | Tech hour |
| SQL | Joins, group | Tech hour |
From application to offer at Thoughtworks
Thoughtworks hires graduates through campus cells, careers, and off-campus HackerRank drives. After eligibility, the shape is XP-consulting: code in public, then prove you can collaborate and live the values.
Application methods
Campus recruitment
Primary for many colleges. PPT → HackerRank → pair → tech → cultural fit. Sometimes all in one day.
Online applications
thoughtworks.com careers / job boards. Follow the HackerRank mail.
Referrals
Help visibility. You still pair.
1. HackerRank online test
Dec 2024 campus: 4 coding problems, 75 minutes. 19 of 175 moved on. Languages from the invite (Java/Python/JS common).
Pass habit: Fully solve the two easiest first. A third complete beats a fourth 40% dump. Name complexity in comments if you have 20 seconds. Edge cases: empty, single element, duplicates.
Deeper OA notes: Thoughtworks online assessment.
2. Code pairing
This is the signature filter.
- 2024 campus: Build the brief from scratch while explaining. 19 → 8.
- 2026 Medium: Existing repository with bugs/features. Interviewer talks the whole time. Last 15-20 minutes: AI tools allowed; they watch prompts and integration, not copy-paste worship.
What they score: communication, incremental slices, OOP, tests, whether you listen when they nudge.
Pass habit: Think out loud. Write a failing test or a tiny example first. Ask “should we handle X?” before inventing a framework. If you get stuck, narrate the next experiment.
3. Technical interview (~1 hour)
Projects, then tree + linked list coding, SQL, concepts. Two interviewers on some 2026 accounts. They will open your Git history if you linked it. Be ready to redesign a module for extension (the consulting “next client change” question).
4. Cultural fit / leadership
Situation-based. Inclusion, feedback, disagreement, client impact, Why Thoughtworks. Friendly panels still fail people who only have textbook answers. Some 2026 loops have no separate HR after this.
Write four stories:
- You received hard feedback and changed.
- You included someone who was talked over.
- You disagreed and stayed kind.
- Why consulting + XP, in your words.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | HackerRank | ~75 min | Completeness |
| 2 | Pair | ~60-90 min | Collaboration |
| 3 | Technical | ~60 min | Depth + SQL/DSA |
| 4 | Cultural fit | ~45-60 min | Values |
| 5 | HR | Often folded in | City, CTC, joining |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| PPT / apply | Days | Read 80% line |
| HackerRank | 1 slot | 4×75 on some campuses |
| Pair + tech + values | Same day or +1-2 weeks | Campus can be one day |
| Result | Days | 2024: 2 selected end of day |
| End to end | 1 day to ~4 weeks | Off-campus longer |
Pairing: a 60-minute clock you can rehearse
| Minute | Move |
|---|---|
| 0-5 | Restate the problem. Example in / example out. |
| 5-15 | Smallest slice that runs. Ugly is fine. |
| 15-40 | Next behaviour. Extract a name. Add a test if the language allows. |
| 40-50 | Edge cases the interviewer cares about. |
| 50-60 | If AI is allowed: one targeted prompt, then you own the merge. |
Do this with a friend weekly. Silent genius is the fail mode.
AI window (2026-style)
If they allow tools at the end:
- Prompt with constraints and the current function name.
- Read the output. Reject style that does not match the repo.
- Explain what you kept and what you threw away.
Pasting a wall of generated code without reading it is a values fail as much as a tech fail.
Technical: SQL you should write on a whiteboard
SELECT c.name, COUNT(o.id)FROM customers cLEFT JOIN orders o ON o.customer_id = c.idGROUP BY c.nameHAVING COUNT(o.id) >= 2;Explain LEFT vs INNER. That plus a tree recursion is enough for many GAD technicals. System-design theatre is not.
Cultural fit: what “good enough” sounds like
Why Thoughtworks: “I want to learn by pairing and I care how software gets delivered, not only that it compiles.” Specific > “I like agile.”
Feedback: Situation, what they said, what you changed, what you would still do differently.
Inclusion: A lab teammate who was ignored, what you did in the room, not a speech about diversity policies.
Documents and Git
ID, resume one page, college ID. Put a real GitHub if you claim one. Pairing will reveal an empty repo faster than HR will.
Weekend mock that matches a campus day
Saturday morning: 75 minutes, 4 HackerRank-style problems. Score completes only.
Saturday afternoon: 60-minute pair kata with a friend (they may interrupt).
Sunday: 45-minute tech oral (project + one tree + one SQL) and record two cultural-fit answers.
That weekend is closer to Dec 2024’s same-day loop than twenty silent LeetCode mediums.
Pairing anti-patterns
- Silence for three minutes while you “think.”
- Renaming everything in the repo before a test passes.
- Ignoring the interviewer’s hint to extract a class.
- Dumping AI output you did not read.
- “It works on my machine” with no example.
If you catch yourself doing one of these in practice, stop and narrate the next smallest step.
TDD-lite that is enough for GAD
You are not expected to recite a Kent Beck book. You are expected to:
- Write an example (input → output) before a 40-line function.
- Make it pass.
- Rename.
- Handle null/empty.
That loop in Java or Python is “TDD/agile thinking” for a fresher panel. SOLID as buzzwords without a smaller method is worse than no SOLID.
Why Thoughtworks (40 seconds)
“I learn faster when I pair, and I want consulting work where delivery practices are part of the job.” The GAD loop (HackerRank, pair, values) matches how I already practise.” If you do not like pairing, do not fake this sentence. Sit Sapient or EPAM instead.
City and travel
Bengaluru and Pune show up most on 2025 Associate notes. Chennai, Coimbatore, Gurugram also hire. Client work can mean travel. Ask in cultural fit if that matters. “I will only do remote” is a values mismatch for many teams; be honest.
Thoughtworks University vs the interview
University is onboarding after the offer. Do not spend prep time memorising internal program names. Spend it on pairing and stories. Mention University only if structured learning is a real reason you applied.
What “19 of 175” should do to your plan
The OA is a numbers game. You cannot charm the HackerRank compiler. Three complete solutions is the practical bar from that 2024 write-up. If your mocks are 1 complete + 3 partials, you are not ready to pair yet. Fix completeness first.
Repo pairing: a practice setup
Clone a small public kata or your own mini-project. Ask a friend to pick a failing test or a new feature. You have 45 minutes to:
- Run the project.
- Find the relevant file without panic-scrolling.
- Change the smallest thing.
- Explain the design you would not do.
That is closer to the 2026 Medium account than another Two Sum.
Clean code checklist they can see
- Names that say what the value is (
pendingOrders, nottemp2) - Methods you can read in one screen
- No 8-level nest
- Tests or at least examples
- A comment only when the why is not in the name
You do not need a style-guide tattoo. You need the interviewer to follow your diff.
SQL plus a tree: the 2024 tech mix
GFG GAD: projects, tree, linked list, SQL in one hour. That is not a system-design round. Practise:
- Invert a binary tree / level order (narrate recursion)
- Reverse a linked list / detect cycle
- One JOIN with GROUP BY
If you can do those on a shared editor while talking, you are in the 2024 selected shape. If you only have LeetCode hard graphs, you may still freeze on SQL.
Values stories that fail
- “I believe in diversity” with no scene.
- Blaming a teammate as the whole plot.
- Claiming you never disagreed with anyone.
- Reciting Thoughtworks values from a careers page.
A lab argument about Git workflow, resolved with a written convention, is better than a speech.
Same-day campus stamina
Dec 2024 was PPT + OA + pair + tech + values in one day. Eat. Carry a charger. Do not start a new LeetCode problem in the gap after HackerRank. Review your own OA solutions; pairing may echo them. Keep values stories on a paper in your pocket, not on a phone you cannot unlock in the hall.
HackerRank completeness vs cleverness
Thoughtworks pairing will reopen messy code. A brute-force solution you can explain and then improve in the pair is better than an unread contest template. On the OA, still prefer a passing O(n log n) over a broken O(n). Comments like “would add tests for empty input” help only if the code already runs.
Graduate role names
Graduate Application Developer and Associate Developer both appear on 2024-2026 India notes. Read the JD for city and CTC. The loop (HackerRank, pair, tech, values) is the same sport. Do not prep a different stack because the title token changed.
What to do if you fail the pair
You can sit another drive. The failure mode is usually communication or incremental delivery, not “I don’t know Dijkstra.” Practise pairing for two weeks and retry off-campus. Do not immediately switch to only more LeetCode; that was not the round you lost.
Off-campus calendar
HackerRank one week, pair the next, tech later. Keep a 30-minute weekly pair kata until the last round, even if the portal is quiet. Students who “take a break” after OA forget how to talk while typing. That is an expensive way to waste a 19/175-style shortlist.
80% vs skills
If your mailer prints 80%, the cell will pre-filter. If it does not, a 75% with strong pairing still has a shot off-campus. Do not invent a CGPA FAQ for a year when only the percentage line changed. One eligibility story is enough: read the JD. If both 80% and “no cutoff” rumours circulate in your WhatsApp group, the mailer in your inbox is the only one that matters.
Thoughtworks practice pages
Week-by-week plans live on the preparation guide, not here.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
Thoughtworks preparation strategy that works
If a Thoughtworks invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Thoughtworks sits around ₹10-18 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Thoughtworks does not publish one forever CGPA. Several 2025-2026 campus/off-campus Graduate Application Developer notes print 80% in UG, Core CS/IT (sometimes AI-ML), no backlogs, and a specific batch year. Other drives feel looser. Always verify thoughtworks.com careers or your placement email. Skills in DSA, clean code, and TDD/agile thinking matter more after the screen.
What you are training for: Typical campus shape: PPT → HackerRank coding (Dec 2024 GFG: 4 problems in 75 minutes; 19/175 advanced) → Code pairing → Technical interview (~1 hour: projects, trees, linked lists, SQL) → Cultural fit / values (situation-based; some 2026 accounts had no separate HR). End-to-end can be same-day on campus or a few weeks off-campus.
Short version of the prep split: About 40% DSA you can explain while typing, 25% clean OOP/TDD habits (small methods, tests, names), 15% SQL and CS fundamentals, 10% pair-programming practice with a friend, 10% values stories (inclusion, feedback, client impact). Languages: Java, Kotlin, Python, Ruby, JavaScript. Full plan: /thoughtworks/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Thoughtworks previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Thoughtworks drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Thoughtworks usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Thoughtworks?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Thoughtworks-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Thoughtworks story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Thoughtworks PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Thoughtworks papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Thoughtworks papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Thoughtworks-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Thoughtworks compensation & benefits
Figures are candidate-reported India bands as of August 2026.
| Band | Typical CTC (reports) | Notes |
|---|---|---|
| GAD / Associate Developer | ₹10-18 LPA | Hub-level band |
| 2025 campus Associate | ~₹11.1 LPA | Bengaluru / Pune note |
| 2026 off-campus tiles | ₹11-13.2 LPA | Confirm city |
Confirm base vs variable and joining city on the written offer. Treat ₹10-18 LPA as a reported band, not a guarantee.
Benefits students actually care about
- Thoughtworks University / structured graduate onboarding
- Learning culture, tech radar talk, XP practices
- Cities: Bengaluru, Pune, Chennai, Coimbatore, Gurugram
- Client-project variety (also: travel/client expectations, ask)
How to talk CTC
Know ₹11 L-ish campus numbers. Ask city. Cultural fit is not the place to hard-negotiate like a product blog. Compare offers on city + learning + pairing culture, not headline only.
Offer-stage discipline
- Read role name (GAD vs Associate)
- Confirm joining vs exams
- Do not resign another offer until the letter lands
- Background check will match percentages if 80% was printed
What’s changed in Thoughtworks hiring lately
- Pair programming is still the differentiator. 2026 added existing-repo + optional AI window in at least one public write-up. Practise both blank-file and repo pairing.
- HackerRank 4×75 remains the campus shape people cite. Conversion 175→19 is the vibe: many sit, few pair.
- 80% CS/IT shows up on 2025-2026 GAD tiles. Do not assume the old “no cutoff” line.
- Cultural fit can replace HR. Have stories ready the morning of OA.
- CTC cluster ~₹11-13 L on recent campus/off-campus notes, inside a wider ₹10-18 chatter band.
- Net for 2026: explain while you code, finish three HackerRank problems, write four values stories.
Common questions about Thoughtworks hiring
Process & papers
What is the Thoughtworks placement process?
HackerRank → pair programming → technical (~1h) → cultural fit. Some 2026 accounts had no separate HR. Campus can be same-day. Off-campus takes longer.
How many rounds are there in Thoughtworks interview?
Most graduate loops report 4 stages. Count the invite.
Can I download Thoughtworks placement papers PDF?
Yes. Free Thoughtworks papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
What is the Thoughtworks online assessment exam pattern?
Campus Dec 2024: 4 coding / 75 minutes on HackerRank. 19/175 advanced. Languages: Java, Kotlin, Python, Ruby, JavaScript as listed. Confirm the invite.
Eligibility & offer
What is Thoughtworks eligibility criteria for freshers 2026?
Several GAD mailers: 80% UG, core CS/IT, no backlogs, named batch. Other drives print no floor. Your notice overrides this page.
What is Thoughtworks salary for freshers in India?
Candidate-reported CTC often lands around ₹10-18 LPA, with ₹11.1 L and ₹11-13.2 L cited on recent campus/off-campus notes (as of August 2026). The written letter is the only number that matters.
What is Thoughtworks University?
Immersive graduate onboarding before client work. A reason to join, not an exam round.
Prep & Thoughtworks-specific
How to prepare for Thoughtworks placement?
DSA you can narrate, pairing katas, SQL, four values stories. Details: preparation guide.
What is Thoughtworks pair programming interview?
Collaborative coding with a Thoughtworker. From-scratch (2024 campus) or existing repo (2026 account), sometimes with a short AI-tool window. They score communication and incremental design.
What programming languages are allowed in Thoughtworks?
Java, Kotlin, Python, Ruby, JavaScript. Pick one you can pair in.
Is there a cultural fit round?
Yes. Situation-based values. Sometimes it is the last round with no extra HR.
Any pro tip for Thoughtworks placement preparation?
Explain while you code. Pair weekly. Finish three HackerRank problems. Write four STAR values stories.
Where can I read real interview experiences?
Thoughtworks interview experience, GFG GAD Dec 2024, and the 2026 Medium Associate Developer post.
Thoughtworks vs Publicis Sapient vs EPAM for freshers?
Thoughtworks: strictest pairing and values. Publicis Sapient: coding + Core Values. EPAM: more volume coding. Prep DSA for all; add live pairing for Thoughtworks.
Do I need TDD experience before applying to Thoughtworks?
You do not need a production TDD job. You do need to show incremental delivery: an example first, a small passing slice, then a rename. Practise that in weekly pair katas. Buzzword SOLID without smaller methods will not help.
Thoughtworks - recent candidate experiences
Full write-ups stay on interview experience.
What to steal this week
Steal: 75-minute 4-problem mocks; weekly pairing; four values stories; one SQL join.
Ignore: silent LeetCode only; treating cultural fit as HR fluff; listing five languages.
If you only do three things: time four problems, pair one kata out loud, record one values story.
Campus GAD, 7 Dec 2024 (GFG)
PPT, then HackerRank 4/75. Pair from scratch. Tech 1h (projects, tree, LL, SQL). Cultural fit situational. 175 → 19 → 8 → 2 selected for Graduate Application Developer. Takeaway: pairing and values delete as many people as the OA.
Source: GFG Thoughtworks GAD.
Associate Developer, 2026 (Medium)
HackerRank, then pair on an existing repo, AI tools in the last 15-20 minutes, two-interviewer tech, leadership/cultural fit, no separate HR. Selected. Takeaway: practise repo navigation and honest AI use, not only blank-file katas.
Source: Medium, Niranjan N R.
What selected vs rejected patterns look like
Helped: three complete OA solutions; talking while typing; asking clarifying questions; specific Why Thoughtworks.
Hurt: four partials; silent pairing; brochure values; empty GitHub.
Thoughtworks vs Publicis Sapient vs EPAM
All three mix consulting and engineering. Thoughtworks is the pairing specialist. Sapient has Core Values after a coding test. EPAM is a broader coding funnel. If you can pair, sit Thoughtworks. If you can tell STAR stories but hate shared editors, Sapient may fit better.
More narratives: Thoughtworks interview experience.
Similar companies
EPAM · Nagarro · Publicis Sapient · Globant · Zoho