Capgemini Interview Experience on Superset Platform
Interview Experience
I appeared for my Capgemini interview through the Superset platform. The entire process consisted of four rounds, each of which was elimination-based. Here is an overview ...
Full Details
I appeared for my Capgemini interview through the Superset platform. The entire process consisted of four rounds, each of which was elimination-based. Here is an overview of the rounds and my interview experience:
Round 1 Online Assessment The first round was an online assessment comprising several sections: Technical Assessment: This included aptitude questions, output-based questions, and cloud- and networking-related questions, all in MCQ format. The difficulty level was moderate, and this was an elimination round. English Test: After clearing the technical assessment, the English test followed. It was relatively easy and focused on basic language skills. It also included a paragraph-writing task of 200 words on simple topics. Gaming-based Round: This section was easy and featured logical and analytical games. Clearing this round was essential to move to the next stage. Some students were directly shortlisted for the third round, while others had to appear for the second round, depending on the company's shortlisting criteria.
Round 2 Coding Round for Higher Package Candidates Students shortlisted for higher packages appeared for this round, which includes two coding questions. Unfortunately, I did not attempt this round, so I am not familiar with the specific types of questions included. However, my friends who participated in this round mentioned that the difficulty level was moderate, with questions based on arrays, graphs, and strings. Clearing this round was essential to move to the next stage for higher package students.
Round 3 Communication Round The third round tested communication skills, focusing on speaking, clarity.
Round 4 Interview Process The final round was the interview, conducted on the Superset platform. The interview was scheduled to start at 1:30 PM and lasted approximately 30 minutes, concluding at 2:00 PM. Here's how the experience went: Interviewer: Introduce yourself. Me: Answered. Interviewer: Asked several questions related to DBMS, as I had mentioned it in my resume. These included SQL-based questions. Me: I answered four out of the five or six questions they asked. Interviewer: Asked me to write a Fibonacci series code on a notepad. Me: Answered in detail and explained each iteration thoroughly. Interviewer: Asked about one of my favorite projects. They asked why I chose to work on it, what I am currently working on, and what improvements I would add to the project. Me: I explained the project I am currently working on. Interviewer: Asked some OOPs-based questions, such as those on inheritance, classes, and objects. Me: Answered. Interviewer: Do you have any questions for me? Me: Asked about my role at the company, and they provided a detailed response. Overall Experience The interview process was smooth and positive. The interviewer was patient and encouraging throughout the discussion. Each round was designed to test a specific skill set, and the progression through the rounds felt structured and logical.
About This Question
This is a candidate experience report from a capgemini interview for a pm role during the oa round reported in 2025.
It covers the following topics: Arrays, Strings, Graphs, Sql, Math .
Difficulty rating: Easy
More Capgemini Interview Questions
About Capgemini Interview Reports
This question was reported by a candidate who interviewed at Capgemini. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Capgemini are the higher-signal extractions to take from this report.
For broader preparation context, the Capgemini interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Capgemini reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Capgemini Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Capgemini reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.