Ixyle
Indian Services

TCS

Practise a TCS interview

Free first round · 20 min · no credit card

India's largest campus recruiter. NQT-driven aptitude → tech → HR.

Interview philosophy

How Tata Consultancy Services actually interviews

TCS interviews lateral candidates with a process-first lens: the bar is not "FAANG-style algorithmic excellence" but rather "can this person reliably deliver inside a CMMI-Level-5 delivery org for a Fortune 500 client". The conversation is warmer and more conversational than product-co interviews — expect interviewers (often delivery managers, not pure engineers) to spend meaningful time on past-project walkthroughs, your role on a team, and client-handling stories.

The lateral track typically skips TCS NQT (which is the campus iON-driven test) and starts with a recruiter screen + one or two technical rounds + an HR/managerial round. Technical rounds focus on (a) the stack on your CV (interviewers will go deep — DBMS, OS, OOP, your framework, your domain) and (b) project deep-dives where you'll be asked to defend tech choices, debug a past production issue, and sketch how you'd extend the system. For Digital / Prime track laterals, expect harder DSA + a light system-design probe.

HR is heavily weighted on willingness signals: relocation, time zone, vertical flexibility, stack flexibility, notice period, and a reasonable CTC ask. Aggressive negotiation in the technical round, evasive answers on notice period, or a strong preference to remain on a single stack are all meaningful negative signals.

"Selected" at TCS lateral = clear project understanding + stack-relevant technical depth + flexibility on location/stack/shift + reasonable CTC ask + stable history. The bar is reliability and process fluency, not algorithmic brilliance.
Cultural pillars

What they're measuring you on, beyond the right answer

The values interviewers probe for. Each pillar is what they ask about, plus how they ask it.

Integrity (Tata Code of Conduct)

Ethical conduct, regulated-sector compliance, Responsible AI use; non-negotiable across the Tata group.

How they probe · Scenario probes on conflicts of interest, data handling on client engagements, and adherence to compliance gates.

Client Value Creation

Outcome-oriented engagements; the candidate is expected to talk in terms of business value, not just code shipped.

How they probe · What was the measurable impact of your last project? How did you escalate when a client deliverable slipped?

Excellence & Process Discipline (CMMI 5)

TCS is CMMI Level 5 — process adherence, code reviews, defect-density tracking are part of the muscle.

How they probe · Walk me through your release / SDLC process. Who signed off code reviews? How were defects tracked?

Continuous Learning

100M+ learning hours/year on iEvolve; certifications are visible to managers and influence allocation.

How they probe · Which TCS-relevant certifications/upskilling have you done in the last 12 months? Comfortable retraining onto a new stack?

Unity & Flexibility

150+ nationalities, 50+ countries — willingness to relocate, work in any time zone or stack, and serve any vertical is core.

How they probe · Are you open to BFSI/Retail/Telecom verticals? Comfortable with onsite rotation, night shifts, or a non-preferred tech stack?

The full loop

Round-by-round, in the order they actually run

Reported pattern from candidate write-ups. Eliminating rounds are the ones where a single bad signal ends the loop.

  1. 01
    Recruiter screen20 minEliminating

    current CTC, expected CTC, notice period, location, stack overview

  2. 02
    Technical 145 minEliminating

    stack-specific deep-dive (Java/.NET/Python/SQL), CS fundamentals, project walkthrough

  3. 03
    Technical 245 minEliminating

    second technical pass — design / debugging / SQL / domain knowledge; sometimes skipped for non-Digital tracks

  4. 04
    Managerial30 minEliminating

    client-handling, conflict, delivery pressure, project leadership

  5. 05
    Hr25 minEliminating

    willingness, notice period, family situation, salary fitment, BGV expectations

Real questions, by round type

What candidates were actually asked

Curated from interview reports and company write-ups. Practise against any of these in a live mock.

Sde Lateral

Technical

  • Walk me through the architecture of your most recent project end to end.
  • Why did you pick <framework> over <alternative>? What were the tradeoffs?
  • Explain ACID. How does your DB handle isolation in production?
  • Difference between abstract class and interface — where did you use each in your project?
  • Write SQL: 2nd highest salary per department. Now optimize for 50M rows.
  • Java: explain garbage collection generations and a real OOM you debugged.
  • What's your unit test coverage? How is it enforced in CI?
  • How would you redesign this module if you had 3 more weeks?

Behavioral

  • Describe a time the client pushed back on your estimate. How did you handle it?
  • Tell me about a production incident you owned end to end.
  • How do you handle a teammate who consistently misses commitments?
  • Have you led a module/track? How did you split work?
  • Why are you leaving your current company?

