Most freshers preparing for Capgemini spend three weeks on aptitude and two days on technical. Then they sit in the pseudo-code round, stare at a question about loop output, and blank out completely. The Capgemini interview process has a specific structure, and one round in particular has a higher failure rate than anything else on the day. This post breaks down every round, spends real time on the pseudo-code section with worked examples, and tells you exactly where candidates lose marks they shouldn't.
The full structure before you prep anything
Capgemini's campus hiring runs four rounds for most engineering colleges. The exact order can shift slightly depending on the drive (on-campus vs. off-campus, freshers vs. lateral), but the standard sequence looks like this:
- Online Assessment (aptitude + pseudo-code + English)
- Technical Interview
- Managerial Interview (not always present for freshers)
- HR Interview
The online assessment is the filter. Most candidates who clear it get an offer eventually. Most who don't clear it never get a second shot at that batch. That asymmetry should tell you where to put your prep hours.
The online assessment has three distinct sections
The aptitude section covers quantitative reasoning, logical reasoning, and basic data interpretation. Nothing here is unusual. Standard CAT-lite material. If you've been preparing for TCS or Infosys, this section is similar in difficulty.
The English section tests grammar, reading comprehension, and vocabulary. It's timed tightly. Candidates who read slowly lose points not because they don't know the answers but because they run out of time. Practice reading passages under 90-second limits.
The pseudo-code section is the one that matters. More on that next.
The pseudo-code round is where most freshers drop out
Capgemini uses a proprietary pseudo-code language in the assessment. It isn't Python. It isn't Java. It's a simplified notation that looks like this:
SET x TO 5
SET y TO 2
WHILE x > 0
SET x TO x - y
PRINT x
END WHILE
Your job is to trace through it and give the output. Sounds simple. In practice, candidates fail because they've only ever read real code. They're used to syntax errors catching their mistakes. Pseudo-code has no compiler. Every trace is manual.
Let's work through that example. Start: x = 5, y = 2.
- Iteration 1: x = 5 - 2 = 3. Print 3.
- Iteration 2: x = 3 - 2 = 1. Print 1.
- Iteration 3: x = 1 - 2 = -1. Condition x > 0 is false. Loop ends.
Output: 3, 1. That's it. The trap here is that some candidates print x before the subtraction. Read the order of operations inside the loop carefully every single time.
A harder pseudo-code example with a nested condition
Here's a question closer to what appears in the actual Capgemini interview process assessment:
SET a TO 10
SET b TO 3
SET result TO 0
WHILE a > 0
IF a MOD b == 0 THEN
SET result TO result + 1
END IF
SET a TO a - 1
END WHILE
PRINT result
Trace it. a goes from 10 down to 1. For each value, check if a MOD 3 equals 0.
- a = 10: 10 MOD 3 = 1. No.
- a = 9: 9 MOD 3 = 0. result = 1.
- a = 8: 8 MOD 3 = 2. No.
- a = 7: 7 MOD 3 = 1. No.
- a = 6: 6 MOD 3 = 0. result = 2.
- a = 5: 5 MOD 3 = 2. No.
- a = 4: 4 MOD 3 = 1. No.
- a = 3: 3 MOD 3 = 0. result = 3.
- a = 2: 2 MOD 3 = 2. No.
- a = 1: 1 MOD 3 = 1. No.
Output: 3.
The common mistake is stopping at a = 0 when the condition is a > 0, so candidates sometimes include a = 0 in the trace. They don't. The loop exits before that iteration runs.
How to practice pseudo-code without any special tool
Write out 10 short programs by hand. Not on a laptop. On paper. Trace them line by line with a pencil. The physical act of writing forces you to slow down and not skip steps. Most wrong answers in this section come from mental shortcuts.
Start with simple counter loops. Move to nested conditions. Then try functions with return values, which appear in harder Capgemini variants. A function in pseudo-code looks like:
FUNCTION double(n)
RETURN n * 2
END FUNCTION
SET x TO double(4)
PRINT x
Output: 8. Straightforward, but candidates confuse RETURN with PRINT and write nothing.
Do two timed pseudo-code sessions the night before your assessment. The second session always reveals which patterns you're still shaky on.
The technical interview is resume-first, not LeetCode-first
Capgemini's technical round for freshers is not a competitive coding round. The interviewer will open your resume and ask about your projects. "Explain your final year project." "What database did you use and why?" "What would you change if you built it again?"
Candidates who prepared 200 LeetCode problems and zero deep-dive answers about their own work get caught here. Know your projects well enough to explain every design decision. If you used MySQL because it was the only database you knew, say that honestly and explain what you'd choose now. Interviewers at Capgemini value clarity over polish.
Core CS fundamentals are also on the table: OOP concepts, basic SQL queries, and OS topics like process vs. thread. If you're from a non-CS branch, they'll adjust, but they'll still expect you to know what you put on your resume.
The managerial and HR rounds are not formalities
For lateral hires and some campus drives, there's a managerial round between technical and HR. This round tests whether you can communicate clearly under mild pressure. The questions sound soft ("Tell me about a time you handled a conflict in a team") but the interviewer is watching how you structure an answer, not just what you say.
Use a simple structure: situation, what you did, what happened. Keep it under two minutes. Candidates who ramble for five minutes on a single question signal that they can't prioritize information. That's a real concern in a services company where client communication is part of the job.
The HR round covers salary expectations, relocation, bond agreements, and joining timelines. Know the current Capgemini fresher CTC (it's been in the 3.5–4.5 LPA range for most engineering roles, though this varies by batch and role). Don't negotiate aggressively in the HR round for a fresher position. Do ask about the project allocation process.
The one preparation mistake that costs the most
Candidates treat the four rounds as four separate events and prep for each in isolation. They're not separate. The technical interviewer will ask about something you wrote in your online assessment profile. The HR round will reference what you said in the technical round.
Treat the whole day as one continuous conversation. Keep your answers consistent. If you said your strongest language is Java in the technical round, don't tell HR you're "more of a Python person." Inconsistencies get flagged.
Run at least one full mock day before the actual drive. Start with a timed aptitude set, move to a pseudo-code trace session, then do a voice-based mock technical interview. The third activity in that sequence always exposes gaps the first two didn't. That's the point.
PrepFinity's AI mock interviewer runs technical rounds that follow the exact question patterns service companies like Capgemini use. You can do a full mock session in under 45 minutes, get specific feedback on your answers, and identify the two or three topics you need to review before the real thing. The candidates who show up prepared for the pseudo-code round specifically are the ones who clear the filter. Everything else is easier once you're past it.
Ready to practice the exact rounds that Capgemini tests? Start with 3 free interviews — no credit card needed.