The TCS interview is a volume game unlike almost anything else in tech. As India's largest IT services recruiter, TCS hires freshers by the tens of thousands each cycle, and the process is built to sort that flood into bands rather than grill any one person for hours. Most candidates meet it through the TCS National Qualifier Test (NQT), an online aptitude and coding exam that acts as the gateway, and your score there quietly decides which package you are even interviewed for.
Those bands matter more than the job title. Candidates report three fresher tracks, Ninja (the base package), Digital, and Prime (the highest, with one report citing around 12 LPA), and the NQT largely sorts you between them before you meet a panel. One person was told plainly that a weak NQT was why they got Ninja rather than something higher, and being interviewed for one band then offered a lower one is common; several describe being asked mid-interview whether they would accept Digital or Ninja.
The interview itself is usually a single walk-in or campus session folding the Technical, Managerial (MR) and HR rounds into one sitting, sometimes across three panels and sometimes with one or two people covering all three. Freshers get a technical round built on OOPs, DBMS, SQL and a coding problem or two; experienced and lateral hires report far heavier sessions on system design, cloud and framework internals. Prime and Digital interviews are often short, ten to twenty-five minutes in several reports.
Two things catch people off guard: the logistics and the wait. Walk-in drives mean physical resumes, photocopies of your Aadhaar and PAN, passport photos, and hours in queues; results then crawl through the NextStep and iBegin portals, often stuck on 'Candidate Batched' for weeks, so silence after a good interview is normal. This guide breaks down each stage and the questions candidates reported.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksThe interview process, round by round
- TCS National Qualifier Test (NQT) Online test
The gate for almost all fresher hiring: an aptitude and coding test. How you score heavily influences which band you are shortlisted for, and missing the cutoff means no interview at all. One candidate was told a weak NQT was why they landed Ninja rather than a higher band.
- Technical Round (TR) In person
Opens with a self-introduction and a walk through your projects, then drills into fundamentals: OOPs (the four pillars, inheritance and the rest), DBMS topics like normalization and keys, live SQL, and one or two coding problems, sometimes typed and sometimes on paper. Everything on your resume is fair game.
- Managerial Round (MR) Often back-to-back with TR and HR
Situational and behavioural probing: strengths and weaknesses, a scenario question, your family, and the occasional deliberately tricky question to test composure. For Prime, one candidate was told communication counts here as much as the technical answers.
- HR Round Usually the same day
The fit-and-logistics round: willingness to work any shift, relocation (one candidate was asked point blank about moving to Delhi), and questions about your family. Often short, and run straight after the MR, sometimes with the same panel.
- One candidate's deep-dive interview Deep dive
One candidate's session went far beyond what TCS's reputation suggests: framework internals (FastAPI, ASGI versus WSGI, SQLAlchemy, pydantic), designing a service in OOPs then rewriting it as API endpoints on paper, rate limiting and idempotency, Kafka, cloud and Kubernetes (S3 or blob storage, EKS, pods, ingress and egress), Docker image optimisation, and a full Flipkart system-design question that ran into sharding and replication. They were rejected.
Interview questions candidates report
TCS NQT (aptitude and coding)
- Aptitude: numerical and quantitative ability, logical reasoning, verbal ability
- Programming-logic questions on pseudocode, output prediction and complexity
- Hands-on coding where working, compiling code is expected
- Common patterns: climbing-stairs / ways to reach the nth step, Fibonacci, pattern printing
OOPs, DBMS and core CS
- The four pillars of OOPs (inheritance, encapsulation, polymorphism, abstraction) with examples
- SQL query writing: one candidate was given two queries and found the second one complicated
- DBMS normalization and types of keys; array versus linked list use cases
- OS memory management and paging; internet versus intranet
Coding, projects and resume in the interview
- Write two short programs the interviewer dictates, then explain your logic aloud
- Solve a linked-list problem on pen and paper and dry-run a given test case
- Be ready for the panel to revisit the code you wrote in the NQT and re-explain it
- Deep questions on anything on your CV (NumPy drew array-dimension questions; ML draws 'why Random Forest')
Deeper technical questions (one candidate's report)
- Framework internals: FastAPI, pydantic, OAuth2, ASGI versus WSGI, SQLAlchemy
- Design a banking service in OOPs, then convert it to API endpoints on paper
- Rate limiting, idempotent endpoints, Kafka; cloud and Kubernetes (S3 or blob storage, EKS, pods, ingress and egress)
- System design (design Flipkart search) plus database sharding and replication
Managerial and HR
- Strengths and weaknesses (pick the weakness carefully; one HR disliked 'procrastination')
- A situational or scenario-based question, plus a curveball to test composure
- Tell me about your family and academic background
- Any-shift working, relocation to named cities, salary expectations and the service bond
What candidates said about the process
This candidate expected a standard services interview and got a staff-level grilling: FastAPI and pydantic internals (ASGI versus WSGI, SQLAlchemy), designing a banking service in OOPs and rewriting it as API endpoints on paper, rate limiting, idempotency, Kafka, AWS and Kubernetes, and finally a full Flipkart system-design question with sharding and replication before a rejection. TCS lateral interviews, they warned, go far deeper than the company's reputation suggests.
Read the candidate's account →A campus candidate explained OOPs with real examples, wrote the two programs the panel asked for (and was told they were correct), and answered everything except one of two SQL queries at the end. Confident of at least the Ninja package, they then found their name against none of the bands when results posted. A recurring TCS frustration: answering the large majority correctly is not always enough at a mass recruiter.
Read the candidate's account →This Prime interview ran about an hour and leaned on pen and paper. The interviewer cut off an AGI tangent, handed over paper, and asked for a linked-list solution with a walk-through of a given test case. It then ranged across OOPs, OS topics like memory management and paging, and web concepts (cookies, sessions, JWT, intranet versus internet) plus an array-versus-linked-list use case. MR and HR followed, and no SQL came up.
Read the candidate's account →Asked to solve a 'ways to reach the nth step' problem (essentially climbing stairs), this candidate could not crack it, then slipped on a simple Fibonacci loop and was told their programming was weak. They were also told a poor NQT was why they were in the Ninja band rather than higher, and the role could mean support or development, not the AI/ML they wanted. HR then covered family, shifts and relocation.
Read the candidate's account →Expecting a small, orderly interview, this experienced candidate found a full walk-in drive hiring for roughly 20 to 25 roles from fresher to fifteen years of experience. The morning was pure logistics: a physical resume, two photocopies each of Aadhaar and PAN, and passport photos, with those short of them queuing at a nearby Xerox shop. The first task was hand-copying resume details onto a paper form.
Read the candidate's account →How to prepare
- Treat the NQT as the real hurdle. Its aptitude and coding score does not just shortlist you, it sorts you into Ninja, Digital or Prime before the interview, and a weak score can cap your offer however well you interview.
- Know OOPs, DBMS and SQL cold. For freshers these come up in almost every write-up: the four pillars with examples, normalization and keys, and writing SQL live. Rehearse explaining them aloud, not just recognising them.
- Defend everything on your resume. Panels pick topics straight off your CV; one candidate who listed NumPy was grilled on array dimensions. If it is on the page, be ready to go three questions deep.
- Practise coding on paper. Candidates were handed a pen for a linked-list or climbing-stairs problem and told to dry-run a test case, so write and trace code by hand, not only in an IDE.
- Prepare the MR and HR properly. Have a real strength, a safe weakness (one HR disliked 'procrastination'), a situational story, and honest answers on shifts, relocation and the bond. For Prime, communication is scored alongside the tech.
- Expect chaos and a long wait. Walk-in drives mean queues, photocopies (Aadhaar, PAN, passport photos) and hand-filled forms; results then crawl through NextStep, often stuck on 'Candidate Batched'. Keep applying elsewhere in parallel.
Frequently asked questions
What is the TCS NQT?
The National Qualifier Test is TCS's online entry exam and the gateway to almost all fresher hiring: an aptitude section (numerical, verbal and logical reasoning), a programming-logic section and hands-on coding. Your score heavily influences whether you are shortlisted for the Ninja, Digital or Prime band.
What is the difference between TCS Ninja, Digital and Prime?
They are hiring bands, largely sorted by NQT performance: Ninja is the base package, Digital sits above it, and Prime is the highest (one candidate cited around 12 LPA). Candidates are sometimes interviewed for a higher band and offered a lower one, so being asked mid-interview whether you would accept Digital or Ninja is common.
How many rounds is the TCS interview?
After the NQT, most candidates face a Technical Round, a Managerial Round (MR) and an HR round, often the same day and sometimes with one panel covering all three. Prime and Digital interviews can be very short, ten to twenty-five minutes, while experienced and lateral interviews run an hour or more.
What technical questions does TCS ask freshers?
The most reported are the four pillars of OOPs with examples, DBMS topics like normalization and types of keys, live SQL query writing, and one or two coding problems (often on paper) such as a linked-list task or the climbing-stairs problem. Expect deep questions on anything on your resume.
Is the TCS interview hard for experienced candidates?
It can be far tougher than the company's reputation suggests: framework internals, designing and coding a service on paper, rate limiting and idempotency, Kafka, cloud and Kubernetes, and full system design (one candidate designed Flipkart, then fielded sharding questions). Prepare as you would for any senior engineering loop.
How long does TCS take to share results?
Often weeks, and the silence is not necessarily bad news. Candidates track status on the NextStep and iBegin portals, where it frequently sits on 'Candidate Batched' long after the interview. Friends interviewed the same day sometimes get offers first, so a delay on your side does not always mean rejection.
TCS will ask its own version of these. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions