Project, DBMS, OOP, Coding, Why-TCS round·Engineering·Medium·20 min

TCS Ninja Technical Interview — Project, DBMS, OOP, Coding, Why-TCS

20 min · 1 credit · scorecard at the end

ZeroPitch Research Desk

Updated 2026-05-24 · Newly added · be among the first to take it

Field: Engineering
Company: Tata Consultancy Services
Role: Assistant System Engineer Trainee (Ninja)
Duration: 20 min
Difficulty: Medium
Completions: New
Updated: 2026-05-24

What this round is about

Topic focus. The post-NQT TCS Ninja Technical Round — final-year project deep-dive, DBMS (1NF/2NF/3NF normalization, joins, ACID, indexes), OOP four pillars with examples from YOUR project, one coding question (typically a pattern print or a SQL query), language fundamentals, and a why-TCS probe.
Conversation dynamic. Arjun Kumar, a 14-year TCS Technical Lead from the Chennai BFSI delivery centre, is calm and structured. He never raises his voice. After almost every technical answer he asks why did you choose that.
What gets tested. Project ownership, DBMS basics under live recall, OOP applied to your own work, one coding problem written and dry-run cleanly, language fundamentals at hygiene level, why-TCS articulated with one specific reason, and clear yes on relocation.
Round format. Forty-five to sixty minutes, four blocks, candidate-led on the project, interviewer-led on DBMS and OOP. Arjun will deliberately push back on one correct answer to test conviction.
Time budget. Roughly five to ten minutes on the project deep-dive, fifteen on DBMS plus OOP, ten on the coding problem, and the last five on language fundamentals plus why-TCS. Arjun keeps the pace tight and cuts long-winded answers short.

What strong answers look like

Specific module ownership. Name the module YOU built, not what your team built collectively. Name the technology and the alternative you rejected, with a one-sentence reason.
Non-textbook OOP examples. Encapsulation as the private fields on YOUR Patient class, inheritance as YOUR Admin extending User, polymorphism as YOUR generateReport behaving differently for PDF and CSV subclasses. Two sentences per pillar is enough.
SQL subquery for second-highest salary. SELECT MAX(salary) FROM Employee WHERE salary less than (SELECT MAX(salary) FROM Employee). No LIMIT. Dry-run mentally on five rows.
Pattern that runs on first dry-run. Loops with correct bounds (no off-by-one), sensible variable names, walked through for N equals 3 or 4 verbally.
Why-TCS with one specific anchor. Reference the BFSI vertical and BaNCS, the ILP at Trivandrum, the Chennai Tidel Park delivery centre, or the All India NQT scale. One specific reason beats three generic ones.

What weak answers look like (and how to avoid them)

Resume inflation. Listing Spring Boot or Machine Learning without being able to explain dependency injection or model selection. Avoid by removing technologies you cannot defend in two sentences.
Textbook OOP examples. The car-engine polymorphism example, the bank-account encapsulation example. Avoid by preparing one project-specific example per pillar before the interview.
SQL with LIMIT when asked without LIMIT. Reads as tutorial copy, no internalisation. Practice the subquery form before the interview.
Frozen on pattern printing. Off-by-one loops you cannot debug. Avoid by hand-writing three different patterns on paper the week before.
Generic why-TCS. TCS is a good company is the most cited soft-reject signal. Look up one specific TCS thing before the interview and reference it.
Hesitating on relocation. I prefer Bengaluru only is a no-hire signal. The right answer is a clear yes to relocation anywhere in India.

Pre-interview checklist (2 minutes before you start)

Have your project one-liner ready. What the system does, who uses it, which module is YOURS. Thirty seconds, not three minutes.
Pre-rehearse the four OOP pillars with project examples. One sentence per pillar, drawn from your final-year project. No car engines, no bank accounts.
Write the second-highest-salary SQL once on paper. Both forms: with LIMIT and the subquery form. Be ready to use only the subquery form.
Hand-write one star pattern on paper. Right triangle of stars, N equals 4. Read your own code back and verify it works.
Look up one specific TCS thing. BaNCS product, ILP programme, BFSI vertical, Chennai delivery centre at Tidel Park. Pick one and remember it.
Confirm with yourself: yes to relocation, yes to 1-year service agreement. Anywhere in India, no preference, no hesitation.

How the AI behaves

Probes every technical answer. After almost every answer Arjun asks why did you choose that. Have a one-sentence reason ready.
No mid-interview praise. He will not say great answer or exactly. He acknowledges with Okay, fine. or Understood. and pushes deeper.
Allergic to textbook examples. If you give the car-engine polymorphism, he will visibly tire and ask for a project example. The bank-account encapsulation triggers the same response.
Deliberate pushback once. He will challenge one correct answer during the round to test your conviction. Defend with reasoning. Capitulating immediately reads as low conviction.
Cross-questions resume claims. If you list Spring Boot or Machine Learning, expect a deep follow-up. False statements get exposed and become an instant reject signal.

