Tata Consultancy Services Data Analyst Interview Guide

We've seen TCS evaluate Data Analyst candidates in a way that's deceptively simple but easy to underestimate: the interview is essentially a line-by-line audit of your CV. Multiple candidates described interviewers moving directly from the self-introduction into project deep-dives, asking not just what the project was but what bottlenecks existed, what validation steps were taken, and how decisions were made end to end. If you listed SQL, Python, or ETL work, expect to write a query or explain a pipeline live — not just define terms. One candidate faced a four-person panel on Teams with live screen-sharing; another had a combined technical-and-manager round where both interviewers probed the same project from different angles.

A recurring pattern is that TCS cares more about practical reasoning under realistic constraints than algorithmic difficulty. The SQL questions we've seen — top customers by month using window functions, duplicate row handling, largest salary by department — are moderate in complexity but require clean execution. Beyond SQL, candidates reported a broader technical surface than expected: pandas date parsing, OOP principles, and even Java threads and exception handling for an analyst title. The non-obvious signal is that TCS seems to be checking general IT fluency alongside analytics, especially for consulting-track roles where you may be placed across varied client environments.

The tone is consistently described as supportive rather than adversarial, but that calm atmosphere can mask how closely interviewers track inconsistencies. Candidates who admitted gaps honestly and redirected to what they did know fared better than those who bluffed into advanced territory. Operational honesty — knowing your own work precisely and communicating limits without flinching — appears to be what separates accepted offers from rejections here more than raw technical depth.