QA Engineer applicants have rated the interview process at Tech Mahindra with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 64.1% positive. This is according to Glassdoor user ratings.
Candidates applying for QA Engineer roles take an average of 5 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Tech Mahindra overall takes an average of 15 days.
Common stages of the interview process at Tech Mahindra as a QA Engineer according to 1 Glassdoor interviews include:
Skills test: 50%
Phone interview: 50%
Here are the most commonly searched roles for interview reports -
I completed three rounds of interviews successfully. After that, the HR discussion and salary discussion were completed, and I also submitted all the pre-offer documents. Later, another project discussion round was scheduled, which I attended as well. However, after all these steps, I was informed that the position has been put on hold. It feels disappointing after investing so much time and effort throughout the interview process.
I applied through college or university. The process took 6 months. I interviewed at Tech Mahindra (Bengaluru) in Sep 2022
Interview
It was good interview process for freshers. Asked about java programming, oops. Hiring management is good. Written simple java programming codes. It was about 30 mins interview. Difficulty level is average
Interview questions [1]
Question 1
How do you contribute to team if you as a team lead. What actions would you take
I applied online. The process took 1 week. I interviewed at Tech Mahindra (Pune) in Jan 2024
Interview
The interviewer asks questions about domain and automation testing.
Automation Framework, case study, agile, scrum, QA process, bug life cycle, communication etc.
overall the experience is good but 4 rounds of interviews are too time-consuming in single day
Interview questions [1]
Question 1
describe the Automation Framework.
bug life cycle.
what QA process do you follow?
what will you do if your team receive a production bug?
whats your role in a production incident?