TCS NQT hiring maps your test score to Ninja, Digital, or Prime, then runs a fundamentals-and-projects interview (often one panel with TR, MR, and HR). Notes below are from public 2024-2025 candidate reports.
Round-wise process at a glance
Round
Typical format
What clears you
NQT Foundation (~75 min)
Numerical, Logical, Verbal timed subsections
Enough correct across sections; do not sink all time on quant
NQT Advanced
Advanced aptitude + coding (often 1 easy + 1 medium; ~7 hidden tests each on some papers)
Full AC on easy; partials on medium still help banding
Candidate profile: Priority college campus; mapped to Prime after NQT. Single sitting with Technical, Managerial, and HR panelists. Verdict in report: Selected Prime (~9 LPA).
NQT
Timed aptitude + coding on TCS Ion / NextStep flow
Prime mapping after clearing NQT (campus-specific)
Technical panel
Most recent project (Kaggle ML): explain, imbalanced data handling, logistic regression vs KNN, draw data-flow architecture on paper
Solo vs team preference
Java: polymorphism definition + write runtime polymorphism example
Exception handling: try/catch - interviewer prompted for finally; when finally is mandatory (file open/close)
Collections; insert a node in the middle of a LinkedList (code)
Java Stream API (candidate did not know - panel noted it)
Managerial panel
Family; why TCS; what if Cognizant offered double salary?
Stay 40 years?; what if no ML projects assigned?
Any location; Australia same salary?; night shifts; 4:30 a.m. start?
How do you prioritise work?
HR panel
Ongoing online degree conflict?
If offered Ninja/Digital instead of Prime, accept or keep shopping?
Upgrade process awareness; rate interview /10
Separate briefing on bond/policy after panel
Final result: Prime offer
Takeaways
What decided it: Prime panels still grill Java/SQL fundamentals. Honest “I don’t know Stream API” beat bluffing. Location and shift flexibility are heavily probed.
Common fail: Inconsistent relocation/shift answers or bluffing basics
How to practise: NQT timed sections; OOP/SQL flashcards; rehearse bond/location answers
Technical interview experience 2 - Ninja / Digital patterns (2024-2025)
Technical interview experience 2
Candidate profile: Composite of Ninja 3.3 LPA Phase-2 and Digital/Prime GFG reports.
NQT Foundation (example timings)
Numerical 25 min / ~20 Q; Logical 25 min / ~20 Q; Verbal 25 min / ~25 Q
Advanced coding examples
Easy if-else - all tests pass
Medium subarray sum - partial (e.g. 3/7) still common
Other reports: control-flow easy + medium-hard advanced coding
TR / MR questions reported across drives
OOP four pillars; abstract class vs interface; virtual keyword (C++); constructors/destructors; operator overloading
Java: JDK/JRE/JVM; == vs === if JS on resume; var/let/const; closures; DOM; async
SQL: primary/super/candidate keys; INNER/LEFT/RIGHT/FULL joins; cross join; normalisation; GROUP BY aggregates; UPDATE employee name
Coding: reverse string; print primes; binary search (prerequisites, negative indexes); frequency count; pattern print; Dijkstra/Kruskal at high level
Git/GitHub commands when GitHub appears on resume
Project role, frontend flow, Node.js steps if listed
HR
Why TCS; relocation; night shifts; document verification
Takeaways
What decided it: Ninja interviews still expect live SQL and OOP. Digital/Prime add deeper project and language follow-ups. Advanced coding section is the banding lever.
Common fail: Inconsistent relocation/shift answers or bluffing basics
How to practise: NQT timed sections; OOP/SQL flashcards; rehearse bond/location answers
Candidate profile: Final-year CSE; NQT at a priority institute (~500-600 appeared, ~85 interviewed); shortlisted Digital (higher NQT cutoff than Ninja). In-person at TCS premises same day.
Day logistics
Reporting ~9:00 AM; interview ~5:00 PM after queueing
Three rounds same day: Technical (~25-30 min), Managerial, HR (~10-15 min)
Result ~2-3 weeks later; selected System Engineer Digital (Grade C1)
Technical panel
Programming fundamentals and language concepts tied to resume
Candidate profile: Composite of 2025-2026 Ninja reports where NQT form domain (e.g. Cloud) steered the panel; strict document verification at gate.
Before the panel
NextStep profile completion, then interview slot mail
Strict doc check: semester marksheets, domicile, application vs Aadhaar name match, two resume copies
Mismatch between portal data and ID can stop you before TR
Technical / MR themes
Internship deep-dive; other offers (answer without arrogance)
Domain follow-ups when Cloud/AI selected: Gen AI basics, tools named on resume, willingness to learn Fabric/Azure/AWS if certified
MR: strengths/weaknesses, why hire fresher vs experienced, AI replacing jobs (answer with augmentation, not denial)
Relocation, day/night shifts, five-year goals
Fundamentals still asked
OOP four pillars; SQL joins; TRUNCATE vs DELETE on DBMS follow-ups
C: malloc vs calloc, pointer basics when C appears on resume
~20-22 minute combined panel reported; calm tone helped
Takeaways
What decided it: Domain selection on NQT can narrow questions - revise what you claimed. Fundamentals still appear even on Cloud-tagged interviews.
Common fail: Inconsistent relocation/shift answers or bluffing basics
How to practise: NQT timed sections; OOP/SQL flashcards; rehearse bond/location answers
HR interview experience
HR interview experience
Highest-frequency prompts from recent reports:
Why TCS (and why not a peer IT services firm at higher pay)?
Any location / night shift / early morning shift?
Family background; higher studies plans
Accept lower band (Ninja/Digital) if offered?
Rate yourself; questions for the panel
Tip: Back “learning growth” with a concrete TCS programme or senior anecdote - panels push on generic answers.
Sample answers for high-frequency questions
Q. Four pillars of OOP. A. Encapsulation (bundle state + methods; hide internals), Abstraction (expose essentials via abstract class/interface), Inheritance (reuse/extend behaviour), Polymorphism (one interface, many implementations - overload compile-time, override run-time).
Q. Abstract class vs interface. A. Abstract class can hold state and constructors and mix concrete/abstract methods; single inheritance. Interface is a capability contract; multiple implementation; no instance fields (modern Java: default/static methods). Use abstract class for shared is-a code; interface for shared can-do.
Q. SQL: students per department. A.SELECT department, COUNT(*) AS cnt FROM students GROUP BY department; Know PRIMARY KEY vs UNIQUE and INNER vs LEFT JOIN definitions cold.
Q. When must you use finally? A. To release resources (close files, connections) whether an exception occurred or not. try-with-resources is preferred in modern Java; mention both.
Q. Binary search prerequisites. A. Random-access sorted data (usually ascending). Does not apply to unsorted arrays without sorting first. Clarify index conventions with the interviewer before coding.
Q. TRUNCATE vs DELETE? A. DELETE is DML, row-by-row, can use WHERE and roll back in a transaction. TRUNCATE is DDL, wipes all rows fast, usually no rollback, resets identities. DROP removes the table object.
Q. malloc vs calloc? A. Both heap-allocate; calloc zero-fills n × size bytes, malloc leaves garbage until you write. Always NULL-check and free.
Q. Night shifts / higher studies (MR+HR). A. Shifts: honest flexibility for global clients, or state constraints early. Studies: disclose online degrees; avoid signaling immediate full-time MBA exit after ILP.
Dense prep checklist
Finish Foundation without over-investing in one subsection
Advanced coding: one full AC mandatory mindset for Digital/Prime hopes
Sheet: OOP + SQL joins/keys + one language deep (Java or C++)
Project architecture drawable in 3 minutes
Script flexible location/shift answers without sounding rehearsed
Tips from successful candidates
NQT tips
Drill sectional timers; do not sink all time on one quant block
Template I/O in your language; aim for one full coding AC
Interview tips
Own every resume line; say “I don’t know yet” over bluffing
Match prep to your form language medium (e.g. Core Java)
Band tips
Answer relocation/shift questions directly and consistently
Keep coding warm if Digital/Prime upgrade paths open
These links are research inputs we used to map round structure and recurring questions - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways for TCS.
