Software Engineer applicants have rated the interview process at Capgemini Engineering with 2.9 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 80% positive. To compare, the company-average is 65.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 7 days to get hired, when considering 145 user submitted interviews for this role. To compare, the hiring process at Capgemini Engineering overall takes an average of 19 days.
Common stages of the interview process at Capgemini Engineering as a Software Engineer according to 145 Glassdoor interviews include:
One on one interview: 28%
Skills test: 21%
IQ intelligence test: 11%
Presentation: 9%
Group panel interview: 8%
Background check: 7%
Personality test: 7%
Phone interview: 5%
Drug test: 2%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1 day. I interviewed at Capgemini Engineering (Chennai) in Nov 2012
Interview
I applied through Online and took 2 day , First round will be written and second round will be technical round, The written will on link list and socket programming ,Second round will be on pure c,linux internals and socket programming , not in dept but trick questions.
Interview questions [1]
Question 1
Almost all questions are related socket programming and link list .
they will usually ask more about microservices, how do we handle request, ask us to design the api for an application.
they will have L1 and L2 round for overall interview process.
3 interviews, 2 technical and 1 hr. Medium leetcode. Hr was good to know about the team and company culture. Did not upfront discuss comp for the role. Project detail was not discussed but team detail was good
I applied through a staffing agency. I interviewed at Capgemini Engineering (Madrid)
Interview
La primera fase consistía en una entrevista con Recursos Humanos para ver trabajos previos, expectativas laborales, etc. Una parte en inglés.
La segunda fase fue mas técnica con el jefe de equipo, con bastantes preguntas técnicas y específicas del lenguaje de programación a usar.