Capgemini interview experience (2025 - On Campus)
Question Details
Recently, I had the opportunity to attempt the Capgemini's Exceller on-campus diversity hiring-female only, grabbed the chance, and boom, the interview went something like...
Full Details
Recently, I had the opportunity to attempt the Capgemini's Exceller on-campus diversity hiring-female only, grabbed the chance, and boom, the interview went something like: (describing every round in detail as below). The interview was well structured. Recruitment Overview Process Online Assessment Coding Assessment Communication Assessment
Round 1 Assessments Technical assessment : Had 25 questions; 15 pseudocodes based heavily on finding the output for array, stack, and queue; operations on bitwise and arithmetic operators, post and pre-increment operators (Medium-Hard level). 10 MCQs; all basic questions regarding programming languages and individual DSA theory (Easy peasy). English Proficiency Assessment: MCQs based on grammar, antonyms and synonyms, and fill in the blank with the correct word tense (Smooth & Easy level). Cognitive test: Including games to play, i.e, puzzles to solve within a time limit (Focus and practice helps!) and 75 curated psychometric questions (Individual responses).
Round 2 Coding Assessment Well, only the top-performing students were able to attempt this round; the rest were moved to the Communication round. Unfortunately, I wasn't one of them. But hey, I qualified for the Spoken English (Communication) round, so yaayy.
Round 3 Communication Assessment Consisted of four sections: read and repeat, hear and repeat, listen to a conversation and answer the questions, and lastly, a topic was given; 30 seconds to think about it and 45 seconds to speak about it, sounds tough right? but actually pretty do-able if you are NOT distracted. Tip is to focus and try remembering because ticking time waited for none and no repetition was allowed. :-(
Round 4 Technical Interview The interview lasted around 25-30 minutes and the few of the questions were asked as below : Self-Introduction, what is your final year project, projects made over the years, programming languages I feel comfortable with, basics of SQL, difference between primary and foreign key, what is union and union all and their difference, oops concept with example; what are break, continue and pass, concepts of cpp like pointers, friend function and a program to print palindrome numbers in Python. Agile methodologies and describing the models like waterfall, spiral, SDLC and its stages, and a brief questioning for Analytics tools in Google Analytics (I had mentioned Google Analytics in my resume hence the specific question). Final Outcome Heads-up, every round was an elimination round. The interview round was focused mostly on resume, make sure you thoroughly go through the resume, every detail mentioned and certifications done should be revised before the interview. Result? I'm waiting, regardless of the outcome whatever it may be; I hope this experience helps! Toodles .
About This Question
This is a reported interview question from a capgemini interview for a swe role during the oa round reported in 2025.
It covers the following topics: Strings, Bit Manipulation, Sql, Networking, Stack Queue, Queue, Arrays, Stack .
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.