Academic requirements
Marks: 6.0 / 60% floor across 10th, 12th, graduation
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT and related)
Year: Final year + recent grads within ~2 years
Backlogs: None active at selection; clear before joining
Capgemini is a global consulting, technology services, and digital transformation company. Founded in 1967, Capgemini operates in 50+ countries and provides services in cloud, AI, cybersecurity, and digital transformation. Capgemini India is one of the top recruiters of engineering graduates, with large engineering campuses and Exceller fresher tracks.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Good fit: You can dry-run loop logic on paper, you do not panic when an OA turns into mini-games, and you are fine relocating for a project. Internships help on resume screens but will not save a blank Coding Benchmark.
Harder path: You only practiced IndiaBix aptitude and never traced Pseudocode; you switch languages every week; you treat communication rounds as “HR fluff.” Capgemini’s late-stage drops are often location, bond/training questions, or a shaky project story - not a surprise DSA hard problem.
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT, college CGPA list | Pseudocode bar, coding tiering |
| Exceller (Superset / careers) | Resume volume; open registration windows | Still expect OA + Coding Benchmark + interviews |
| Hiring events / fairs | Venue and schedule | Same technical filters |
Campus path (typical): college registers → PPT → resumes via placement cell → proctored OA → Coding Benchmark → tech + HR (campus or virtual) → offers. Advantages: familiar venue, peer energy, season-aligned slots.
Exceller path (typical): register on Superset / careers → assessment link after screen → same Pseudocode / games / Coding Benchmark ladder → interviews. Advantages: more attempts per year if your campus missed Capgemini. Expect a denser applicant mix.
Off-campus does not mean easier Pseudocode. It often means more applicants fighting the same CoCubes / Superset / SAB stack. If your CGPA sits near 6.0, spend energy on tracing and one clean coding AC - not on hunting a mythical lower cutoff blog post.
Yes for eligibility on many drives. No as a substitute for Stage 1. Capgemini’s quiet filter is Pseudocode + game-based aptitude before anyone cares about your CGPA story. Put one honest project on the resume (CRUD, automation, small full-stack) and be ready to explain it in 45 minutes - panels still dig projects even when coding was only medium.
Gap years and backlogs: a gap over about two years is the usual hard stop students report. Active backlogs at selection are a common reject; plan to clear them before offer paperwork either way. Full-time degrees only - part-time paths are not the fresher Analyst route described here.
Capgemini Certifications: after joining, Capgemini University and cloud/SAP paths matter more than pre-join certificate stacks. Optional reading: certifications.
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 6.0 CGPA / 60% at 10th, 12th, and graduation | Safe shortlists often sit nearer 70-75%; 80%+ helps premium chatter |
| Degree | B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT and related) | Full-time only |
| Branch | CSE, IT, ECE, EE, Mechanical, Civil, related | Strong coding helps adjacent branches on some drives |
| Year | Final year + recent grads (~2 years) | Entry roles also take up to ~2 years experience in some posts |
| Backlogs | No active backlogs at selection | Clear before joining paperwork |
| Gaps | Max ~2 years education gap | Have a clean story |
| Age | Often 18-28 for fresher tracks | Drive-dependent |
| Nationality | Indian citizens for India roles | Confirm international eligibility on the posting |
| CGPA range | Rough chances | Reality check |
|---|---|---|
| 6.0-6.9 | Eligible | You need strong Pseudocode + Coding Benchmark |
| 7.0-7.9 | Average selected cluster | Matches many shortlists students describe |
| 8.0+ | Stronger shortlist odds | Still loses if game-based / coding collapses |
Academic requirements
Marks: 6.0 / 60% floor across 10th, 12th, graduation
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT and related)
Year: Final year + recent grads within ~2 years
Backlogs: None active at selection; clear before joining
Branch & programming
Branches: CSE, IT, ECE, EE, Mechanical, Civil, related
Coding languages: C, C++, Java safe for Benchmark; Python rules vary by invite
Experience: Freshers and up to ~2 years for some entry posts
Minimum CGPA required (candidate-reported): 60% or 6.0 CGPA across 10th, 12th, and graduation. That is the usual Analyst / Exceller floor - not a promise that 6.0 alone gets you shortlisted when your campus prints a tighter list. Always verify the drive notice.
Capgemini does not publish one universal India cutoff for every Exceller and campus drive. Numbers below synthesize campus notices, candidate write-ups, and placement-cell mailers as of August 2026. Your placement email wins.
What that means day to day: a 7.8 CGPA who freezes on nested-loop Pseudocode usually loses to a 6.4 who traces dry-runs calmly and ships one Coding Benchmark AC. Capgemini’s “services + digital” story matches how drives feel - volume hiring with a quirky first filter, not a LeetCode-hard product bar.
Download 2026 Capgemini placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Capgemini papers are simulators for Pseudocode stamina and Coding Benchmark triage, not leaked live exams. Themes repeat more than exact clones. If you can finish a 2024 pack under time, a 2026 Stage 1 still feels familiar even when the game-based module is new.
| Round (typical) | What to practice |
|---|---|
| Pseudocode / Game-Based | Loop/array tracing, adaptive pressure, attention games |
| Quant + English | Percentages, P&L, time & work, RC, grammar |
| Coding Benchmark | 2 easy-medium problems / 45 min; tier mapping |
| Interviews | OOPs, SQL, OS, projects, Why Capgemini |
Across recent drives, the same families show up again and again:
Use year pages for pattern depth; use the PDF for timed full runs.
How to use a paper (not just “solve it”): time the Stage 1 block the way your invite says; mark every Pseudocode question you guessed; rewrite any coding answer that would fail edge cases; then spend 15 minutes listing which tracing idea you missed. Three reviewed papers beat ten skimmed ones. When a game-based style module appears in a pack, actually play similar attention/memory drills - reading about games does not build the muscle Capgemini tests.
Capgemini’s Pseudocode questions rarely need exotic libraries. They stack:
If you can narrate state line by line on paper, you are practicing the real skill. If you only “recognize the pattern,” you will miss the twisted middle questions.
| Theme that shows up | What to drill next |
|---|---|
| Reverse / palindrome / Armstrong | String + math edge cases (leading zeros, empty) |
| Array rotate / remove duplicates | In-place vs extra space trade-offs |
| Two sum / second largest | Hashing vs two-pointer under 20 minutes |
| Fibonacci / prime | Complexity talk for the tech interview |
Capgemini runs campus drives and Exceller off-campus hiring (often via Superset or the careers portal). Technical bar is the same idea either way: Pseudocode + games decide who codes; coding decides which CTC tier you land.
Campus recruitment
Placement cell lists → PPT → batch OA on CoCubes/Superset/SAB → Coding Benchmark → tech + HR on campus or virtual. Season-aligned with college calendars.
Exceller / off-campus
Register on Capgemini Exceller (Superset) or careers. Assessment link after resume screen → same Pseudocode / Coding Benchmark ladder → interviews.
Events & referrals
Hiring events and employee referrals still expect the same OA filters. Do not assume a referral skips Pseudocode.
Online Assessment - Stage 1 (often Pseudocode + Quant + Game-Based + English/tech)
Platforms students name: CoCubes, Superset, Capgemini SAB; webcam proctored. No negative marking in most reports. Older campus packs sometimes describe Pseudocode as ~15 MCQs in 25 minutes; 2026 invites more often describe a multi-section Stage 1 plus a separate Coding Benchmark day. Trust the mailer for section order and clocks.
| Section | What it feels like | Focus |
|---|---|---|
| Pseudocode | Language-agnostic tracing; older packs ~15 Q / 25 min | Loops, conditionals, arrays, nested logic |
| Quantitative | Percentages, P&L, time & work, ratios, DI | Speed + accuracy |
| Game-Based Aptitude | Interactive mini-games (2026: often 4 games / ~20-30 min) | Attention, memory, patterns, deduction |
| English / Tech MCQs | Grammar, RC, short writing; programming + cloud + DBMS/OS/networks | Do not leave blank |
Candidate-reported clear rate from Stage 1 toward Coding Benchmark / interviews sits around ~25% on hub aggregates (year pages sometimes cite ~35% clearing Pseudocode alone). Treat both as “steep first filter,” not gospel.
Time boxing that works for many students: Pseudocode first if it is weighted (~1.5 min/question on older 15/25 packs); skip a stuck tracing item after ~90-120 seconds; do not dump 40 minutes into one quant DI set; leave buffer for English/tech MCQs that look “easy” but still have sectional cutoffs.
Why Capgemini likes Pseudocode + games: it removes IDE autocomplete and pure formula grinding. Candidates who only ever typed inside VS Code with autocomplete feel Pseudocode hardest. Treat notebook tracing as non-negotiable for two weeks before any drive. Game-based modules punish panic - practice staying still and reading instructions once.
Coding Benchmark (2 problems / 45 minutes)
Languages: C, C++, Java on many 2026 invites; Python reported prohibited on several Coding Benchmark drives - confirm the mailer. Older 2024-2025 pages still list Python as allowed. Interviews generally allow any language you can defend.
| Solves | Exceller tier (candidate-reported) | Approx CTC |
|---|---|---|
| 0 (Stage 1 cleared) | Analyst (A4) | ~₹4.25 LPA |
| 1 | Analyst Star (A4-P) | ~₹5.75 LPA |
| 2 | Senior Analyst (A5) | ~₹7.5 LPA |
Practical target: lock one fully passing solution (~20 min), then invest in the second. Two half-broken codes often underperform one clean AC + a partial - especially when partial marking is present (2025 notes) but full ACs still decide Star/Senior chatter.
Build order under the clock: (1) skim both prompts, (2) pick the “sure” problem first, (3) write brute force that passes samples, (4) harden edge cases, (5) only then open the harder problem. Name variables clearly; tech interviews may reopen this code.
Technical Interview (~45 min, virtual or onsite)
OOPs, DBMS/SQL, OS, networking, cloud basics (IaaS/PaaS/SaaS), live coding (prime, reverse, stack vs queue), and project deep-dive. Roughly ~60% of OA survivors clear tech in student-reported funnels. Fundamentals beat fancy system design for fresher Analyst tracks.
Expect “difference between C and Java?”, “what is normalization?”, “write a JOIN for…”, and “walk me through your project architecture.” If you cannot explain your own resume bullet, that is a red flag. Bring the same calm tracing habit from Pseudocode into spoken form.
HR Interview (~30 min)
Why Capgemini?, relocation, strengths/weaknesses, 5-year plan, training/bond questions. Around ~80% of tech-clear candidates get offers when communication and location answers are clean.
Prepare a specific Why Capgemini (global clients, cloud/digital work, learning via Capgemini University - pick what is true for you). Vague “I like coding” answers underperform. If you need time before relocating, say so clearly rather than bluffing.
Communication round note: some campus/Exceller paths insert listen-and-repeat / 45-second paragraph style screens (Aspiring Minds appears in write-ups). That round can eliminate candidates across package bands - including people who never saw coding. Budget speaking practice the same week you practice Pseudocode.
| Phase | Duration | What happens |
|---|---|---|
| Stage 1 OA | 1 day | Pseudocode + games + aptitude |
| Coding Benchmark | 1 day (sometimes same window) | Tier-defining coding |
| Technical | 1-2 weeks | Fundamentals + projects |
| HR | 2-3 days | Fit / location / joining |
| Result | 2-3 days | Offer + background checks |
Total: usually 2-3 weeks end to end once assessments start. Exceller off-campus can stretch on resume-screen wait.
| Gate | Typical student-reported bar |
|---|---|
| Sectional | ~50-60% each |
| Overall Stage 1 | ~60-65% |
| Coding for clearance | 0 OK for Analyst; 1/2 for Star/Senior |
| Mock target | Aim 65-70% overall before the real drive |
Older-style cutoff tables students still share (useful as mock targets even when section names shift):
| Section | Min | Safe | Excellent |
|---|---|---|---|
| Quantitative | 50-55% | 60-65% | 70%+ |
| Logical / Game-Based | 50-55% | 60-65% | 70%+ |
| Verbal | 45-50% | 55-60% | 65%+ |
| Technical MCQs | 40-50% | 60% | 70%+ |
| Coding | 0-1 depending on tier goal | 1 fully | 2 problems |
If you only remember three numbers: 4 stages, Exceller bands ₹4.25 / ₹5.75 / ₹7.5 LPA by coding solves, Pseudocode + games before anyone cares about your CGPA story.
What to practise in each section:
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Capgemini invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Capgemini sits around ₹4.25-7.5 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Capgemini eligibility for freshers 2026 is candidate-reported: typically 60% or 6.0+ CGPA across 10th, 12th, and graduation; B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT and related); final-year students and recent graduates within about 2 years; no active backlogs at selection; max ~2 years education gap; full-time degrees; Indian citizens for India roles. Always verify your drive notice. Criteria are unchanged in substa.
What you are training for: Capgemini fresher loops commonly run four stages: Online Assessment (Pseudocode, Quantitative, Game-Based Aptitude, English/tech MCQs on CoCubes/Superset/SAB) → Coding Benchmark (2 problems / 45 min) → Technical Interview (~45 min) → HR (~30 min). Campus and Exceller off-campus paths usually finish in about 2-3 weeks from assessment to offer.
Short version of the prep split: Split time roughly: 40% aptitude + game-based, 30% Coding Benchmark in C/C++/Java, 20% CS fundamentals (OOPs, DBMS, OS, networks, cloud basics), 10% tech + HR. Practice 10-15 previous papers and 5-10 timed mocks. One clean full coding solve beats two half solutions for tiering.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Capgemini previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Capgemini drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Capgemini usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Capgemini?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Capgemini-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Capgemini story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Capgemini papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Capgemini papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Capgemini-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Capgemini paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Capgemini. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Capgemini, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Capgemini mistakes, you are collecting content, not preparing.
Sit one more mixed Capgemini set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Figures below are candidate-reported as of August 2026. Treat them as ranges - offer letters win.
| Tier | Code | Coding Benchmark | Total package (approx.) |
|---|---|---|---|
| Analyst | A4 | Stage 1 clear, 0 solves | ~₹4.25 LPA |
| Analyst Star | A4-P | 1 of 2 solves | ~₹5.75 LPA |
| Senior Analyst | A5 | Both solves | ~₹7.5 LPA |
| Role | Notes | Band |
|---|---|---|
| Associate Consultant (entry card) | Overlaps Analyst chatter | ~₹4-4.5 LPA |
| Broader Analyst write-ups | Certs / older guides | ~₹3.5-5.5 LPA |
| Consultant | ~2-3 years | ~₹8-10 LPA |
| Senior Consultant | ~3-5 years | ~₹12-15 LPA (wider bands in some guides) |
| QA | ISTQB sometimes preferred | ~₹3.5-4.5 LPA |
| Business Analyst | Entry | ~₹5-8 LPA |
Candidate stories: campus Analyst 2025 ₹4.25 LPA (Mumbai then project-based); off-campus ECE 2024 ₹4 LPA.
How to read the Exceller map: ₹4.25 / ₹5.75 / ₹7.5 is the fresher technical offer ladder students most often cite for A4 / A4-P / A5. Exact CTC splits (base vs bonus vs benefits) vary by offer letter and year - use the band for expectation-setting, not negotiation theater before you have an offer. Certifications pages sometimes quote a wider Analyst band (~₹3.5-5.5 LPA); treat that as older/broader chatter, not a second Exceller ladder.
Peer context students ask about: TCS fresher bands often cited around ₹3.5-4 LPA; Infosys SE often around ₹3.6-4.5 LPA depending on the source year; Capgemini’s Star/Senior Analyst bump is the coding-driven differentiator vs a single flat services CTC.
Health insurance (employee + family), PF (~12% employer in many India offers), gratuity, ~20-25 days annual leave plus sick/casual, Capgemini University L&D, and flexible/hybrid norms that vary by project. Bond or notice questions show up in HR - answer factually.
Growth students ask about: Analyst → Consultant → Senior Consultant is the common services ladder people describe. Internal mobility and cloud/SAP upskilling are real talking points after joining - if you care about not being stuck on one module forever, say that in your own words without overselling.
Know the Exceller 4.25 / 5.75 / 7.5 map, ask how fixed vs variable splits, and clarify joining vs finals. One calm clarifying question beats aggressive negotiation with no market anchor. Do not negotiate from vibes before you have a letter.
Game-based OA
Interactive aptitude mini-games replace older MCQ logical banks on many 2026 drives. Calm execution matters as much as quant formulas.
Exceller tiering
Coding Benchmark solves still map to Analyst / Star / Senior Analyst bands. One clean AC is the practical Star target.
Language rules
C/C++/Java stay safe. Several 2026 Coding Benchmark invites reported Python blocked - read the mailer.
Company context
Cloud, AI, cybersecurity, and digital transformation vocabulary shows up in tech MCQs and interviews more than in older pure-aptitude years.
Net for 2026: do not wait for a rumor that Pseudocode is “gone.” Double down on tracing, game-based comfort, and Coding Benchmark triage. Virtual interviews remain common; process length is still roughly 2-3 weeks once you are inside.
Typical fresher path: Online Assessment (Pseudocode, Quant, Game-Based, English/tech) → Coding Benchmark (2 / 45 min) → Technical (~45 min) → HR (~30 min). Campus and Exceller off-campus usually land in about 2-3 weeks. Confirm round names on your invite.
Most software fresher loops report four stages. Some drives add a communication screen or fold coding into the assessment day. Count the mailer, not a random blog.
Yes. Free Capgemini placement papers PDF and 2024-2026 style practice are on this site - pattern trainers with solutions, not leaked live papers. No registration for main downloads. Start with the 2026 PDF or the archive.
Pseudocode is language-agnostic logic tracing without an IDE. Game-Based Aptitude uses interactive mini-games (attention, memory, patterns). In many 2026 drives, games replace older MCQ logical-reasoning sections. Both are major Stage 1 filters.
A hands-on coding stage after Stage 1: typically 2 problems in 45 minutes. Solves map to Exceller salary tiers. Aim for one fully passing solution before polishing the second.
Candidate-reported: 60% / 6.0 CGPA across 10th, 12th, graduation; B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT and related); final year or recent grads within ~2 years; no active backlogs; max ~2 years gap; full-time; Indian citizens for India roles. Same substance as 2025 - verify your drive notice.
Exceller bands students cite (August 2026): Analyst ~₹4.25 LPA, Analyst Star ~₹5.75 LPA, Senior Analyst ~₹7.5 LPA, tied to Coding Benchmark solves. Associate Consultant chatter often sits near ₹4-4.5 LPA. Offer letter wins.
After clearing Stage 1: 0 coding solves → Analyst (A4); 1 → Analyst Star (A4-P); 2 → Senior Analyst (A5). Tier is coding-driven once aptitude/Pseudocode is cleared.
Split ~40% aptitude/games, 30% Coding Benchmark (C/C++/Java), 20% CS fundamentals, 10% interview/communication. Practice 10-15 papers and 5-10 mocks. Details: preparation guide.
Pseudocode is language-agnostic. Coding Benchmark: C, C++, Java are the safe set; Python was restricted on several 2026 drives. Interviews usually allow any language you can defend. Confirm the invite.
Sometimes yes - listen-and-speak / short paragraph screens appear in campus and Exceller write-ups and can eliminate candidates even when coding never happened. Practice speaking under a timer.
Roughly 50-60% sectional and 60-65% overall on Stage 1, with Pseudocode + games as hard filters. Not official Capgemini numbers - use them as mock targets (~65-70% overall).
All three are large services paths. Capgemini leans Pseudocode + game-based + Exceller coding tiers. TCS is NQT-style aptitude + coding. Infosys is IRT sectional cutoffs + coding (≥1). Prep shared aptitude, then specialize for Capgemini’s Pseudocode and games.
Prioritize Pseudocode tracing and one rock-solid Coding Benchmark AC. Capgemini rejects MCQ grinders who freeze on games or leave two partial codes. Rehearse Why Capgemini and relocation in plain words.
Start with Capgemini interview experience on this site, then cross-check recent community write-ups. Patterns shift by year - use them as maps, not scripts.
Prefer zero active backlogs at selection. Many drives let you sit the assessment only if the notice allows, but final selection usually requires cleared backlogs before joining. Do not treat backlog leniency as a free pass past Pseudocode.
No. Mechanical, Civil, ECE, and other branches clear Capgemini when Pseudocode and Coding Benchmark are real. Branch does not replace coding ability; it also does not auto-reject you if coding is strong - see the ECE switcher story below.
Usually 2-3 weeks once assessments start: Stage 1 and Coding Benchmark in about a day each, technical within 1-2 weeks, HR in a few days, results shortly after. Exceller resume-screen waits can stretch the front of the funnel.
Often yes - HR commonly asks about relocation and project-based location changes (Mumbai and other hubs appear in stories). Answer honestly; location bluffing is a common late-stage drop.
Profile: B.Tech CS, 7.5 CGPA. Round 1 on Capgemini Assessment Portal: 15 Pseudocode MCQs, about 12/15, cleared. Coding: reverse array (about 10 minutes, all cases) and Armstrong (about 15 minutes, all cases). Tech (35 min): C vs Java, OOPs, stack vs queue, prime code, normalization, SQL JOIN, project deep-dive. HR (~25 min): Why Capgemini, relocation, strengths/weaknesses, training questions. Selected: ₹4.25 LPA, Mumbai initially then project-based. Full write-up style notes: interview experience.
What helped: finishing Pseudocode calmly instead of chasing every quant mark; treating Armstrong as a full-AC problem rather than a partial; having a 60-second project story ready.
Profile: B.Tech ECE, 7.0 CGPA. Careers portal → assessment link in ~2 weeks; all rounds within about a month. Coding: 1 complete + partial second; cleared with mid coding + strong game-based. HR asked why switching from ECE to IT. Selected: ₹4 LPA. Takeaway: Capgemini welcomes career switchers when Pseudocode and communication hold.
What helped: owning the career-switch story early; not apologizing for ECE; showing game-based composure when coding was only mid.
A 2024-25 on-campus path (GeeksforGeeks, write-up updated Oct 2024) described aptitude + essay → PrepInsta-style game round → peers split toward coding for higher packages vs straight to communication for base package. Communication included listen-and-repeat, listen-and-answer, fill-in-blanks, and a 45-second paragraph. Final interview ~15 min, project-heavy.
An Exceller track (coding 16 Feb 2024 for A4(P)/A5; communication 17 Feb on Aspiring Minds; virtual Superset interview 28 Feb 2024) noted lobby waits before the interviewer joins - and that communication eliminated candidates across package bands, including some who never coded.
Common question families candidates keep listing:
What hurt other candidates in the same cycles: coding before clarifying constraints; treating communication as a formality; assuming Python on Coding Benchmark; optimising the hard problem while leaving an easy AC incomplete; freezing when asked “explain your project without buzzwords.”
What to steal from these stories: treat games and communication as real filters; bank one Coding Benchmark AC for Star targets; keep project stories short and honest; do not treat one GfG post as a fixed paper template - return to timed mocks.