Real, anonymous reports from people who interviewed for Software Engineer at Tata, newest first and distilled into what to expect across the loop.
My process started after an offline NQT exam. I was called in after that, and the full day included document verification and then a screening-style interview. The questions were mostly light and conversational—things like hobbies—and they also asked about programming in a very basic way, including the idea of naming or discussing any one programming language.
After my resume got shortlisted based on CGPA and how relevant it looked for the role, I went through interviews that felt fairly structured. The technical part had two separate interviews, and the questions leaned into core technical topics rather than anything too obscure. After that, there was a distinct HR round.
The interview process typically begins with an online test followed by a series of technical and HR interviews, often structured in a clear sequence. Candidates noted that the timeline can vary, with some experiencing a quick decision-making process while others faced delays and confusion.
Candidates reported a strong emphasis on fundamental programming concepts, particularly in languages like Java, C, and SQL, with many questions designed to assess basic understanding rather than advanced problem-solving skills. Some interviews also included domain-specific technical discussions relevant to the role.
The HR rounds often involved personal and straightforward questions aimed at assessing cultural fit and communication style, rather than deep behavioral storytelling. Candidates described these sessions as relaxed and conversational, focusing more on personality than technical mastery.
Several candidates expressed frustration with the communication throughout the process, citing a lack of clarity regarding next steps and outcomes. While some found the interviews straightforward, others felt the process was disorganized and left them without closure.
Overall, candidates described the difficulty of the interviews as average, with many feeling that the focus was on validating basic knowledge rather than presenting challenging problems. This led to a perception that the interviews were more about checking fundamentals than rigorous evaluation.
Candidates suggested focusing on core programming concepts and being prepared for both technical and personal questions. Many emphasized the importance of clear communication and the ability to articulate one's background and experiences effectively.