Java Lead applicants have rated the interview process at Capgemini 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 66.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Java Lead roles take an average of 21 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Capgemini overall takes an average of 22 days.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 6 weeks. I interviewed at Capgemini (Bengaluru)
Interview
Got call from HR regarding opportunity and scheduled L1 interview, later got positive feedback after couple of weeks. HR called for salary discussion and during the conversation 8 I had been told that there is no matching opportunity for my preferred location which is Bangalore, this is unacceptable, HR only called and took all the details regarding location preference, CTC expected CTC etc.. Later they only coming back and saying that no opportunities. Not sure if this is how Capgemini hiring process works.
Interview questions [1]
Question 1
Questions in dept on all areas from core Java to spring boot and deployment strategies.
The process took 1 day. I interviewed at Capgemini (Chennai) in Apr 2025
Interview
Coding in Java and verbal questions on spring boot. Some questions that I remember are like what is sql injection, hashing collision , annotation in spring boot, implementation of composite key in spring boot etc
Interview questions [1]
Question 1
Given an array of repeating numbers , find the first two repeating numbers.
1. Tell me about yourself 2. Java 8 streams Coding question 3. Questions on REST APIs and Microservices 4. which microservices patterns have you used in project 5. have you used saga or circuit breaker pattern
Interview questions [1]
Question 1
1. Remove second non repeating character from string using java 8 streams
2. What is eureka and feign
3. when will you use soap and when rest
4. disadvantages of rest apis
5. fail-fast and fail safe collections
6. idempotent methods in rest api