Systems Engineer applicants have rated the interview process at Tata Consultancy Services with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 82% positive. To compare, the company-average is 72.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Systems Engineer roles take an average of 12 days to get hired, when considering 413 user submitted interviews for this role. To compare, the hiring process at Tata Consultancy Services overall takes an average of 13 days.
Common stages of the interview process at Tata Consultancy Services as a Systems Engineer according to 413 Glassdoor interviews include:
One on one interview: 19%
Skills test: 15%
Background check: 15%
Group panel interview: 13%
IQ intelligence test: 10%
Personality test: 10%
Presentation: 8%
Drug test: 5%
Phone interview: 4%
Other: 2%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 months. I interviewed at Tata Consultancy Services (Bengaluru) in Jun 2025
Interview
The interview was scheduled in Banglore, where they asked me about basic DSA questions, Basic SQL queries and asked me write and explain the code snippet with eg and asked some basic HR related questions
Other Systems Engineer Interview Reviews for Tata Consultancy Services
I interviewed at Tata Consultancy Services (Chennai)
Interview
i went for a second round and there is lot of people they asked me about deep qns but i am not prepared for that so i am not answered properly so they rejected me
I interviewed at Tata Consultancy Services (Bangalore Rural)
Interview
The interview began with questions based on my resume, where I explained my skills and experiences. It then moved to a detailed discussion of my final year project, focusing on my role, technologies used, and challenges faced. I was asked basic Python and SQL questions to test my understanding of core concepts like queries, functions, and logic building. The overall focus was on clarity, fundamentals, and how effectively I approached problem-solving rather than complex coding.