The technical interview leans heavily on CS fundamentals: OOP concepts like inheritance and polymorphism, OS fundamentals like process scheduling and memory management, DBMS with normalisation and basic SQL, and discrete mathematics. Expect rapid-fire questions at moderate depth, not hour-long deep-dives into a single topic. Final-year project explanation gets 5-6 follow-ups: be ready to defend architecture decisions you may have made as a group months ago. The Ninja interview is conversational and 30-45 minutes long: it's designed to check whether you can explain technical concepts clearly to a future client, not whether you can solve competitive programming problems. Candidates who over-prepare for hard DSA at the expense of CS fundamentals often underperform in Ninja rounds.
Recruitment process
- TCS NQT Online Test: qualify at Ninja threshold score
- Technical Interview (30–45 min): CS fundamentals and project walkthrough
- Managerial Round (MR): behavioral and team-fit assessment
- HR Round: relocation, shift flexibility, joining timeline
Interview rounds
- Technical Interview (30–45 min): OOP (4 pillars with real examples), DBMS (normalisation, joins, indexes), OS (process vs thread, memory management), basic DSA. Project deep-dive: be ready to defend every design choice
- Managerial Round (20–30 min): Teamwork story, conflict resolution, 'why TCS specifically', 5-year goal. Non-generic answers are required: interviewers flag rehearsed answers
- HR Round (15–20 min): Relocation and night-shift availability are binary: Wipro and TCS both require explicit yes. CTC discussion, bond period acknowledgement, joining date
STAR for technical framework
- Situation (project context)
- Task (your specific role)
- Action (what you actually built)
- Result (measurable outcome).
Practice questions
- 01Practise
Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.
Standard - 02Practise
What is the difference between a class and an object? Give an example.
Warm-upTCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives. - 03Practise
Write a SQL query to find the second-highest salary in a department.
Warm-up - 04Practise
What is normalisation in databases? When would you de-normalise?
Warm-up - 05Practise
What's the difference between a stack and a queue? Give a real-world use case for each.
Warm-up - 06Practise
Given a stream of integers, design a data structure that returns the median in O(log n).
Intense - 07Practise
You have a service that's slow only on Tuesdays. Walk me through how you'd debug.
StandardGoogleyness: structured debugging, hypothesis-driven, instrumentation-first. - 08Practise
Here's 200 lines of payment-processing code with several intentional bugs. Find them and explain the production impact of each.
IntenseStripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs. - 09Practise
Explain webhooks vs. polling for a developer who has never built a payment integration. You have 4 sentences.
StandardStripe values writing clarity above almost everything. Length-constrained explanation tests prioritisation of ideas. - 10Practise
Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?
IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
