Real, anonymous reports from people who interviewed for Software Engineer at TATA ELXSI, newest first and distilled into what to expect across the loop.
My process felt compact but very evaluation-heavy from the start. After the initial stage, I hit a first round that involved multiple coding tasks—essentially two problems with only a few clarifying constraints. Since I was interviewing as a fresher, I also had to explain my final-year project end-to-end, and the interviewer kept asking questions that followed directly from what I said.
My interview journey was very structured and ran like a sequence of timed gates. It began with a screening step where they looked at my resume and kept the questions easy to moderate, with a focus on staying close to my project and the story I’d already built on my CV. After that, I went into assessments that included a mix of aptitude-style evaluation and technical coverage.
The interview process typically follows a structured sequence: an initial assessment (aptitude and coding), followed by one or two technical interviews, and concluding with an HR round. Candidates noted that timelines for onboarding could be lengthy, with delays in receiving offer letters after clearing interviews.
Technical interviews primarily assess coding skills and fundamental programming concepts, often tied to the candidate's resume and project experience. Topics frequently include C/C++, data structures, and basic algorithms, with some interviews incorporating system-level concepts and practical problem-solving.
The HR round generally focuses on fit, communication, and personal background, with questions about strengths, relocation preferences, and project experiences. This round tends to be conversational rather than strictly evaluative, allowing candidates to express their motivations and interests.
Overall, candidates described the difficulty of the interviews as average to moderate, with a focus on clarity of thought and structured responses rather than obscure or overly complex questions. The pace of the interviews can feel demanding due to the need for real-time problem-solving and explanation.
Candidates are often required to discuss their prior projects in detail, explaining their roles, technical choices, and execution strategies. This aspect emphasizes the importance of being able to articulate one's experiences and thought processes clearly during the technical discussions.
Many candidates expressed a desire to better prepare for the project discussion aspect and emphasized the importance of being able to communicate technical concepts effectively. Some noted that they felt unprepared for the potential delays in the hiring process after interviews.