IT Services · Campus Placement · Mumbai
TCS Hiring 2026 for campus and off-campus freshers — eligibility, FY27 intake context, NQT Foundation/Advanced pattern, Ninja/Digital/Prime salary bands, interview questions, resume tips, how to apply, and a 30-day preparation plan.
TCS Hiring 2026 Roadmap
Intake shape, AI-skilled hiring, rolling NQT windows, and Verbal Ability revisions — what changed going into mid-2026.
TCS is trending toward approximately 25,000 fresher seats for FY27, down from around 44,000 onboarded in FY26 — competition per seat is meaningfully higher.
TCS leadership has stated that roughly 60% of FY26 fresher hires had demonstrable AI skills (vs ~10–15% a few years earlier). Digital and Prime panels commonly expect an AI or data-related project discussion.
NQT 2026 windows have opened on a rolling basis for 2024–2026 batches (officially spanning a wider 2021–2027 pass-out range). Check the live TCS NQT portal rather than a remembered “last date.”
The Verbal section now includes Sentence Completion, Passage Recall, and Email Writing — older vocabulary-only question banks are incomplete prep.
BSc, BCA, and BCom graduates use a different NQT variant from the BE/B.Tech/MCA track — registering for the wrong variant is a common avoidable mistake.
| Update | What it means for you |
|---|---|
| Lower FY27 intake (~25,000 vs ~44,000) | Apply earlier in the cycle; don’t wait for a “safe” later drive |
| ~60% AI-skilled fresher hires | Have at least one AI/ML or data project ready for Digital/Prime |
| Rolling NQT registration windows | Recheck the official portal — third-party deadlines go stale fast |
| Revised Verbal Ability syllabus | Practice Email Writing and Passage Recall, not just vocabulary |
Fresher intake context (illustrative)
Higher competition per seat — apply earlier; figures are directional from public hiring commentary.
Warning: do not rely on a “last date to register” from a third-party site months ago. Always cross-check the live date on the official TCS NQT registration portal.
What is the TCS NQT and what sections does it cover?
Expert answer: TCS National Qualifier Test is the primary online screening for campus and off-campus TCS hiring in India. It typically has four scored sections: Verbal Ability, Reasoning Ability, Numerical Ability, and Programming Logic — with an additional coding section for Digital and Prime track aspirants. Your composite percentile and section-wise cutoffs determine whether you qualify for Digital (UG ₹7.09–8.04 LPA) or Prime (UG ₹9.09–9.30 LPA; PG up to ₹11.80 LPA) bands. I treat NQT as a gate: clearing the top band unlocks higher package tracks and tougher downstream technical rounds.
What interviewers evaluate: Whether you understand TCS entry mechanics, NQT section structure, and how scores map to offer bands — not vague “aptitude test” answers.
Answer strategy: Define NQT, list all five areas (verbal, reasoning, numerical, programming logic, coding), then connect percentile bands to Digital/Prime/Ninja tracks.
Common mistakes: Omitting Programming Logic, confusing NQT with only aptitude, or unable to explain how track selection works.
Follow-up questions:
What is the difference between TCS Digital and TCS Prime? Which one should you target?
Expert answer: TCS Prime (UG ₹9.09–9.30 LPA; PG ₹11.50–11.80 LPA) is the premium fresher band for top NQT performers — roles focus on technical specialist tracks, lead projects, and mentorship. TCS Digital (UG ₹7.09–8.04 LPA; PG ₹7.39–8.04 LPA) targets solid aptitude and basic OOP/CS fundamentals with roles in full stack, cloud, AI/ML, and big data. I target Prime only if mock NQT scores and timed coding practice consistently hit Digital/Prime cutoffs; otherwise I optimize for Digital to avoid overcommitting to DSA at the expense of aptitude.
What interviewers evaluate: Realistic self-assessment, awareness of package bands, and a prep strategy aligned to your current skill level.
Answer strategy: State UG/PG CTC bands for Digital and Prime, contrast target roles (full stack/cloud vs technical specialist), and give a decision rule based on mock scores.
Common mistakes: Quoting outdated ₹4.5/₹7 LPA figures, claiming Prime without coding evidence, or ignoring aptitude weight in NQT.
Follow-up questions:
Explain the concept of polymorphism with a real-world example.
Expert answer: Polymorphism means one interface, many implementations. Compile-time polymorphism is method overloading — same method name, different parameters. Runtime polymorphism is method overriding — a subclass provides its own version of a parent method. A practical example: a PaymentProcessor interface with processPayment() implemented by CreditCardPayment, UpiPayment, and NetBankingPayment. The billing service calls processPayment() without knowing the concrete type — new payment methods can be added without changing client code. This is how TCS interviewers expect you to connect OOP theory to extensible system design.
What interviewers evaluate: OOP fundamentals with clarity on compile-time vs runtime polymorphism and a concrete, production-style example.
Answer strategy: Define both polymorphism types briefly, then walk through payment-gateway or notification-dispatcher example with interface + overrides.
Common mistakes: Only giving animal/dog/cat analogy, confusing overloading with overriding, or skipping real-world mapping.
Follow-up questions:
Write a program to find the second largest element in an array without sorting.
Expert answer: I use a single-pass approach with two variables: max and secondMax, both initialized to negative infinity (or first two elements handled explicitly). For each element, if it exceeds max, shift old max to secondMax and update max; else if it is greater than secondMax and not equal to max, update secondMax. Time O(n), space O(1). Edge cases: array length < 2, all elements equal (no second largest), duplicates where max appears multiple times. I narrate the logic aloud while coding — TCS panels value clean edge-case handling over clever one-liners.
What interviewers evaluate: Array traversal fluency, complexity awareness, and disciplined edge-case handling under interview pressure.
Answer strategy: State O(n)/O(1) upfront, write the two-variable loop, then verbally list edge cases before the interviewer asks.
Common mistakes: Sorting first (O(n log n)), mishandling duplicates, or crashing on arrays with fewer than two distinct values.
Follow-up questions:
What is a deadlock? How would you prevent it in a multi-threaded application?
Expert answer: Deadlock occurs when two or more threads block forever, each waiting for a resource held by another. All four Coffman conditions must hold: mutual exclusion, hold-and-wait, no preemption, and circular wait. Prevention strategies: acquire locks in a global consistent order, use tryLock with timeouts, minimize lock granularity, and prefer higher-level concurrency utilities (java.util.concurrent) over raw synchronized blocks. In Java services, I also avoid nested locks on different objects and use thread dumps to diagnose circular wait in production incidents.
What interviewers evaluate: Concurrency literacy — can you name Coffman conditions and give practical prevention, not just a textbook definition.
Answer strategy: Define deadlock → list four conditions → give two prevention tactics (lock ordering + timeout) with a brief Java example.
Common mistakes: Missing one Coffman condition, suggesting “just use more threads,” or no concrete prevention mechanism.
Follow-up questions:
What are the main differences between SQL and NoSQL databases? When would you use each?
Expert answer: SQL databases are relational, schema-first, and ACID-compliant — ideal for structured data with joins and transactional integrity (banking, orders, HR records). NoSQL databases (document, key-value, column, graph) trade strict schema and joins for horizontal scalability and flexible payloads — useful for session stores, logs, catalogs, and high-write telemetry. I choose SQL when consistency and complex queries matter; NoSQL when scale, schema evolution speed, or denormalized access patterns dominate. TCS interviewers often follow up with a scenario: “Would you store user profiles in MongoDB or PostgreSQL?” — justify with access pattern, not hype.
What interviewers evaluate: Data modeling judgment and ability to match database type to workload requirements.
Answer strategy: Contrast schema, consistency, scaling model; give one SQL use case and one NoSQL use case with reasoning.
Common mistakes: Claiming NoSQL is always faster, ignoring ACID needs, or unable to name a concrete use case for each.
Follow-up questions:
Tell me about a time you worked under a tight deadline and how you managed it.
Expert answer: During my final-year major project, our demo date moved up by four days after a scope change. I listed all deliverables, classified them as must-have vs nice-to-have with my team lead, and focused on a thin vertical slice: login, core workflow, and one report. I sent progress updates every evening, escalated a blocker on API integration on day one, and paired with a teammate on testing. We shipped the demo on time with zero critical bugs and deferred analytics to the next sprint. TCS values structured prioritization and proactive communication — not heroics or last-minute all-nighters alone.
What interviewers evaluate: STAR storytelling, prioritization under pressure, and team communication maturity.
Answer strategy: Use STAR with specific timeline, your prioritization framework, stakeholder updates, and measurable outcome.
Common mistakes: Vague team stories, no trade-offs mentioned, or framing success as working overnight without a plan.
Follow-up questions:
What is the difference between process and thread? How does context switching work?
Expert answer: A process is an independent program execution unit with its own virtual memory space, file descriptors, and OS resources tracked in a PCB. A thread is a lighter execution unit within a process that shares the process heap and open files but has its own stack and registers (TCB). Context switching saves CPU register state and switches execution; for threads it is faster because address space does not change — only thread-local state is swapped. Multithreading improves throughput for I/O-bound work but introduces race conditions requiring synchronization.
What interviewers evaluate: OS fundamentals — memory isolation, shared state risks, and context-switch cost reasoning.
Answer strategy: Contrast memory model first, explain PCB vs TCB, then why thread context switch is cheaper than process switch.
Common mistakes: Saying threads have separate memory spaces, or describing context switch without mentioning saved register state.
Follow-up questions:
Why do you want to join TCS over other IT companies?
Expert answer: I want to join TCS because of its scale as one of the world’s largest IT employers, structured fresher development through ILP, and platforms like Fresco Play for continuous upskilling. TCS’s global delivery footprint means early exposure to enterprise clients and diverse tech stacks — which fits my goal of building production discipline before specializing. I have researched their campus programs and am drawn to the stability, mentorship density, and certification paths (cloud, architecture) that support long-term growth — not just brand recognition.
What interviewers evaluate: Company research depth, genuine motivation, and fit for IT services career path — beyond generic answers.
Answer strategy: Three pillars: scale + training (ILP/Fresco Play), project exposure, alignment with your 2–3 year skill goals.
Common mistakes: Generic “brand name” answers, incorrect facts about TCS programs, or only mentioning salary.
Follow-up questions:
Explain normalisation in databases. What are 1NF, 2NF, and 3NF?
Expert answer: Normalisation reduces redundancy and update anomalies by decomposing tables based on functional dependencies. 1NF: atomic column values, no repeating groups, unique rows. 2NF: 1NF plus no partial dependency — non-key attributes must depend on the whole composite primary key. 3NF: 2NF plus no transitive dependency — non-key attributes depend only on the primary key, not on other non-key columns. Example: Student(CourseID, StudentID, Grade, InstructorName) violates 3NF if InstructorName depends only on CourseID — split into StudentGrade and CourseInstructor tables.
What interviewers evaluate: DBMS design literacy — can you define each normal form and demonstrate with a concrete decomposition.
Answer strategy: One sentence per normal form, then walk a Student/Course table through violations and fixes step by step.
Common mistakes: Memorizing definitions without examples, confusing 2NF partial dependency with 3NF transitive dependency.
Follow-up questions:
What is your understanding of Agile methodology and how does it differ from Waterfall?
Expert answer: Waterfall is sequential: requirements → design → implementation → testing → deployment, with scope locked early. Agile is iterative: work ships in short sprints with continuous stakeholder feedback and changing requirements welcomed late. Scrum adds roles (Product Owner, Scrum Master), ceremonies (sprint planning, daily standup, retrospective), and artifacts (backlog, increment). TCS uses Agile on most client delivery — I mention that I am comfortable with sprint demos, backlog grooming, and adapting when priorities shift mid-sprint.
What interviewers evaluate: Software delivery methodology awareness and readiness for client-project Agile environments.
Answer strategy: Contrast planning rigidity vs iteration, name Scrum ceremonies, connect to TCS delivery context.
Common mistakes: Equating Agile with “no documentation,” or unable to name a single Scrum ceremony.
Follow-up questions:
Where do you see yourself in five years, and how does TCS fit into that plan?
Expert answer: In five years I see myself as a confident IT Analyst or Assistant Consultant with strong delivery on at least one enterprise domain — having earned relevant certifications through TCS’s learning ecosystem (cloud, architecture, or a specialization aligned to my project). Short term, I want to master fundamentals on ILP, contribute reliably on client sprints, and build communication skills for stakeholder calls. TCS fits because it offers structured career tracks, global project exposure, and certification support that maps to my goal of becoming a solution-oriented engineer, not jumping roles every year.
What interviewers evaluate: Long-term planning realism, alignment with TCS career ladder, and commitment signal without overpromising.
Answer strategy: Anchor to TCS tracks (Associate → IT Analyst → Assistant Consultant), mention certifications, show 1-year and 5-year milestones.
Common mistakes: Saying “CEO in five years,” vague ambitions, or a plan that implies leaving TCS immediately after skilling up.
Follow-up questions:
What each interview round probes
Check eligibility before you spend hours on NQT prep — this filter is applied before registration completes, and backlog rules tightened for 2026.
| Requirement | Detail |
|---|---|
| Minimum aggregate | 60% (or 6 CGPA) in Class X, Class XII, Diploma (if applicable), Graduation, and Post-Graduation (if applicable) |
| Eligible degrees | BE / B.Tech / ME / M.Tech / MCA / M.Sc (and BSc/BCA/B.Com under TCS Smart Hiring via a different NQT variant) |
| Eligible batches | 2024, 2025, and 2026 graduating batches (officially spanning 2021–2027 pass-outs) |
| Academic gap | Maximum one-year gap generally accepted; more than two years of cumulative gap across academics is typically disqualifying |
| Backlogs | No active/standing backlogs at joining; for 2026, more than one active backlog at application can disqualify at verification even after clearing NQT |
| Age limit | Generally 18–28 years (some drives cite a narrower band — verify on the specific posting) |
| Prior TCS history | No active TCS application or prior TCS employment within roughly the last 9–12 months |
| Experience | Freshers or candidates with up to ~2 years of prior experience via the NQT route |
Eligibility checklist
One NQT gateway sorts candidates into Ninja, Digital, or Prime — then interviews and verification. Pair this guide with our placement interview guide and practice with AI mock interviews.
Selection process — four stages
Apply via the official TCS NQT portal (or campus placement cell) with accurate academic percentages — these are verified later, so don’t round up. Select the correct variant (Ninja/Digital/Prime track vs Smart Hiring).
One gateway test on the TCS iON platform. Foundation covers Numerical, Verbal, and Reasoning. Advanced adds higher-difficulty quant/reasoning plus coding (typically 2 problems). Combined performance sorts you into Ninja, Digital, or Prime — there is no separate “Digital exam.”
CS fundamentals (OOPs, DBMS/SQL, OS, CN), your primary language, and a walkthrough of resume projects. Digital/Prime rounds go deeper and may include live coding or an AI/data project discussion.
Communication, relocation flexibility, bond/service-agreement awareness, and behavioural fit. Some drives (especially Ninja) combine Technical and HR into one panel — don’t assume a fixed round count.
Document verification (percentages, backlog status, ID) followed by offer letter with CTC breakdown, joining date, ILP/training details, and service-agreement terms. Confirm fixed vs variable and bond terms before accepting.
TCS Hiring Process 2026
Role-specific loops: TCS Software Engineer, TCS Java Developer, and Infosys interviews.
The National Qualifier Test is one test with two parts — not separate Digital or Prime exams. Verbal Ability now includes Email Writing and Passage Recall. Use the AI Question Generator for fresh Advanced coding practice prompts.
NQT exam pattern flow
| Section | Focus Area |
|---|---|
| Foundation — Numerical Ability | Quantitative aptitude, arithmetic, data interpretation |
| Foundation — Verbal Ability | Sentence Completion, Passage Recall, Email Writing |
| Foundation — Reasoning Ability | Logical reasoning, pattern recognition, puzzles |
| Advanced — Quant & Reasoning | Higher-difficulty aptitude and multi-step logic |
| Advanced — Coding | Typically 2 problems with live compilation + hidden tests |
TCS updates exam formats periodically. Always verify the latest NQT pattern on the official portal before applying. Percentile cut-offs are cohort-specific and not officially published.
Now includes Sentence Completion, Passage Recall, and Email Writing alongside classic grammar and RC-style work. Ignoring Verbal because “it’s not coding” still hurts combined percentile.
Prep tip: Practice short professional emails and Passage Recall drills weekly — not vocabulary lists alone.
Percentages, ratios, time-speed-distance, profit-loss, averages, interest, and data interpretation. Campus NQT papers are time-pressured — mental math shortcuts save minutes.
Prep tip: Drill 30 timed quant questions daily in Weeks 1–2 of your prep plan.
Blood relations, seating arrangements, syllogisms, coding-decoding, series, and direction sense. Accuracy here separates higher-track shortlists from mass cuts.
Prep tip: Practice 15 reasoning sets under 20-minute clocks; learn diagram notation for arrangements.
Higher-difficulty versions of Foundation topics plus probability, permutations & combinations, and multi-step puzzles. Required for Digital/Prime — optional in spirit for Ninja but still affects combined score.
Prep tip: Don’t neglect Foundation accuracy while chasing Advanced difficulty — placement uses a combined score.
Typically 2 problems with live compilation evaluated against hidden test cases — one easier (arrays/strings) and one harder (recursion / basic DP / structure manipulation). Edge cases (empty input, duplicates, negatives) matter.
Prep tip: Solve under a strict timer; the second coding question is where many Digital/Prime-capable candidates lose the band.
Illustrative composite of NQT and technical round weighting across campus drives — use our DSA topic map for coding depth after aptitude is secure.
Illustrative topic importance (NQT + technical + HR)
TCS runs one NQT and slots you into three fresher bands. Your combined Foundation + Advanced performance — not a separate exam — determines the track.
One NQT → three tracks
*Ninja CTC is candidate-reported — confirm on offer letter.
| Track | Approx. CTC (UG) | NQT bar | Typical work |
|---|---|---|---|
| Ninja | ₹3.36–4.5 LPA* | Foundation clear | App maintenance, testing, BA support |
| Digital | ₹7.0–8.0 LPA | Foundation + strong Advanced | Cloud, IoT, digital engineering |
| Prime | ₹9.09–11.8 LPA | Top-percentile Advanced | AI/ML, R&D, architecture, high-value clients |
Prioritize clearing Ninja comfortably over gambling everything on Advanced. A confirmed Ninja offer beats a missed Digital attempt.
Digital is a realistic 3–4 week Advanced-section target — keep Foundation accuracy high while you push coding.
Prime is worth the extra prep — but don’t let Foundation slip; combined score still decides the band.
Salary is the most-searched part of TCS hiring — and the part where third-party sources disagree most. Figures below mix official hiring-page bands (Digital/Prime) with clearly labeled candidate-reported estimates (Ninja).
Fresher CTC bands (illustrative)
| Track | Approx. CTC | Approx. in-hand (monthly) | Target roles & focus |
|---|---|---|---|
| Ninja | ₹3.36–4.5 LPA* | ~₹22,000–25,000 | Enterprise maintenance, testing, BA support |
| Digital | ₹7.0–8.0 LPA (UG) | ~₹45,000–50,000 | Full stack, cloud, IoT, digital engineering |
| Prime | ₹9.09–9.30 LPA (UG) · up to ~₹11.59–12.26 LPA (PG) | ~₹55,000–75,000 | AI/ML, R&D, architecture, high-value clients |
| Dimension | Ninja | Digital | Prime |
|---|---|---|---|
| Approx. CTC (UG) | ₹3.36–4.5 LPA* | ₹7.0–8.0 LPA | ₹9.09–9.30 LPA |
| Approx. CTC (PG) | Slightly above UG band | Slightly above UG band | Up to ~₹11.59–12.26 LPA |
| NQT requirement | Foundation clear | Foundation + strong Advanced | Foundation + top Advanced |
| Interview depth | Standard technical + HR | Deeper technical / projects | Extended technical; AI/data often expected |
| Typical work | Maintenance, testing, BA support | Cloud, IoT, digital eng. | AI/ML, R&D, architecture |
| Candidate-reported percentile* | ~50th–62nd | ~63rd–82nd | ~83rd+ |
Use these as prep benchmarks across NQT and interview rounds — not as guaranteed cutoffs.
Target
High accuracy across Verbal + Quant + Reasoning
Combined Foundation score still counts toward track placement — don’t abandon it while chasing Advanced coding.
Target
2/2 coding questions whenever possible
Digital and Prime aspirants should solve both problems cleanly with correct edge-case handling under sectional timers.
Target
Strong OOPs, SQL, DBMS, OS + project depth
Narrate answers with examples from projects; Digital/Prime may probe AI/data work and light coding.
Target
Clear communication and bond/relocation clarity
Use STAR format, research ILP/training, and prepare honest “Why TCS?” plus service-agreement answers.
No fixed cutoff is publicly disclosed by TCS. Targets below are preparation benchmarks from campus prep communities — not official thresholds.
Realistic four-week plan assuming coursework or a parallel job search — Foundation first, then Advanced coding, CS fundamentals, and full mocks. Share progress in the InterviewEra Community.
30-day preparation arc
Week 1 (Days 1–7)
Week 2 (Days 8–14)
Week 3 (Days 15–21)
Week 4 (Days 22–28)
NQT and interviews get you hired — but a weak resume can cost a Digital/Prime shortlist look in off-campus volume. Run yours through the ATS Resume Checker before you apply.
Resume bullet — weak vs strong
Built a mental wellness app using MERN stack.
Built and deployed a full-stack mental wellness app (MERN + Socket.io) with an LLM chat assistant, mood analytics, and JWT auth — live on Render/Vercel.
Weak
Built a mental wellness app using MERN stack.
Stronger
Built and deployed a full-stack mental wellness app (MERN + Socket.io) with an LLM chat assistant, mood analytics, and JWT auth — live on Render/Vercel.
Weak
Worked on a group project for expense tracking.
Stronger
Designed a group-expense-splitting tool handling subset-of-group scenarios, reducing manual calculation errors to zero across 20+ trial sessions.
Weak
Familiar with Java, Python, React.
Stronger
Proficient in Java (DSA, OOPs) and React; built 2 deployed full-stack projects using these stacks, both linked on GitHub.
Featured answer: visit the official TCS NQT registration portal, create an accurate academic profile, select the correct hiring variant, schedule and take the online NQT, then proceed to interviews if shortlisted. Candidates often share live window updates in the InterviewEra Community.
Application flow (start)
Full 10-step checklist appears in the How to Apply section.
Your college placement cell coordinates registration and often the first interview round on campus.
Self-register via the official TCS NQT portal — primary route when your college has no active TCS drive. Same NQT and interview bar as campus.
These patterns cause rejections even when candidates know individual topics. Fix them before your NQT slot.
Mistake
Why it hurts: NQT eliminates most applicants before any technical round — strong coders still fail without quant, verbal, and reasoning practice.
How to fix it: Allocate serious Week 1–2 time to timed Foundation sets; Verbal now includes Email Writing and Passage Recall.
Mistake
Why it hurts: TCS campus pipeline is aptitude-first. LeetCode-heavy prep without NQT simulation leaves you unprepared for the actual filter.
How to fix it: Balance daily prep: Foundation timed practice + Advanced coding — not coding alone.
Mistake
Why it hurts: Track placement uses a combined score. Advanced coding without Foundation accuracy often lands lower than expected.
How to fix it: Keep Foundation accuracy high while you push Advanced difficulty.
Mistake
Why it hurts: Generic “TCS is a big company” answers fail panels that test motivation, relocation, and service-agreement clarity.
How to fix it: Prepare 5 STAR stories plus honest answers on bond terms, relocation, and why TCS over peers.
Mistake
Why it hurts: Technical rounds expose gaps in spoken explanations — silent practice hides communication issues.
How to fix it: Run full mocks before NQT: Foundation/Advanced simulation + technical narration + HR round.
Mistake
Why it hurts: NQT requires muscle memory for speed math, revised Verbal tasks, and sectional pacing — cramming one week before fails for most freshers.
How to fix it: Follow the 30-day plan below starting 4 weeks before your drive date.
A minimum of 60% aggregate (or 6 CGPA) is required across Class X, Class XII, Diploma (if applicable), Graduation, and Post-Graduation (if applicable).
The 2024, 2025, and 2026 graduating batches are eligible, with the officially accepted pass-out range spanning 2021–2027.
The core NQT for Ninja/Digital/Prime hiring is free. Separate variant-based tests on the tcsion.com platform (Cognitive, IT, Non-Tech, BFSI) carry a fee of roughly ₹599–999.
All three are entered via the same NQT. Ninja is the base entry track (~₹3.36–4.5 LPA, candidate-reported), Digital requires a strong Advanced-section score (~₹7.0–8.0 LPA), and Prime requires a top-percentile Advanced score (~₹9.09–12.26 LPA), with correspondingly more demanding work at each higher tier.
Yes. You can self-register directly through the official TCS NQT portal regardless of your college’s campus drive status.
Active backlogs at joining are disqualifying. For 2026, more than one active backlog at application can disqualify you at verification even after clearing the NQT.
Two parts: Foundation (Numerical, Verbal, Reasoning Ability) and Advanced (Advanced Quant & Reasoning, Coding, and an optional subject-specific section in some drives). Verbal now includes Sentence Completion, Passage Recall, and Email Writing.
Candidate-reported figures range from ₹3.36 LPA to ₹4.5 LPA. TCS has not published a single fixed official Ninja CTC figure — confirm the exact number in your offer letter.
Approximately ₹7.0–8.0 LPA, with separate UG/PG bands shown on TCS’s official Prime/Digital hiring page.
Approximately ₹9.09–9.30 LPA for 0–1 year UG candidates and about ₹11.59–11.80 LPA (up to ~₹12.26 LPA in some reported PG bands) for 0–1 year PG candidates — confirm on the official hiring page and your offer letter.
Yes — typically a 1-year service agreement across fresher bands, with a financial penalty (commonly cited around ₹50,000) for leaving early. Always verify exact terms in your own offer letter.
Typically a Technical Interview followed by a Managerial/HR Interview. Some drives combine these into a single panel, especially for Ninja-track hiring.
OOPs, DBMS normalization, Operating Systems (process/thread, deadlock), Computer Networks (TCP/UDP), and a deep understanding of your own resume projects — plus AI/data discussion readiness for Digital/Prime.
Not a strict requirement, but Prime-track interviews increasingly expect candidates to discuss an AI or data-related project, reflecting TCS’s shift toward AI-skilled fresher hiring.
Yes. TCS typically allows candidates to hold multiple offers simultaneously; you simply cannot join more than one company.
A separate hiring funnel for BSc, BCA, and B.Com graduates, using a different NQT variant from the BE/B.Tech/MCA track.
FY27 intake is trending toward roughly 25,000 seats, down from about 44,000 onboarded in FY26, with a stronger lean toward AI-skilled candidates in Digital and Prime tracks.
No official base-pay differential exists by location for freshers, though HRA is adjusted by city classification and cost of living varies between metro and Tier-2 postings.
Original mark sheets from X, XII, Diploma (if applicable), Graduation, and Post-Graduation, along with valid photo ID proof.
Varies by drive. Candidates commonly report several weeks to a couple of months between NQT registration and a final offer letter, depending on interview scheduling and verification.
Reattempt policies vary by drive and are communicated on the registration portal — there isn’t a single universal cooldown publicly fixed across all cycles.
No — both routes go through the same NQT and interview process. The difference is administrative (who coordinates registration), not evaluation standard.
Practice beats passive reading
Practice Technical-then-HR sequences with AI follow-ups, generate NQT-style coding prompts, and ATS-check your resume before you apply.
Continue in this order for the fastest path through this topic.