Test Lead applicants have rated the interview process at Tech Mahindra with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 64% positive. This is according to Glassdoor user ratings.
Candidates applying for Test Lead roles take an average of 45 days to get hired, when considering 5 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 Test Lead according to 5 Glassdoor interviews include:
Background check: 20%
IQ intelligence test: 20%
Group panel interview: 20%
Phone interview: 20%
One on one interview: 20%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 1 day. I interviewed at Tech Mahindra (Bengaluru) in Nov 2023
Interview
Interview was good. It consists of 2 technical and 1 HR round. My wife referred me through her connections. Interviewer was polite and had sound knowledge on technical parts. If you are good at technical then its basically equal to getting the offer provided your salary expectations meets their threshold.
Interview questions [1]
Question 1
Good technical questions were asked like singleton classes and its uses. Also regarding how to handle delivery at difficult and unexpected situations.
The interview went well and the first round of interview is around 1 hour which includes all the basics of testing and programming concepts of Java. Had a good interaction with Client in Second round and the discussion is all about the previous companies and projects
Interview questions [1]
Question 1
Testing concepts, Real time testing scenarios, Java Programming
I applied online. The process took 2 weeks. I interviewed at Tech Mahindra (Toronto, ON)
Interview
It was an in-person interview. The first round was internal, and the second was with the client. Questions asked were about the QA process. Some questions were about the domain. And qa methodologies