Taro Logo

Java Developer Interview Experience - India

August 1, 2016
Negative ExperienceNo Offer

Process

I arrived at the venue at the scheduled time of 9 AM. It took them over 1 hour and 30 minutes to process resumes and send all candidates to an open hall. After another hour or so, an HR representative arrived and took me to a conference hall. Some basic Java questions were asked, and I was done with that stage. At 12 PM, I was asked to wait for the next round. I waited, we waited, and all waited... None of us had any idea when they would conduct the next round. I had 3 more interviews scheduled for the same day. All were missed due to the significant delay in their process. At 2 PM, I was asked to go for lunch. Another hour passed. Then, I was called for the next round. The surprising part was that the client was ADP. They kept us waiting until the client representatives arrived. I had a high-level technical discussion with the ADP representative. I was sure that I covered over 85% of the questions. I was overwhelmed with joy.

However, the result came back negative. I couldn't believe the words, 'You can leave for the day.' Were they kidding me? If my technical standards were not up to the mark, why did that person interview me for over 1 hour and 15 minutes? I was disappointed beyond my control.

I went to HR and asked, "You should have informed me in the mail beforehand that the interview was for ADP. Their interviews feel like a game; they play with desperate candidates." I went home, recollected all the interview questions, and verified them online. I was correct in more than 85% of the questions. If they expect 100%, candidates would prefer Google, Facebook, or Microsoft, not ADP or Capgemini. Remember this.

Questions

Why use a hash map and explain this data structure in detail.

Hibernate and session management.

Project architecture.

Dependency injection in Spring.

Cache in Hibernate.

Sorting based on customized logic.

Thread management in depth.

JavaScript objects.

What are global variables in JavaScript and how to declare them.

Load factor and its functionality.

Linked list data structure.

Struts2 and Spring differences.

Hibernate tags and HBM file syntax.

Etc...

Was this helpful?

Interview Statistics

The following metrics were computed from 79 interview experiences for the Capgemini Java Developer role in India.

Success Rate

18%
Pass Rate

Capgemini's interview process for their Java Developer roles in India is very selective, failing most engineers who go through it.

Experience Rating

Positive47%
Neutral11%
Negative42%

Candidates reported having mixed feelings for Capgemini's Java Developer interview process in India.

Capgemini Work Experiences