Capgemini Placement Preparation: Pseudocode, Game-Based Aptitude and English Sections Explained

Capgemini tests freshers differently: pseudocode MCQs instead of written coding, and a game-based aptitude round instead of a standard paper. Here is how each section works, with a worked example of every game type.

Prashant Jain

KnowledgeGate AI educator

19 Jul 20265 min read

Capgemini fresher assessments can differ from the standard aptitude papers you may have practised. In many recent campus drives, the process has included a gamified aptitude round and pseudocode MCQs, but the exact assessment can differ by role, college and hiring cycle. Prepare only from a generic aptitude pattern and you may meet unfamiliar game formats on test day.

One ground rule first: the exact section list, question counts, timings and cutoffs vary between drives and cycles. Confirm the pattern for your drive in the instructions your college or Superset shares, or on the official Capgemini careers portal. What stays stable is the shape of the assessment; that is what this post prepares you for.

Capgemini selection process: the sections at a glance

Some recent Capgemini campus drives (including Analyst and Senior Analyst profiles run through Superset) have tested candidates along three fronts before interviews, and our Capgemini Superset preparation course organises its videos, test series and previous-year questions along the same fronts:

Section

What it tests

How to prepare

Pseudocode MCQs

Tracing language-agnostic code and predicting output

Daily paper tracing of loops, conditions, recursion

Game-based aptitude

Deductive logic, working memory, planning, numeracy through short games

Familiarity with each game family, then timed practice

English communication

Grammar, comprehension, vocabulary in context

Error-spotting drills and steady reading

A behavioural questionnaire has also featured in some drives (it needs honesty more than preparation), and technical and HR interviews follow the written stage.

Capgemini pseudocode section: tracing code without a compiler

The pseudocode section gives you short, language-agnostic snippets and asks what they print. The recurring families are loops and counters, nested conditionals, recursion, array and string manipulation, and operator behaviour (integer division, modulo, precedence). Here is the discipline, worked once:

a = 2, b = 3, sum = 0
for i = 1 to 4
    sum = sum + a
    a = a + b
print sum

Trace it with a variable table:

  1. i = 1: sum = 0 + 2 = 2, then a = 2 + 3 = 5

  2. i = 2: sum = 2 + 5 = 7, then a = 5 + 3 = 8

  3. i = 3: sum = 7 + 8 = 15, then a = 8 + 3 = 11

  4. i = 4: sum = 15 + 11 = 26, then a = 11 + 3 = 14

Output: 26. The common wrong answer comes from adding the updated value of a instead of the value it held when the line ran.

Recursion yields to the same method. Take f(n) defined as: return 1 if n is 1 or less, otherwise return n multiplied by f(n minus 2). Then f(6) = 6 × f(4) = 6 × 4 × f(2) = 6 × 4 × 2 × f(0) = 48. Write the expansion out fully, then collapse it.

Capgemini game-based aptitude: the game types, each worked through

Capgemini's aptitude round has been delivered as a set of short cognitive games in recent cycles, and the exact set can differ by drive, so treat these as the families worth knowing rather than a guaranteed lineup. The games feel strange the first time and comfortable the third time.

The switch challenge: deductive logic with operators

You see an input string of digits, an output string, and a set of "operators" that reorder positions; pick the one that produced the output. Suppose the input is 4 7 1 9 and the output is 1 9 4 7. The output's first digit, 1, sat in position 3 of the input; then 9 from position 4, 4 from position 1, 7 from position 2. The operator is (3, 4, 1, 2). Work backwards from the output one position at a time; these become mechanical.

The grid challenge: working memory under interruption

You are shown a dot on a grid to remember. The game then interrupts you with a different task, usually judging whether a pattern is symmetrical, before showing another dot; after several rounds you recall every position in order. The working method is verbal encoding: say the positions as words ("top left, centre, bottom right") instead of holding a picture. Verbal labels can be easier to rehearse across the interruption than an unlabelled picture, so test whether this method improves your own recall.

The motion challenge: planning moves in a maze

You move a ball through a small maze to a target within a limited number of moves. The failure mode is moving immediately and discovering the trap two moves later. Plan the complete path before touching anything, count the moves it needs, then execute.

The digit challenge: rebuilding equations at speed

You get an equation with blank boxes and digits to place, say two blanks plus a blank equalling 81, using 2, 7 and 9. Units digits settle it: a number ending in 2 plus 9 gives a units digit of 1, so 72 + 9 = 81. Reason from the units place first instead of brute-forcing arrangements; the clock is the real opponent.

These games reward calm familiarity far more than raw ability. The daily structure in our 30-day aptitude routine adapts directly: swap its topic drills for game-family practice in weeks two and three.

Capgemini English communication section: what it checks

The English section is conventional next to the games: reading comprehension, sentence correction and error spotting, vocabulary in context, and sentence ordering. Engineering students under-prepare it on the theory that English cannot be studied. It can: error-spotting questions repeat a small set of grammar patterns (subject-verb agreement, tenses, prepositions, articles), and twenty minutes of daily reading fixes comprehension speed faster than any trick.

How to split your Capgemini preparation

Plan on four to six weeks at roughly ten to twelve hours a week, split like this:

  • Pseudocode: about half your hours, daily. Trace snippets on paper every day; previous-year Capgemini questions show you the recurring families. Weeks one and two build the tracing habit; weeks three onward are timed sets.

  • Games: three sessions of twenty to thirty minutes a week. Familiarity, then speed. Start these in week one, not week three. If your aptitude base itself is weak, build it first with our Aptitude for Placement course and layer the game formats on top.

  • English: a steady drip. Twenty minutes of daily reading plus a grammar-pattern drill on alternate days. Low effort, compounding return.

You will miss days; everyone does. When you do, drop that day's English or games slot and protect the pseudocode block, where rustiness shows fastest. The opposite mistake is worse: spending all four weeks on pseudocode because it feels most "technical", then meeting the games cold. Run all three fronts in parallel from week one.

Your next step

If you want this preparation already assembled, the Capgemini Superset course packages topic-wise videos, test series and Capgemini previous-year questions across every section above. Sitting several service-based drives this season? The full company-wise catalogue lives on our Placement Preparation category page.

Before you lock your plan, confirm your drive's exact sections, timings and eligibility in the official announcement from Capgemini or Superset. Then give the games the respect of familiarity and the pseudocode the respect of paper tracing.

Keep learning

Discussion