Common traps in this type of round

Project answered at team level, not personal level. We built a hospital management system instead of I built the appointment-scheduling module.
OOP definitions without examples from your work. Reciting the textbook definition then stopping. Always pair definition with a one-sentence project example.
SQL with LIMIT when told without LIMIT. A common tutorial habit; practice the subquery form.
Off-by-one loops in pattern printing. Common when nervous; dry-run mentally before saying you are done.
Generic why-TCS. The single most cited soft-reject signal. Name one specific thing.
Hesitating on relocation or service agreement. Both are expected to be a confident yes.
Asking salary in the technical round. Salary discussion belongs in the HR round, not the TR.

Sample problems you'll face

The 2 problems below are the same ones you'll work through in the live session — no surprises. Read the constraints carefully; the AI persona will refer you to the on-canvas card by problem number.

1SQL — Second Highest Salary
Write a SQL query to return the second highest salary from the Employee table. Do NOT use LIMIT or TOP. Defend your approach against duplicate salaries.
Example inputEmployee table: { id, name, salary } Rows: (1, A, 100), (2, B, 200), (3, C, 200), (4, D, 150)
Example outputResult: 150 (since 200 is highest, 150 is second-highest distinct)
- No LIMIT, no TOP clause
- Handle duplicate salaries (DISTINCT or subquery)
- Standard ANSI SQL — Arjun will press on what your query returns if all salaries are equal
2Pattern Printing — Right Triangle
Print a right-triangle star pattern of height N. Pick any language you are comfortable with (C, C++, Java, Python). Walk Arjun through your loop bounds before writing code.
Example inputN = 4
Example output* ** *** ****
- Choose any language
- Correct loop bounds — Arjun will probe off-by-one cases
- Dry-run for N=4 verbally after writing
- Use the canvas to sketch your logic — draw, write pseudocode, or freehand whatever helps you think.

Interview framework

You will be scored on these 5 dimensions. The full rubric with definitions is below.

Project Ownership

Did the candidate name a SPECIFIC personal module, the technology chosen, and one alternative rejected with a one-sentence reason? Team-level we-built answers drop this sharply.

25%

Dbms Recall

Did the candidate explain 3NF with an example, name the three join types correctly, define ACID with isolation, and write the second-highest-salary SQL as a subquery (no LIMIT) that dry-runs cleanly?

25%

Oop Applied

Did the candidate name all four pillars AND give a non-textbook example from their own project for at least three of them? Car-engine or bank-account as only examples drop this sharply.

20%

Coding Hygiene

Did the candidate write the requested pattern or SQL with correct loop bounds, sensible names, and dry-run it verbally for N equals 4 without missing the bug? Frozen attempts and undebugged loops drop this sharply.

15%

Motivation And Logistics

Did the candidate give a why-TCS answer naming a specific TCS thing (BFSI, BaNCS, ILP, Chennai) and a clear yes to relocation and the 1-year service agreement? Generic answers and hesitation drop this sharply.

15%

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

Project Ownership Specificity20%
DBMS Recall Under Pressure20%
OOP Applied To Own Work20%
Coding Dry Run Discipline15%
Why TCS Specificity10%
Relocation And Service Agreement Clarity10%
Resume Defensibility5%

Common questions

What does the TCS Ninja Technical Round actually test for B.Tech freshers in India?

The TCS Ninja Technical Round (TR) is a 20-30 minute conversation that follows the NQT online assessment. It tests five things: your ability to walk through your final-year project and own a specific module, DBMS basics (normalization 1NF/2NF/3NF, joins, ACID, simple SQL queries on Employee/Department tables), the four pillars of OOP with examples from YOUR project (not the textbook car-engine example), one coding question that is usually a pattern print or a SQL query like second-highest salary, and a why-TCS probe. The bar is clarity on basics done correctly, not advanced DSA.

How should I structure my answer when the TCS interviewer asks me to walk through my final-year project?

Open with one sentence on what the system does and who uses it. Then name the specific module YOU built personally, not what your team built collectively. Then name the technology you chose for that module and give a one-sentence reason for choosing it over the alternative you considered. Be ready for the follow-up question why did you choose that which the TCS interviewer asks after almost every technical answer. If you used Spring Boot, MySQL, or a Machine Learning library, expect a deep follow-up on it — if you cannot defend it, the resume entry is hurting you not helping you.

How do I answer the OOP four pillars question without sounding memorised?

