
Capgemini Business Analyst candidates report resume-led screening alongside varied technical, business-case, presentation, and client-facing assessments. Prepare your project examples and adapt technical revision to the assigned domain.
$67K
Avg. Base Comp
$120K
Avg. Total Comp
2-4 rounds
Typical Rounds
2 weeks
Process Length
Capgemini Business Analyst interviews do not appear to follow one fixed script. Candidates describe anything from a short, profile-focused two-round process to written assessments, technical and managerial discussions, and an assignment or presentation. Your resume and project experience are the recurring center of gravity. Be ready to explain your responsibilities, daily work, the problem you faced, the action you took, and why you chose that approach.
Several candidates were asked to apply structured reasoning to business situations rather than simply define concepts. Reports include scenario questions, business cases, and a client-style presentation of a digital-product journey followed by detailed questions. Practice stating assumptions aloud, organizing an answer before giving it, and tailoring your explanation to a client or stakeholder audience.
Technical depth is notably team- and domain-dependent. Some candidates encountered SQL, Agile delivery concepts such as story points and sprint ceremonies, or data and programming fundamentals; others discussed skills explicitly listed on their resume or questions tied to a business domain. Revise the technologies and workflows in the specific job description, but prioritize accurate examples from your own work over a generic technical checklist.
A later conversation may cover motivation, availability, workplace scenarios, conflict resolution, and how you manage tasks or deadlines. The exact sequence varies by opening and domain. Prepare concise answers for why Capgemini, why the role, and how your background connects to the opening, while keeping your case and project explanations clear enough for follow-up questions.
Synthesized from 18 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.
The process felt more like being examined on the Business Analyst textbook than having a conventional interview. My first stage was about an hour of rapid-fire competency questions. They touched on my experience, but the emphasis was strongly on BA theory and delivery practices, including questions such as how story points work and why teams hold sprint ceremonies. It was demanding because they expected direct, structured answers rather than a broad discussion of real-world experience.
The second stage lasted around two and a half hours and was the most unusual part. I had to prepare a presentation for a client explaining what it would be like to go through a digital product, then present it as though the interviewers were the client. After the presentation, they questioned me on it for roughly an hour and a half. At the end, they described what working at Capgemini would be like. The format was very formal and assessment-heavy; it felt closer to an oral exam than a collaborative conversation.
Based on the questions and the way the rounds were run, they seemed to be looking for someone who could follow a very structured BA approach and clearly explain Agile and client-facing concepts. I had applied because the market was slow, but by the end I felt the role was not a good fit for my background or the compensation. I did not receive an offer. My advice is to prepare concise, textbook-clear explanations of core BA concepts such as story points and sprint ceremonies, and practice presenting a digital-product walkthrough to a client while defending your choices in detailed follow-up questions.
Prep tip from this candidate
Prepare for an assessment-style process: be able to explain story points and sprint ceremonies crisply, then practice a client-facing presentation that walks through a digital product and withstands extended follow-up questioning.
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 | |
|---|---|
| SELECTive Wine Connoisseur | |
| Size of Joins | |
| P-value to a Layman | |
| Largest Salary by Department | |
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Late Deliveries | |
| Swap Variables | |
| Addressing Data Quality Issues | |
| Scalable Data Pipelines | |
| Alternative Vendor Tradeoff | |
| Popular Products | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Relational Migration | |
| Top Three Salaries | |
| Prime to N | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Closest SAT Scores | |
| Bagging vs Boosting | |
| Top 3 Users | |
| Find the Missing Number | |
| 500 Cards | |
| Month Over Month | |
| Paired Products | |
| First Touch Attribution | |
| Experiment Validity |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an introductory recruiter or HR conversation covering background, availability, salary expectations, notice period, communication, and motivation. Some reports instead begin with an online or written assessment, so the opening format may depend on the specific opening.
Candidates report technical interviews tied closely to prior projects, daily responsibilities, and listed skills. Depending on the team, topics may include SQL, Agile delivery concepts, requirement understanding, or domain-specific workflows; prepare to explain how you used relevant skills in practice.
Some candidates report scenario questions, business cases, logic tests, guesstimates, an assignment, or a client-style presentation of a digital-product journey. These formats may test how clearly you frame assumptions and communicate a recommendation under follow-up questions.
Candidates report a later managerial or HR discussion on workplace scenarios, conflict resolution, deadlines, project history, compensation, and role expectations. This may be conversational, but specific examples of your judgment and collaboration remain useful.