Software Tester applicants have rated the interview process at Cognizant with 2 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 69.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Tester roles take an average of 3 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Cognizant overall takes an average of 17 days.
Common stages of the interview process at Cognizant as a Software Tester according to 2 Glassdoor interviews include:
One on one interview: 33%
IQ intelligence test: 17%
Skills test: 17%
Background check: 17%
Personality test: 17%
Here are the most commonly searched roles for interview reports -
I applied through college or university. The process took 4 weeks. I interviewed at Cognizant in Nov 2020
Interview
about yourself about project basics of data structure and algo, basics of relational data base and management system basics of object oriented programming language and basics of one particular language
I applied online. I interviewed at Cognizant (Chennai) in Apr 2026
Interview
tell me about yourself and testing related questions it can be average one some asked easy and some like harder one and general questions are asked some questions are easy to answer
The interview process was very smooth and easy. It was a great overall experience, and the HR was also supportive. The interviewer was extremely friendly and made me feel comfortable, which helped me answer confidently.
Interview questions [1]
Question 1
about my skills ,education,basic coding question,hr based questions
I applied online. The process took 2 weeks. I interviewed at Cognizant (Ciudad de Mexico) in Apr 2025
Interview
Por medio de llamada telefonica y una videollamada tuve charla con reclutadores sobre mi formacion como tester y mi nivel de ingles, mis dudas acerca de la empresa, ubicación, prestaciones, etc
Interview questions [1]
Question 1
Que herramientas he usado para llevar un seguimiento de errores