willingness

  • Are you willing to relocate to any TCS delivery centre in India?
  • Are you comfortable with night-shift / rotational shift if the project demands it?
  • Are you open to working on a non-preferred technology stack for the first 6 months?
  • What is your notice period? Can it be shortened?

Data Engineer Lateral

Technical

  • Star schema vs snowflake schema — when do you pick which?
  • Walk me through your last ETL pipeline: source, transform, sink, monitoring.
  • Spark: difference between repartition and coalesce; when does shuffle happen?
  • Window functions in SQL — write LAG / LEAD on a transactions table.
  • How do you handle late-arriving data in a streaming pipeline?

Behavioral

  • Describe a data-quality incident — RCA and what you changed.
  • How do you collaborate with the analytics consumers of your pipeline?

Consultant Domain Lateral

domain

  • Explain the trade lifecycle for a fixed-income instrument (BFSI track).
  • Walk me through claims adjudication in a healthcare TPA system.
  • What's the difference between a policy admin system and a billing system?
  • How is regulatory reporting different in EU vs US for your domain?

Behavioral

  • Tell me about a requirement that the client added late. How did you protect the timeline?
  • Describe a time you had to push back on a client and how it landed.
What rejects you · what advances you

The two patterns that decide every loop

Red flags

  • Refusal or strong reluctance to relocate to any Indian delivery centre.
  • Refusal to consider night-shift / rotational shift for client-aligned roles.
  • Strong preference for staying on exactly one tech stack — no flexibility.
  • Plans for a higher-studies abroad / MBA in <12 months (services value retention).
  • Bad-mouthing previous employer or naming individuals.
  • Aggressive CTC negotiation in the technical round (push it to HR).
  • Mentioning competing offers as leverage during technical rounds.
  • Fuzzy on basics of your own resume project (sign of resume inflation).
  • Notice period > 90 days with no buy-out plan.

Advance signals

  • Clean project deep-dive: business outcome → tech choice → role → tradeoffs.
  • Visible CMMI / SDLC vocabulary — code reviews, defect density, RCA, retrospectives.
  • Stable employment history (avg tenure > 2 years per company is a positive).
  • Comfortable across 2+ stacks; signals retraining willingness.
  • Domain depth in a TCS focus vertical (BFSI, Retail, Telecom, Healthcare, Manufacturing).
  • Open to onsite (US / UK / Europe / GCC) rotation.
  • Reasonable CTC expectation (typically 25-40% hike on current).
  • Crisp client-handling story with measurable outcome.

Don't do

  • Open with CTC negotiation in the technical round.
  • Downplay willingness — never say 'I'd rather not relocate' on the first ask.
  • Mention competing offers as leverage during technical screens.
  • Bring up ESOPs / equity expectations — TCS lateral comp is base + variable, not equity.
  • Bad-mouth your previous employer or current manager.
  • Skip the 'why are you leaving' question with vague answers.
  • Show inflexibility on shift / vertical / stack.
Compensation

Base salary bands by level

Junior

4.57.5L

Annual base

Mid

816L

Annual base

Senior

1630L

Annual base

Staff+

2855L

Annual base

TCS lateral hiring uses internal grade bands (Y/T/P/I/E/M). No equity. Base comp is conservative versus product cos but onsite (US/UK/Europe) postings add ~2-3x via per-diem. Variable pay is band-linked (5-15%). Joining bonus is rare and small if offered. Hike on switching is typically 25-40%; very hot skills (cloud architects, SAP S/4HANA, Salesforce CPQ) can pull 50%+.

Process

What to expect after each round

Typical timeline

~4 weeks

Recruiter-screen → offer

Reapply window

6 months

After a final-round rejection

Feedback practice

Detailed feedback rarely shared with candidates; recruiters give a one-line outcome.

Thanks for your time. We'll get back to you with feedback in 5-7 working days.

Verified profile

Last verified Mon Apr 27 2026 00:00:00 GMT+0000 (Coordinated Universal Time) · 9 sources

View sources
  • TCS Careers — Lateral Hiring (https://www.tcs.com/careers/india/lateral-hiring)
  • Tata Code of Conduct (https://www.tcs.com/who-we-are/governance/tata-code-of-conduct)
  • TCS Diversity, Equity & Inclusion (https://www.tcs.com/who-we-are/diversity-equity-inclusion)
  • Glassdoor — TCS Senior Software Engineer interviews (2024-2026)
  • AmbitionBox — TCS interview reviews & salary (2025-2026)
  • GeeksforGeeks — TCS Recruitment Process
  • Levels.fyi — TCS India bands
  • 6figr.com — TCS salary 2026
  • ccbp.in / unstop.com — TCS Recruitment Process 2025-2026