TCS R&I - Intern | On Campus 2025 Interview Experience
Question Details
Hello Everyone! I recently had the opportunity to interview for the position of Project Intern at TCS Research Innovation (RI) which took place through our campus placeme...
Full Details
Hello Everyone! I recently had the opportunity to interview for the position of Project Intern at TCS Research & Innovation (R&I) which took place through our campus placements in March 2025. Recruitment Process Overview Initial Screening Technical Interview
Round1 Initial Screening - CV Shortlisting Duration: 2 weeks A total of 24 candidates were shortlisted based on their CVs. There was no preliminary written test or coding round in our case.
Round 2 Technical Interview Duration: 40 minutes Method: MS Teams Key Questions : Mostly related to the project, in my case ML and deep learning questions. DSA Questions: BST, Complete binary tree, Function pointer, Type casting, Sorting algorithms etc. OOPS Questions: 4 main concepts, Virtual function, Abstract base class, Real life application examples etc.
Note: This was one and only interview round. Additional Tips Prepare a good CV (must). Try to keep a project related to the preference you choosed while applying for the role. Final Outcome Out of 24 shortlisted students, 7 of us were selected, and I was one of them.
About This Question
This is a reported interview question from a tcs interview for a mle role (intern level) during the recruiter round reported in 2025.
It covers the following topics: Binary Tree, Sorting, Ml, Trees .
Topics
More Tcs Interview Questions
About Tcs Interview Reports
This question was reported by a candidate who interviewed at Tcs. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Tcs are the higher-signal extractions to take from this report.
For broader preparation context, the Tcs interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Tcs reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Tcs Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Tcs reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.