Candidates describe Capgemini Software Engineer interviews as a mix of HR conversation and technical rounds that focus on your own projects, core Java and Spring Boot. Feedback timing ranged from about a week to slow, follow-up-heavy waits.
$113K
Avg. Base Comp
$130K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Capgemini Software Engineer interview as less about algorithm puzzles and more about whether you can explain your own hands-on work clearly. One recent candidate who did not get an offer said the HR interview asked about hobbies and teamwork, while the technical interview focused on what they had actually built with the technology they applied for. Another candidate, also without an offer, was asked to confirm a Java and Spring Boot background and then spoke with HR, with an English test somewhere in between.
The most detailed technical account came from a 30-minute interview where the candidate shared their screen and wrote code in Notepad, finding the second-highest element in an array without using two loops. The conversation then moved to Java 8 features, HashMap versus ConcurrentHashMap, abstract classes versus interfaces, Spring Boot basics, Git conflict handling and how work moves through GIT, SIT and UAT. Another candidate recalled Java OOP questions in an L1 round that was mostly technical.
Pacing and communication vary. One candidate who received an offer had a technical round and an HR round on the same day, waited in their Superset account for the second round to appear, and heard back within about a week. Another had to chase feedback after L1 while L2 scheduling dragged on. Prepare two or three projects you can walk through end to end, rehearse the Java fundamentals on your resume, and plan to follow up with your recruiter after each round.
Synthesized from 223 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Capgemini process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Capgemini
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Largest Salary by Department | |
| Top 3 Users | |
| SELECTive Wine Connoisseur | |
| Size of Joins | |
| Real-Time Transaction Streaming | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Find Duplicate Numbers in a List | |
| Hurdles In Data Projects | |
| Transformer Encoder Layer | |
| Digitizing Student Test Scores | |
| RAG Strict Source Control | |
| Count Transactions | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Swap Variables | |
| Offer Matching API Design | |
| Cloud-Agnostic Deployments | |
| Scalable Data Pipelines | |
| Testing Constraints | |
| Alternative Vendor Tradeoff | |
| Client Solution Pushback | |
| Relational Migration | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Prime to N |
Synthesized from candidate reports. Individual experiences may vary.
One candidate said HR screened their CV first, and that the HR interview that followed was more personal than technical. They were asked about hobbies and how they work in a team, so concrete examples of collaboration were more useful than general claims about being a good teammate.
Technical rounds centered on the technology a candidate applied for and their own project work. One candidate was asked to confirm a Java and Spring Boot background, and another described mostly technical L1 questions on Java OOP concepts. In a 30-minute interview, one candidate wrote code in Notepad to find the second-highest array element without two loops, then discussed Java 8, HashMap versus ConcurrentHashMap and Spring Boot basics.
Beyond coding, one candidate was asked about Git conflict handling, Agile tickets and user stories, and the GIT, SIT and UAT flow used in projects. Another reported taking an English Mocha test between the technical interview and HR discussion. These came up in single accounts, so treat them as possible rather than standard.
Later stages differed by candidate. One had a technical round and an HR round on the same day and heard back within about a week. Another described an L1 technical round followed by an L2 round whose scheduling dragged on, and said they had to follow up repeatedly for feedback.