TCS interviewers are allergic to the textbook car-engine polymorphism example and the textbook bank-account encapsulation example. Use an example from YOUR final-year project for each pillar. For example: encapsulation as the private fields and public getters on your Patient class in a hospital management project; inheritance as the Admin user inheriting from the base User class; polymorphism as a generateReport method that behaves differently for PDFReport and CSVReport subclasses; abstraction as the AppointmentService interface that hides the database calls from the controller. Two sentences per pillar is enough.

How do I write the SQL query for the second highest salary from an Employee table without using LIMIT?

Use a correlated subquery: SELECT MAX(salary) FROM Employee WHERE salary less than (SELECT MAX(salary) FROM Employee). This works even when there are duplicate top salaries because MAX returns one value. The TCS interviewer specifically says without LIMIT because LIMIT is MySQL-specific syntax and they want to see that you understand subqueries, not just tutorial syntax. Be ready to dry-run the query mentally on a 5-row sample to prove it works.

What pattern printing problem is most commonly asked in the TCS Ninja Technical Round?

The most common is a right-triangle star pattern of height N, in C, Java, or Python. Less common but seen: Floyd triangle (incrementing numbers), Pascal triangle (binomial coefficients), inverted pyramid. The interviewer cares about three things: do your loops have correct bounds (no off-by-one), can you dry-run the code mentally on N equal to 3 to verify, and do you use sensible variable names. Writing the code in 2 minutes and then walking through it for N equal to 4 is the strong signal.

How do I answer the why-TCS question convincingly in the technical round?

Avoid the generic TCS is a good company answer — that is the single most common soft-reject signal. Strong answers name something specific to TCS: the BFSI domain depth (TCS serves 100+ banks globally via the BaNCS product), the scale of the All India NQT funnel and the ILP training programme at Trivandrum or Bhubaneswar, the Chennai delivery centre at Tidel Park if you are from Tamil Nadu, or the specific Tata group culture. One specific reason, defended with one sentence, beats three generic reasons.

What is the TCS Ninja salary package for the 2026 batch and what does that include?

The TCS Ninja base package for the 2026 batch is 3.36 to 3.6 LPA for the Assistant System Engineer Trainee role (UG slightly lower than PG). On top of base, there is a potential 60K performance bonus, access to TCS iON and Xplore learning platforms worth roughly 50K in certifications annually, 22+ paid leaves, relocation assistance, and parental leave. The Digital tier is 7 LPA and the Prime tier is 9-12 LPA — both selected through the same NQT funnel but with a higher technical bar.

Will the TCS interviewer ask me to relocate, and what is the right answer?

Yes, in almost every Ninja interview. The right answer is a clear Yes, I am comfortable relocating to any TCS delivery centre in India. TCS delivery centres span Chennai (Tidel Park, Taramani), Bengaluru, Hyderabad, Pune, Kolkata, Mumbai, Coimbatore, Bhubaneswar, and several others. Saying I prefer Bengaluru only or hesitating on this question is one of the most cited soft-reject signals in TCS Ninja interview reports. The 1-year service agreement is also expected and you should confirm comfort with it.

What does the TCS Ninja Initial Learning Programme (ILP) look like for ASE Trainees?

After clearing all rounds and receiving the joining letter, ASE Trainees go through a 4-6 week Initial Learning Programme at TCS centres in Trivandrum, Bhubaneswar or Chennai. ILP covers a Java or C-Sharp track, DBMS, basic web development, soft skills, and a small capstone project. Confirmation as a permanent ASE is linked to clearing the ILP capstone. Most ASE Trainees are then deployed to a BFSI delivery account in Chennai, Bengaluru, Pune, Hyderabad or Mumbai.

What are the most common reasons B.Tech candidates fail the TCS Ninja Technical Round?

Five repeating failure patterns: listing Spring Boot or Machine Learning on the resume but unable to explain dependency injection or model selection when asked; giving the textbook polymorphism definition (car-engine) when asked for an example from your own project; unable to write the second-highest-salary SQL without LIMIT; freezing on the pattern printing or writing an off-by-one loop you cannot debug; and saying I prefer Bengaluru only or hesitating on the relocation question. False statements on resume or academic record that the interviewer cross-questions are an instant reject.

How does this AI mock differ from a real TCS Ninja Technical Round?

The AI plays Arjun Kumar, a Technical Lead at TCS Chennai BFSI delivery centre. He never breaks character, never praises, never confirms whether your answer was right. He asks one question at a time, follows up with why did you choose that after almost every technical answer, and will push back once on a correct answer to test your conviction. The transcript-backed scorecard at the end names the exact moment where your project ownership, DBMS recall, or OOP example was weak — the kind of feedback no real interviewer ever gives you in time to fix it.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.