Interview Experiences

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

Share yours, earn XP

5 stories

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

TCSSystems Engineer
Reported Jul 2026

TCS Systems Engineer interview: priority NQT and Java-focused Prime interview

I went through an on-campus priority NQT process. I had to solve two coding questions before reaching the Prime interview, so the NQT felt like a gatekeeper. The technical interview focused mostly on Java, especially Java OOP, Spring Boot, and SQL. There was also an expectation that I could code through multiple test cases. The process did not rely only on theory. It put weight on solving enough…

Technical Screen0
TCSSoftware Engineer
Reported Jul 2026

TCS Software Engineer Interview Experience: long onsite technical and SQL day

I waited in a hall while candidates were called one at a time, then entered a technical round based directly on my CV. I was asked at least one DSA question, so the interview tested both fundamentals and problem solving. The day was long and exhausting. The format I recall had a technical segment first, followed by coding and SQL queries, and interviewers would help when I got stuck. It ran from…

RejectedOnsite0
TCSSoftware Engineer
Reported Jul 2026

TCS Software Engineer Interview Experience: Long fresher-oriented timeline

After applying online, the TCS process stretched close to 6 to 12 months, though it was organized once underway. It moved from technical coding to an advanced coding/problem-solving round, then a managerial discussion of my technical experience and projects, and finally HR topics: compensation, notice period, policies, and next steps. The NQT exam was important for shortlisting. My listed slot wa…

0
TCSSoftware Engineer
Reported Jul 2026

TCS Software Engineer interview: numeric aptitude questions instead of engineering discussion

My TCS AI interview felt more like a broad numeric and aptitude round than a technical conversation. The mock-test setup mixed numeric and aptitude questions. I kept thinking about the mismatch between what I had prepared from my experience and why so much time went to the numeric part. The questions were straightforward enough, but the flow did not feel connected to actual engineering work. Ever…

Other0
TCSSoftware Engineer
Reported Jul 2026

TCS Software Engineer interview: incomplete AVL tree and a Digital-role offer

After the recruiter call, I sat for the TCS Prime interview. It was focused and structured, lasting about 40 to 50 minutes. It covered DSA, core programming, my projects, and Python OOP. The technical section began with an AVL-tree coding task. I had to build an AVL tree from scratch with insert, delete, search, and LL, RR, LR, and RL rotations. I could not finish the implementation completely, a…

OfferTechnical Screen0

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