Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

3 stories

Likes earn the author +10 XP for the first 3 likes each day

ThoughtWorksFull Stack Engineer
Reported Jul 2026

ThoughtWorks Full Stack Engineer interview cancelled before it began

I applied and had an interview scheduled about a week ahead, which made it feel like a real opportunity. I was surprised by how quickly it moved. Then, the day before the interview, I received a generic rejection saying I was not a good fit. That did not feel consistent with the criteria they stated publicly. I had compared my resume with the job description using an ATS match and received a stro…

Rejected0
ThoughtWorksSoftware Engineer
Reported Jul 2026

ThoughtWorks Software Engineer interview: pair programming, logging and production incidents

The recruiter screen was supportive and gave me enough detail to understand what the interviewers would look for. Scheduling took some time. Once the interviews began, the process felt focused on technical reasoning and how I thought while working with someone else. In pair programming, I had to explain my approach as I coded. We worked on clean code, problem-solving communication and design deci…

Technical Screen0
ThoughtWorksSoftware Engineer
Reported Jul 2026

ThoughtWorks Software Engineer interview experience

After a recruiter conversation, I went directly into a coding-focused process. There was a take-home code challenge on clean code, object-oriented thinking, and testing. When I finished, a pairing-style round asked me to show how the solution fit the current design and explain the full flow rather than simply hand over code. It was moderately difficult because working code was not enough. I also…

Take-home Project0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP