IT Services · Campus Placement · Mumbai
Curated TCS interview questions for campus placements and off-campus drives — with NQT section breakdown, hiring process guide, topic importance chart, Digital vs Prime comparison, common mistakes, and a 30-day preparation plan.
TCS Campus Hiring Roadmap
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:
TCS campus and off-campus drives follow a predictable pipeline — NQT filters the majority before technical depth is tested. Pair this guide with our placement interview guide.
Register on the TCS NextStep / campus portal with accurate academic details. Upload resume highlighting projects, internships, and programming languages. Eligibility typically requires 60%+ aggregate with no active backlogs at most campuses.
Timed online assessment with Verbal Ability, Reasoning, Numerical Ability, and Programming Logic sections — plus coding for Digital/Prime aspirants. Top percentile bands unlock higher package tracks.
Live or virtual panel testing CS fundamentals — OOPs, DBMS/SQL, OS, networking basics — plus 1–2 coding or pseudocode problems. Expect follow-ups on your resume projects and language choice (Java/C/Python).
Assesses communication, situational judgment, and role fit. May include light technical probing, project deep-dives, and scenario questions on deadlines, teamwork, and client delivery.
Final behavioural screen: career goals, relocation flexibility, salary band acceptance, and “Why TCS?” Prepare STAR stories and know Digital vs Prime / Ninja package differences.
Selected candidates receive offer letter with role band, CTC breakdown, joining date, and ILP (Initial Learning Program) details. Digital UG ₹7.09–8.04 LPA / PG ₹7.39–8.04 LPA; Prime UG ₹9.09–9.30 LPA / PG ₹11.50–11.80 LPA — confirm track and fixed vs variable split before accepting.
TCS Hiring Process 2026
Role-specific loops: TCS Software Engineer, TCS Java Developer, and Infosys interviews.
The National Qualifier Test is the highest-leverage stage — most eliminations happen here. Each section tests a different skill; balance prep across all five, not coding alone.
| Section | Focus Area |
|---|---|
| Verbal Ability | Grammar, Reading, Vocabulary |
| Numerical Ability | Arithmetic, Percentages, Profit & Loss |
| Reasoning Ability | Logical Reasoning, Patterns |
| Programming Logic | Flowcharts, Pseudocode |
| Coding | Java, C++, Python |
TCS updates exam formats periodically. Always verify the latest NQT pattern before applying.
Reading comprehension, sentence correction, synonyms/antonyms, and para-jumbles. High accuracy matters more than speed — negative marking on some NQT variants makes reckless guessing costly.
Prep tip: Solve 10 RC passages weekly; review grammar rules for subject-verb agreement and tense.
Percentages, ratios, time-speed-distance, profit-loss, and basic 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, and series patterns. This section separates Digital/Prime shortlists from mass Ninja cuts.
Prep tip: Practice 15 reasoning sets under 20-minute clocks; learn diagram notation for arrangements.
Flowcharts, pseudocode tracing, operator precedence, and debugging snippets — tests whether you think like a programmer before live coding.
Prep tip: Trace 5 pseudocode problems daily; revise loops, recursion, and boolean logic.
1–2 problems for Digital/Prime tracks — arrays, strings, basic sorting/searching. Ninja track may skip or use lighter programming logic only.
Prep tip: Solve 40 easy array/string problems on paper under 25-minute timers.
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 shortlists candidates into three fresher bands after NQT. Your percentile, coding score, and interview depth determine which track you qualify for.
| Track | Package | Difficulty | Coding Level |
|---|---|---|---|
| Ninja | Entry Level | Easy | Basic |
| Digital | Medium | Medium | Intermediate |
| Prime | Highest Fresher Track | High | Strong DSA |
Your NQT percentile and coding performance determine track eligibility. Target Prime only if you consistently solve medium array/string problems under timed conditions.
The salary brackets and roles for both categories generally scale as follows:
| Tier | Annual CTC (Undergraduate) | Annual CTC (Postgraduate) | Target Roles & Tech Focus |
|---|---|---|---|
| TCS Digital | ₹7.09 – ₹8.04 Lakhs | ₹7.39 – ₹8.04 Lakhs | Full Stack Development, Cloud, AI/ML, Big Data |
| TCS Prime | ₹9.09 – ₹9.30 Lakhs | ₹11.50 – ₹11.80 Lakhs | Technical Specialist, Lead Projects, Mentorship |
| Dimension | TCS Digital | TCS Prime |
|---|---|---|
| Annual CTC (UG) | ₹7.09 – ₹8.04 LPA | ₹9.09 – ₹9.30 LPA |
| Annual CTC (PG) | ₹7.39 – ₹8.04 LPA | ₹11.50 – ₹11.80 LPA |
| Target roles | Full Stack, Cloud, AI/ML, Big Data | Technical Specialist, Lead Projects, Mentorship |
| Difficulty | Moderate — strong aptitude + basic coding | High — aptitude plus DSA-medium coding |
| Coding Level | Easy arrays/strings, OOP basics | Medium DSA, optimization expected |
| Selection Rate | Higher — larger intake band | Lower — top NQT percentile only |
| Interview Depth | Technical + HR; lighter managerial | Technical + managerial + HR; deeper CS probes |
Use these as prep benchmarks across NQT and interview rounds — not as guaranteed cutoffs.
Target
75%+
Aim for high accuracy in quant and reasoning sections — speed matters under NQT time limits.
Target
2/2 coding questions whenever possible
Digital and Prime aspirants should solve both problems cleanly with correct edge-case handling.
Target
Strong OOPs, SQL, DBMS, OS fundamentals
Narrate answers with examples from projects; expect 1–2 follow-up probes per topic.
Target
Clear communication and confidence
Use STAR format, research ILP/Fresco Play, and articulate why TCS fits your career plan.
No fixed cutoff is publicly disclosed by TCS. Targets below are preparation benchmarks from campus prep communities — not official thresholds.
Four-week campus prep plan — aptitude first, then programming logic, CS fundamentals, and full mocks.
Week 1 (Days 1–7)
Week 2 (Days 8–14)
Week 3 (Days 15–21)
Week 4 (Days 22–28)
These patterns cause rejections even when candidates know individual topics. Fix them before your NQT slot.
Mistake
Why it hurts: NQT eliminates 60–70% of applicants before any technical round — strong coders fail without quant and reasoning practice.
How to fix it: Allocate 50% of Week 1–2 to timed aptitude and reasoning sets mirroring NQT section clocks.
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: 60 min aptitude + 60 min programming logic/coding — not coding alone.
Mistake
Why it hurts: Generic “TCS is a big company” answers fail HR panels that test motivation, relocation, and career clarity.
How to fix it: Prepare 5 STAR stories and research ILP, Fresco Play, and specific TCS training programs.
Mistake
Why it hurts: Technical rounds expose gaps in spoken explanations — silent practice hides communication and nervousness issues.
How to fix it: Run 3 full mocks before NQT: aptitude simulation + technical narration + HR round.
Mistake
Why it hurts: Managerial and HR rounds weight clarity heavily — mumbled project explanations fail even with correct technical knowledge.
How to fix it: Record 60-second project walkthroughs; fix filler words and structure answers with Situation → Action → Result.
Mistake
Why it hurts: NQT requires muscle memory for speed math and pattern recognition — 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.
TCS National Qualifier Test is the primary campus and off-campus screening for TCS hiring in India. Final-year B.Tech/BCA/MCA students and recent graduates register through TCS NextStep. Your NQT percentile determines Ninja, Digital, or Prime track eligibility.
Typically four stages after application: NQT online test, technical interview, managerial interview, and HR round — then offer. Some campus drives consolidate technical and managerial into one longer panel.
Prime (UG ₹9.09–9.30 LPA; PG up to ₹11.80 LPA) targets top NQT performers with stronger coding and CS depth. Digital (UG ₹7.09–8.04 LPA) requires solid aptitude and basic programming with roles in full stack, cloud, and AI/ML. Ninja remains the mass hiring band with lighter technical expectations.
Prime and Digital technical rounds include easy-to-medium array, string, and logic problems. Heavy dynamic programming is uncommon for fresher TCS loops — aptitude and CS fundamentals matter more than LeetCode Hard.
Percentages, ratios, time-speed-distance, profit-loss, blood relations, seating arrangements, syllogisms, and data interpretation. Programming logic and pseudocode tracing are equally critical for shortlisting.
Prepare STAR-format answers for teamwork, deadlines, and conflict. Research TCS scale, ILP training, Fresco Play, and why you prefer TCS over Infosys or Wipro. Know your preferred location and joining flexibility.
OOPs, DBMS/SQL (joins, normalization), operating systems (process vs thread, deadlock), basic networking, and SQL vs NoSQL trade-offs. Expect 1–2 coding or pseudocode problems alongside theory questions.
Yes — aptitude, reasoning, OOPs, DBMS, and OS overlap heavily. Add company-specific mocks: NQT format for TCS and InfyTQ patterns for Infosys in your final prep week.
Digital UG ₹7.09–8.04 LPA (PG ₹7.39–8.04 LPA); Prime UG ₹9.09–9.30 LPA (PG ₹11.50–11.80 LPA). Figures vary by college tier and offer year — confirm CTC breakdown (fixed vs variable) and joining location before accepting.
Some NQT variants apply negative marking on aptitude sections — verify the instructions on your test day. When negative marking applies, skip questions you cannot eliminate to two options.
Campus drives often complete in 4–8 weeks from NQT to offer. Off-campus batches may stretch longer depending on slot availability and background verification timelines.
Run at least 3 mocks: one timed NQT simulation, one technical with spoken coding narration, and one HR round. InterviewEra mocks score communication, structure, and technical depth across five rubric dimensions.
Practice beats passive reading
Practice aptitude-style reasoning, technical CS fundamentals, and HR STAR answers with AI-generated follow-ups. Get rubric-based feedback on communication, technical depth, structure, confidence, and relevance.