The interview process started with an email from the recruiter containing a link to some technical questions. The questions were a bit challenging but fun to complete, as their solutions required out-of-the-box thinking.
Afterwards, a phone interview with the recruiter followed, which seemed to gauge personality.
The recruiter then emailed me a few pages from a PDF with a project to complete for a Skype meeting. I was given seven days to finish it, and the project was quite difficult, so I didn't fully complete it.
The interviewer asked me some questions about how and why I approached certain aspects of the project, then moved on to more general questions to gauge my technical ability. Overall, it was not a bad interview process.
Can you describe the difference between Polymorphism and Inheritance?
When would you want to use a Map versus a HashMap in Java?
What are the pros and cons of using Custom Of The Shelf (COTS) versus Bespoke (custom-made) development of an application? What is your recommendation and why?
The following metrics were computed from 7 interview experiences for the Capgemini Entry Level Software Engineer role in United States.
Capgemini's interview process for their Entry Level Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having negative feelings for Capgemini's Entry Level Software Engineer interview process in United States.