TCS Interview Guide (2026)

1Snapshot, read this first#

The one thing to understand about TCS: this is a volume process, not a search for the single best coder.

• It exists to find reliable, trainable, communicable freshers at scale.
• A TCS fresher gets dropped into a client project after training.
• The whole bar: show up on time, follow a spec, do not embarrass anyone in front of the client.
• So your job is to be a clean, low-risk, well-spoken candidate, not a show-off.

2Getting the call (the part most guides skip)#

TCS freshers are hired through two doors, and the TCS NQT test is the key to both.

Campus (on-campus or TCS's campus pool). The smoothest path, if your college is a hiring partner.

• TCS runs the drive directly and your placement cell shares the schedule, cutoffs, and registration link.
• Attend every pre-placement talk.
• Meet eligibility: usually no active backlogs and a minimum percentage, commonly around 60% or a 6.0 CGPA across 10th, 12th, and degree.
• Keep gap years explainable.
• One missed email from the placement cell can cost you the slot, so turn on notifications and reply fast.

Off-campus via TCS NQT. How lakhs of students without a TCS tie-up get in.

• Register for the TCS NQT on the official TCS iON / nextstep careers portal.
• Create a CT/DT reference number, fill the profile fully, and book a test slot.
• Register early, slots fill.
• An incomplete profile can block you from applying to the actual job drive after you clear the test.
• The reference number links your test score to the job application, so note it down and do not lose it.

Resume rules for a fresher:

• One page. Clean, single column, no photo-heavy template, saved as PDF.
• Lead with skills and projects, not a long objective line. Nobody reads the objective.
• Quantify everything. Weak: "Made a library management project." Strong: "Built a library management web app (Java, MySQL) handling 500+ book records with search in under 1 second; used by 3 classmates for a semester."
• List languages honestly, only what you can defend. "Expert in Java" plus a blank on what a constructor is equals a fast rejection.

ATS and keyword tips:

• Screening looks for clear, role-relevant terms. Include the obvious true ones: Java, Python, C++, SQL, DBMS, OOP, Data Structures, HTML, CSS, Git, problem solving.
• Spell out degree, branch, year of passing, and percentages in plain numbers.
• The system filters on eligibility first, a human looks second.
• If your 10th or 12th percentage is below the cutoff, the resume never reaches a person.

How people actually get shortlisted:

• The test score is the gate, full stop.
• Clear the NQT at a good level and you are auto-invited to the interview.
• Your band (Ninja, Digital, or Prime) is then decided by how far you push in both the test and the interview.
• There is no backdoor and no reference that beats a failing score. The test is the whole game for getting the call.

3The loop at a glance#

Treat every round as elimination:

• Rounds may happen the same day in a campus drive, or spread across days off-campus.
• A weak HR answer can still sink a strong technical score.
• HR is scoring risk, and "this person might quit in six months" is a risk they will not take.

4The test and coding rounds, patterns, not problems#

The TCS NQT is the heart of fresher hiring. It is section-timed and usually non-backtracking (you cannot return to a previous section), so pace yourself and finish each part before the timer moves you on.

Numerical Ability (Quants). Moderate difficulty, speed is the real test.

• Topics repeat year over year: number system, percentages, ratio and proportion, averages, time-speed-distance, time and work, profit and loss, simple and compound interest, permutations and combinations, probability, and basic geometry and mensuration.
• The challenge is speed, not depth.
• Practice mental math and shortcut methods until a two-step percentage problem is reflexive.
• If you are reaching for a calculator mindset, you are already too slow.

Reasoning Ability (Logical). Same story: moderate difficulty, heavy time pressure.

• Series, coding-decoding, blood relations, directions, syllogisms, seating arrangement, data interpretation from tables and charts, and puzzles.
• Learn to skip and return within a section rather than sinking five minutes into one puzzle.
• A single seating-arrangement set can quietly eat eight minutes.
• Set a mental cap of about ninety seconds per question and move on.

Verbal Ability (English). The free-marks zone most people under-prepare.

• Reading comprehension, sentence completion, error spotting, synonyms and antonyms, and sentence rearrangement.
• Read the passage questions first, then scan for the answer.
• Do not neglect it just because "my English is fine." People who skip verbal prep lose easy points to tricky grammar questions.

Programming Logic / Pseudo-code. Read a snippet, predict the output or pick the correct logic.

• Multiple-choice on code output, loops, recursion, arrays, data types, operator precedence, and basic algorithm behaviour.
• Brush up on C-style pseudo-code, many questions use it.
• The classic traps: off-by-one loop bounds, post-increment versus pre-increment, and integer division.
• Trace the code line by line on paper instead of eyeballing it.

Coding (Hands-on). One or two problems in a real editor, in a language of your choice (commonly C, C++, Java, or Python).

• Expect fresher-level problems: string manipulation, pattern printing, array operations, number logic (prime, palindrome, Armstrong, Fibonacci), simple sorting, and basic file and input handling.
• Full marks come from passing all test cases.
• Partial credit usually exists for passing some, so a working-but-slow solution still scores.

Here is the shape of a typical coding-round answer, clean input handling and a clear loop:

# Check if a number is prime (classic NQT coding problem)
n = int(input())
if n < 2:
    print("Not Prime")
else:
    is_prime = True
    i = 2
    while i * i <= n:        # only check up to sqrt(n)
        if n % i == 0:
            is_prime = False
            break
        i += 1
    print("Prime" if is_prime else "Not Prime")

Two things an evaluator rewards here:

• Reading input in the exact format.
• An edge-case guard (n < 2). That guard is the difference between passing all test cases and losing marks on the "1" and "0" inputs.

How to win these sections:

• Manage the clock, not the ego. Lock easy marks first; never let one hard question eat a section. A thirty-second question is worth the same as one you fight for six minutes.
• Read input and output format exactly. Most fresher failures are wrong output format, not wrong logic. If the problem says print "YES", printing "Yes" fails the test case.
• Dry-run with edge cases: empty input, single element, zero, negative numbers. These are exactly the hidden test cases that trip people.
• Pick one coding language and go deep. Know its input-reading syntax cold, so you spend brain on logic, not semicolons. Fumbling Scanner versus BufferedReader costs real minutes.
• Practice on a timer. Solve 20 to 25 full mock tests before the real one; familiarity with the interface removes half the panic. The first time you see the real UI should not be on test day.

5CS fundamentals (the interview backbone)#

TCS technical interviews lean hard on core computer science, not elaborate DSA.

• The interviewer is usually a project lead, not an algorithms researcher.
• They are checking whether you understood your degree or just passed it.
• Be genuinely comfortable explaining each of these in plain words.

OOP.

• The four pillars (encapsulation, abstraction, inheritance, polymorphism) with a real example each.
• Overloading (same method name, different parameters, decided at compile time) versus overriding (child class redefines a parent method, decided at run time).
• Class vs object, constructors, and what a default constructor does.
• A one-line example per pillar puts you ahead of most candidates.

DBMS. Know the basics and be ready to write SQL on the spot.

• Primary key versus foreign key, normalization (1NF, 2NF, 3NF at a high level), JOINs (inner, left, right), ACID properties.
• Expect something like "get all students with marks above 80, sorted by name":

SELECT name, marks
FROM students
WHERE marks > 80
ORDER BY name;

• They may then ask you to add a JOIN or a GROUP BY, so know those too.
• SQL on paper is one of the most common live tasks in the technical round.

Operating Systems.

• Process vs thread, deadlock and its four conditions (mutual exclusion, hold and wait, no preemption, circular wait).
• Basic scheduling (FCFS, round robin), and what paging and virtual memory mean at a concept level.
• You do not need to compute scheduling tables, but you should explain why a thread is lighter than a process.

Computer Networks.

• OSI vs TCP/IP layers at a high level.
• TCP (reliable, connection-oriented) versus UDP (fast, no guarantees).
• What HTTP, HTTPS, and DNS do, IP vs MAC address.
• A clean answer on TCP versus UDP with one real example each (video call uses UDP, file download uses TCP) lands well.

Data Structures (light).

• Arrays vs linked lists, stack vs queue, what a tree and a hash table are.
• Time complexity basics (why O(n) beats O(n squared)).
• You will rarely code a red-black tree. You will be asked why you would pick a hash table over an array for lookups.

Project discussion. Pick ONE project from your resume and know it end to end.

• The problem, your exact contribution, the tech stack, one hard bug you fixed, and what you would improve.
• Interviewers probe depth here to see if the resume is real.
• The fastest way to fail: say "we built it as a team" and then go quiet when asked what you wrote. Have your specific part memorized.

6Behavioral & culture fit#

TCS's culture is built around its long-standing values, commonly framed as Integrity, Respect for the Individual, Excellence, Learning and Sharing, and operating with the mindset of Leadership with Trust.

• They also emphasize adaptability (willingness to learn any technology and relocate) and long-term commitment.
• HR is explicitly checking one thing: will this person stay, grow, work in a team, and represent the company well in front of a client.
• Everything you say gets scored against that question.

Write 3 to 4 short STAR stories before the interview (Situation, Task, Action, Result):

• One on teamwork.
• One on handling pressure or a deadline.
• One on learning something new fast.
• One on a failure you recovered from.
• Always land on a result with a number. A story without a measurable ending sounds made up.

One full worked STAR example:

S (Situation): In my final-year group project, our 4-person team was building a college event-registration site, and two days before the demo our database kept crashing under multiple simultaneous sign-ups. T (Task): As the member who had set up MySQL, I had to find and fix the crash so the demo would run clean in front of faculty. A (Action): I reproduced the crash by simulating 30 parallel registrations, found we were opening a new DB connection per request and never closing it, and rewrote it to use a single pooled connection with proper close calls. I also added input validation to stop duplicate entries. R (Result): The site then handled 50+ concurrent registrations without a single crash, the demo ran smoothly, and we scored the highest in our batch for that project, 95 out of 100.

Why that answer works:

• Short setup, your specific action, a measurable finish.
• It names a real technical cause (connection leak) and a real number.
• That specificity is what makes HR believe you.

HR specifics to prepare:

• "Tell me about yourself" in 90 seconds, structured: who you are, what you studied, one strong project, what you want next.
• Willingness to relocate anywhere in India.
• Comfort with the service agreement and bond period.
• Why TCS, your strengths, one honest weakness with how you are improving it.
• Salary expectation: for freshers it is largely fixed by band, so be gracious, not demanding. "I am comfortable with the standard package for my band" is the right register.

7Your prep plan#

4-week plan:

• Week 1: Lock quants and reasoning fundamentals; one topic per day plus 10 practice questions. Track your weak topics in a list.
• Week 2: Daily coding, solve 3 to 4 fresher-level problems; master input and output in your chosen language. Start CS fundamentals (OOP, DBMS).
• Week 3: Finish CS fundamentals (OS, CN, DS). Take 2 full-length NQT mock tests this week, timed, no pauses.
• Week 4: 3 to 4 more full mocks, write and rehearse STAR stories out loud, deep-prep one project, do 2 mock HR interviews with a friend.

2-week plan:

• Days 1-4: Quants and reasoning rapid revision with shortcut methods; 1 mock test.
• Days 5-8: Coding practice daily plus CS fundamentals crash (OOP, DBMS, OS, CN basics).
• Days 9-11: 3 full timed mocks, fix weak sections between them.
• Days 12-14: STAR stories, project deep-dive, spoken-English and HR rehearsal.

2-day crash plan:

• Day 1: Two full-length NQT mocks. Review every wrong answer, not just the score. Memorize key quant formulas and one coding language's I/O syntax.
• Day 2: Skim OOP, DBMS, OS, and CN one-liners. Write 3 STAR stories. Rehearse "tell me about yourself" and "why TCS" out loud 5 times. Sleep early, a tired brain loses easy marks.

8Why people get rejected at TCS#

1. Clearing the test but freezing in the interview. They can code in silence but cannot explain what a foreign key is. The interview is a talking test as much as a tech test.
2. Weak spoken English. The communication round genuinely filters here. Hesitant, unclear answers read as risk, because this person will be put in front of a client.
3. A resume project they cannot explain. The moment the interviewer digs one layer, the "project" collapses and so does your credibility.
4. Unexplained academic or honesty gaps. Unexplained year gaps or inflated skills, caught in cross-questioning. Honesty gaps hurt far more than the gap itself.
5. Refusing relocation or showing low commitment. Hinting you will leave soon or will not move anywhere in India is a quiet killer. It directly fails the "will they stay" check.
6. Mugged-up, robotic answers. Reciting a memorized "why TCS" with no personal reason feels rehearsed and fails culture fit. Interviewers hear the same script fifty times a day and spot it instantly.

9The offer, comp & negotiation#

For freshers, TCS compensation is tied to the hiring band, and the numbers are largely standardized:

• Ninja: typically around Rs 3.36 to 3.6 LPA.
• Digital: typically around Rs 6.5 to 7 LPA (cleared after a higher-difficulty advanced coding section).
• Prime: the premium band, often Rs 9 LPA and above depending on skills and interview performance.

The package and the fine print:

• Usually a fixed base plus a smaller variable or allowance component, with standard benefits (medical insurance, provident fund).
• There is commonly a service agreement, meaning a minimum commitment period or bond.
• Read it before signing and know the exit terms, because leaving early can carry a financial penalty.

Negotiation reality for freshers: base pay per band is mostly non-negotiable, so spend your energy on getting into a higher band, not haggling over a few thousand rupees.

1. Aim for Digital or Prime from the start by attempting the advanced coding section and showing strong fundamentals. That is the real raise: a Digital offer pays nearly double a Ninja one.
2. If you hold a competing offer, mention it politely to HR. It can occasionally influence band placement, though not the fixed scale within a band.
3. Clarify the written details: your band, joining location flexibility, and the agreement terms, so there are no surprises on joining day.

10FAQ#

Q: Do I need to be great at DSA to clear TCS? A: No. You need solid fundamentals and one working language. The coding is fresher-level (strings, arrays, number logic), and interviews focus more on CS basics and clear explanation than hard algorithms. Being able to explain a hash table well beats being able to solve a hard graph problem in silence.

Q: Can I appear for the NQT off-campus if my college has no TCS tie-up? A: Yes. Register on the official TCS careers portal, complete your profile, get your reference number, and book a slot. Clearing the test qualifies you for off-campus drives, no college partnership needed.

Q: What if I have a backlog or an academic gap? A: Eligibility often requires no active backlogs at the time of the drive, and gaps should be explainable (illness, exam attempts, family reasons). Be honest. Unexplained or hidden gaps are what hurt you, not the gap itself.

Q: How long is the wait after the interview? A: It varies, from a few days to several weeks, especially in large off-campus cycles. No news for 2 to 3 weeks is normal; keep preparing for other options meanwhile instead of refreshing your email.

Q: Which coding language should I use for the coding round? A: Whichever you know best among C, C++, Java, or Python. Pick one and master its input and output handling so you spend your time on logic, not syntax. Python is often the fastest to write under time pressure if you know it well.

Want this turned into a personalized, dated study plan that counts down to your actual test date? Tell me your test day and your weak sections, and I'll map out exactly what to do each day.