All companies
Capgemini logo
IT Services
Analyst & Software Engineer (Exceller-style hiring)
Online assessment (Technical MCQ + Pseudocode, English, Game-based cognitive, PowerSkills, Coding) + Interviews

Capgemini Interview Questions & Placement Prep (2026)

Capgemini's fresher hiring for Analyst and Software Engineer runs through a shared online assessment — technical MCQs and pseudocode, an English communication test, game-based cognitive ability, a PowerSkills behavioural section and two coding problems — followed by a technical interview and an HR interview. Role and package depend on your performance across every stage, not just clearing the cutoff. This guide covers every section, the syllabus, representative questions, ready code, SQL/OOP/OS revision and a week-by-week plan.

~40 MCQs/pseudocode (40–50 min) + ~30 English (30 min) + 4 cognitive games (20–30 min) + PowerSkills (20–25 min) + 2 coding problems (45–90 min) + technical (20–35 min) + HR (10–20 min)

Last updated:

Exam Pattern

~40 MCQs/pseudocode (40–50 min) + ~30 English (30 min) + 4 cognitive games (20–30 min) + PowerSkills (20–25 min) + 2 coding problems (45–90 min) + technical (20–35 min) + HR (10–20 min)

SectionQuestionsTimeTypeDifficulty
Round 1 — Technical MCQs & Pseudocode~4040–50 minMCQElimination
Round 2 — English Communication~3030 minMCQ / ListeningElimination
Round 3 — Game-based Cognitive Ability4 games20–30 minCognitive gamesElimination
Round 4 — Behavioural / PowerSkillsSituational statements20–25 minSituational judgementNon-elimination (scored)
Round 5 — Coding AssessmentUsually 2 problems45–90 minCodingElimination
Round 6 — Technical InterviewVaries20–35 minInterviewElimination
Round 7 — HR InterviewVaries10–20 minInterviewElimination

Section-Wise Syllabus

Everything that appears in the assessment, grouped by section.

1. Technical MCQs & Pseudocode

Programming fundamentals

  • • C, C++, Java or Python fundamentals
  • • Variables and data types
  • • Operators and precedence
  • • Conditions and loops
  • • Functions
  • • Arrays and strings
  • • Recursion
  • • Pointers and references
  • • OOP basics
  • • Bitwise operations

Output tracing focus

  • • Pre-increment vs post-increment
  • • Integer division and modulus
  • • Nested loops
  • • Scope of variables
  • • Array indexing
  • • Pass-by-value vs pass-by-reference
  • • Static variables
  • • Logical & bitwise operators

DSA revision

  • • Arrays, strings, linked lists
  • • Stacks, queues, hash maps
  • • Trees, BSTs, heaps, graphs
  • • Sorting and binary search
  • • Recursion & backtracking
  • • Greedy and dynamic programming
  • • BFS and DFS
  • • Time and space complexity

2. English Communication

Written / grammar

  • • Reading comprehension
  • • Sentence correction
  • • Error detection
  • • Fill in the blanks
  • • Sentence completion
  • • Para jumbles
  • • Synonyms and antonyms
  • • Articles, prepositions, tenses
  • • Subject-verb agreement
  • • Active/passive & direct/indirect speech

Listening

  • • Grammar-based audio questions
  • • Listening comprehension

3. Game-based Cognitive Ability (4 games)

What is measured

  • • Working memory
  • • Pattern recognition
  • • Deductive reasoning
  • • Planning
  • • Numerical ability
  • • Attention & response speed
  • • Risk and reward decisions

Common game types

  • • Grid memory (remember location/order of symbols)
  • • Pattern recognition (next/missing pattern)
  • • Numerical operations (reach a target)
  • • Deductive reasoning (infer a rule)
  • • Spatial rotation
  • • Working-memory sequence
  • • Planning game (fewest actions to a goal)

4. Behavioural / PowerSkills

Traits evaluated

  • • Teamwork
  • • Ownership
  • • Adaptability
  • • Integrity
  • • Customer orientation
  • • Learning attitude
  • • Communication
  • • Working under pressure
  • • Conflict handling
  • • Decision-making

Answer strategy

  • • Communicate before escalating
  • • Take responsibility
  • • Ask for clarification when needed
  • • Accept feedback gracefully
  • • Follow ethical/organisational procedure
  • • Help the team without missing deadlines

5. Coding Round

Easy topics

  • • I/O, conditions and loops
  • • Number problems
  • • Arrays and strings
  • • Frequency counting
  • • Sorting and searching
  • • Basic math
  • • Pattern printing
  • • Matrix traversal

Medium topics

  • • Two pointers
  • • Sliding window
  • • Prefix sums
  • • Hashing
  • • Binary search
  • • Linked lists, stacks, queues
  • • Recursion & backtracking
  • • Trees, BFS/DFS
  • • Greedy & basic DP
  • • Intervals
  • • Heap / priority queue

6. Technical Interview Areas

OOP

  • • Class vs object
  • • Encapsulation, abstraction
  • • Inheritance, polymorphism
  • • Constructor/destructor
  • • Overloading vs overriding
  • • Virtual functions, abstract classes, interfaces
  • • Access modifiers, static members

DBMS & SQL

  • • Keys: primary, foreign, candidate, composite
  • • Functional dependency
  • • 1NF, 2NF, 3NF, BCNF
  • • Joins, GROUP BY/HAVING
  • • Subqueries, indexes, transactions
  • • ACID properties, deadlocks, views

Operating systems

  • • Process vs thread, context switching
  • • CPU scheduling
  • • Synchronisation, mutex/semaphore
  • • Deadlock
  • • Paging, segmentation, virtual memory
  • • Page replacement
  • • User mode vs kernel mode

Computer networks

  • • OSI layers, TCP/IP model
  • • TCP vs UDP
  • • DNS, HTTP/HTTPS
  • • IP address, MAC address, DHCP, ARP
  • • Routing, three-way handshake
  • • Congestion control

7. Role Interpretation & Documentation

Analyst vs Software Engineer

  • • Analyst: strong aptitude, English, pseudocode and basic coding
  • • Software Engineer: strong technical MCQs, coding, DSA and CS fundamentals
  • • Higher package: usually stronger coding, technical interview and role-specific shortlisting
  • • Clearing the online assessment does not guarantee the higher package — coding score, interview, degree, skills and business needs all factor in

Most Asked Topics

Highest-frequency areas across recent test papers.

Pseudocode output tracing

Pre/post increment, integer division vs modulus, nested loops, scope and pass-by-value vs reference dominate the technical MCQ half.

Game-based cognitive tests

Grid memory, pattern recognition, deductive reasoning and planning games — accuracy over speed, avoid guessing hidden scoring rules.

PowerSkills situational judgement

Consistent answers favouring communication, ownership and following process over escalation or shortcuts.

Array & string coding

Second-largest distinct element, first non-repeating character, Kadane's max subarray, balanced brackets, subarray sum K.

SQL second-highest salary

Classic subquery pattern asked repeatedly in both the coding round and technical interview.

OOP fundamentals

Four pillars, overloading vs overriding, abstraction vs encapsulation, virtual functions.

Networking basics

OSI layers, TCP vs UDP, three-way handshake, what happens after entering a URL in a browser.

Project deep dive

Every technical interview opens with your final-year project, your individual contribution and the tech stack.

Free Resources

Curated practice links per section.

50+ DSA Practice Problems

Solve in order — arrays and strings first, then sorting and recursion.

Easy (10)

  1. Prime number check
  2. Armstrong number in a range
  3. Palindrome number and string
  4. Factorial using recursion
  5. Fibonacci series up to n terms
  6. Sum of digits of a number
  7. GCD and LCM of two numbers
  8. Reverse a number
  9. Second-largest distinct element
  10. Character frequency counting

Easy–Medium (8)

  1. Remove duplicate characters from a string
  2. Array rotation by k
  3. Matrix transpose
  4. Pattern printing — pyramid, diamond
  5. First non-repeating character
  6. Maximum subarray sum (Kadane's algorithm)
  7. Balanced brackets using a stack
  8. Merge two sorted arrays

Medium (10)

  1. Count subarrays with sum K (prefix sum + hashing)
  2. Number of islands (BFS/DFS)
  3. Merge overlapping intervals
  4. Two pointers — pair with target sum
  5. Sliding window — longest substring without repeats
  6. Binary search and its variants
  7. Linked list reversal and cycle detection
  8. Tree traversals (inorder, preorder, postorder)
  9. Coin change — minimum coins
  10. Priority queue / heap based top-k problems

Fundamentals to code from memory (6)

  1. Bubble, selection and insertion sort
  2. Linear and binary search
  3. Recursion base cases and stack depth
  4. Backtracking template (subsets, permutations)
  5. Greedy algorithm structure
  6. Basic dynamic programming (1D and 2D tables)

Previous Year Questions & Patterns

Repeat coding questions with the expected approach.

Pseudocode & output tracing PYQs

  • int a = 5, b = 2; cout << a / b << " " << a % b; — Output: 2 1
  • for (int i = 1; i <= n; i *= 2) cout << i; — Complexity: O(log n)
  • int x = 3; for (int i = 1; i <= 3; i++) x *= i; cout << x; — Output: 18
  • Nested loop complexity: for i in range(n): for j in range(i, n): ... — O(n^2)
  • Trace pre-increment vs post-increment inside an array index expression

Technical MCQs

  • Which data structure follows LIFO? → Stack
  • Which traversal of a BST gives sorted order? → Inorder traversal
  • Which normal form removes partial dependency? → Second Normal Form
  • Which protocol is connection-oriented? → TCP
  • Average lookup complexity of a hash table? → O(1)
  • Which algorithm finds shortest paths in an unweighted graph? → BFS

Quant worked examples

  • A train 180 m long crosses a pole in 9 seconds → speed = 180/9 = 20 m/s = 72 km/h
  • Marked 25% above cost, sold at 10% discount → profit % = 1.25×0.9 − 1 = 12.5%
  • A finishes in 12 days, B in 18 days → together 1/12 + 1/18 = 5/36 → 7.2 days
  • Series 2, 6, 12, 20, 30, ? → differences 4,6,8,10,12 → next = 42
  • CAP coded as DBQ (shift +1) → CODE coded as → DPEF

Game-based cognitive ability strategy

  • Read every game's instructions fully before starting — the scoring rule is stated, not hidden
  • For grid memory, group items into visual patterns instead of memorising each cell
  • For deductive reasoning, test the simplest rule first (colour, shape, count) before combinations
  • Accuracy beats speed; do not rush through numerical target games
  • One mistake does not fail the whole game — keep a steady pace till the end

HR / behavioural questions

  • Tell me about yourself
  • Why Capgemini?
  • Describe a time you disagreed with a teammate — how did you resolve it?
  • Are you willing to relocate and work in shifts?
  • Describe a time you learned a new technology quickly
  • Where do you see yourself in five years?

20+ SQL Query Bank

Write these out by hand — joins and subqueries are asked in both the test and the interview.

Basics & aggregation

Filter and sort

SELECT name, department
FROM employees
WHERE salary > 50000
ORDER BY salary DESC;

Aggregates

SELECT COUNT(*) AS total,
       AVG(salary) AS avg_salary,
       MAX(salary) AS max_salary
FROM employees;

GROUP BY with HAVING

SELECT department, AVG(salary) AS avg_salary
FROM employees
GROUP BY department
HAVING AVG(salary) > 60000;

Joins

INNER JOIN

SELECT e.name, d.department_name
FROM employees e
INNER JOIN departments d
  ON e.dept_id = d.dept_id;

LEFT JOIN

SELECT e.name, d.department_name
FROM employees e
LEFT JOIN departments d
  ON e.dept_id = d.dept_id;

SELF JOIN — employee and manager

SELECT e1.name AS employee, e2.name AS manager
FROM employees e1
JOIN employees e2
  ON e1.manager_id = e2.emp_id;

Subqueries

Second-highest salary

SELECT MAX(salary) AS second_highest
FROM employees
WHERE salary < (SELECT MAX(salary) FROM employees);

Employees above the overall average

SELECT name, salary
FROM employees
WHERE salary > (SELECT AVG(salary) FROM employees);

DBMS & Core Interview Q&A

Short answers you should be able to say out loud.

WHERE vs HAVING?

WHERE filters rows before grouping; HAVING filters groups after GROUP BY and may use aggregates.

INNER JOIN vs LEFT JOIN?

INNER keeps only matching rows; LEFT keeps all left-table rows with NULLs where there is no match.

What is normalisation?

Structuring tables through 1NF, 2NF, 3NF and BCNF to remove redundancy and update anomalies.

Primary key vs unique key?

Primary key: one per table, never NULL. Unique key: several allowed and may hold one NULL.

What are ACID properties?

Atomicity, Consistency, Isolation and Durability — the guarantees of a reliable transaction.

What is a functional dependency?

An attribute (or set) that uniquely determines another attribute's value in a relation — the basis for normal forms.

What is a deadlock?

A cycle of processes each waiting on a resource held by another; prevented via ordering, timeouts or detection algorithms.

Process vs thread?

A process has its own memory space; threads share the memory of their parent process.

OOPs Concepts + 10 Code Snippets

Theory plus the exact snippets asked in the technical round.

Encapsulation

Keep fields private and expose controlled accessors — e.g. a Bank class with a private balance and deposit()/getBalance().

Abstraction

Show only what matters and hide implementation behind interfaces or abstract classes.

Inheritance

Derive Child from Parent to reuse behaviour and extend it with new methods.

Polymorphism

Compile-time overloading versus runtime overriding (virtual functions in C++, method overriding in Python/Java).

Overloading vs overriding

Overloading: same name, different parameters, resolved at compile time. Overriding: subclass redefines a parent method, resolved at runtime.

Constructor & destructor

Constructor initialises an object; destructor releases resources when it goes out of scope.

Virtual functions

Enable runtime dispatch in C++; mark overrides with the override keyword.

Abstract class vs interface

Abstract class can have partial implementation; interface (in most languages) declares only method signatures.

1. Second-largest distinct element (C++)

cpp

int secondLargest(vector<int>& a) {
    long first = LONG_MIN, second = LONG_MIN;
    for (int x : a) {
        if (x > first) { second = first; first = x; }
        else if (x > second && x != first) second = x;
    }
    return second == LONG_MIN ? -1 : second;
}

2. First non-repeating character (C++)

cpp

char firstNonRepeating(string s) {
    int freq[256] = {0};
    for (char c : s) freq[(unsigned char)c]++;
    for (char c : s) if (freq[(unsigned char)c] == 1) return c;
    return '\0';
}

3. Maximum subarray sum — Kadane's algorithm (C++)

cpp

long long maxSubArraySum(vector<int>& a) {
    long long current = a[0], best = a[0];
    for (size_t i = 1; i < a.size(); i++) {
        current = max((long long)a[i], current + a[i]);
        best = max(best, current);
    }
    return best;
}

4. Balanced brackets (C++)

cpp

bool isBalanced(string s) {
    stack<char> st;
    unordered_map<char, char> match = {{')','('}, {'}','{'}, {']','['}};
    for (char c : s) {
        if (c == '(' || c == '{' || c == '[') st.push(c);
        else if (match.count(c)) {
            if (st.empty() || st.top() != match[c]) return false;
            st.pop();
        }
    }
    return st.empty();
}

5. Count subarrays with sum K (C++)

cpp

long long countSubarraysWithSumK(vector<int>& a, long long k) {
    unordered_map<long long, int> freq;
    freq[0] = 1;
    long long sum = 0, answer = 0;
    for (int x : a) {
        sum += x;
        answer += freq[sum - k];
        freq[sum]++;
    }
    return answer;
}

6. Number of islands — BFS (C++)

cpp

int numIslands(vector<vector<char>>& grid) {
    int rows = grid.size(), cols = grid[0].size(), count = 0;
    vector<vector<bool>> visited(rows, vector<bool>(cols, false));
    int dx[] = {0,0,1,-1}, dy[] = {1,-1,0,0};
    for (int i = 0; i < rows; i++) {
        for (int j = 0; j < cols; j++) {
            if (grid[i][j] == '1' && !visited[i][j]) {
                count++;
                queue<pair<int,int>> q;
                q.push({i, j});
                visited[i][j] = true;
                while (!q.empty()) {
                    auto [r, c] = q.front(); q.pop();
                    for (int d = 0; d < 4; d++) {
                        int nr = r + dx[d], nc = c + dy[d];
                        if (nr >= 0 && nr < rows && nc >= 0 && nc < cols &&
                            grid[nr][nc] == '1' && !visited[nr][nc]) {
                            visited[nr][nc] = true;
                            q.push({nr, nc});
                        }
                    }
                }
            }
        }
    }
    return count;
}

7. Merge overlapping intervals (C++)

cpp

vector<vector<int>> mergeIntervals(vector<vector<int>>& intervals) {
    sort(intervals.begin(), intervals.end());
    vector<vector<int>> result;
    for (auto& iv : intervals) {
        if (!result.empty() && iv[0] <= result.back()[1]) {
            result.back()[1] = max(result.back()[1], iv[1]);
        } else {
            result.push_back(iv);
        }
    }
    return result;
}

8. Prime, GCD and Armstrong (C++)

cpp

bool isPrime(int n) {
    if (n < 2) return false;
    for (int i = 2; i * i <= n; i++) if (n % i == 0) return false;
    return true;
}

int gcd(int a, int b) {
    while (b) { int t = b; b = a % b; a = t; }
    return a;
}

bool isArmstrong(int n) {
    int original = n, sum = 0;
    while (n > 0) { int d = n % 10; sum += d * d * d; n /= 10; }
    return sum == original;
}

9. Bank account — encapsulation (Python)

cpp

class Bank:
    def __init__(self):
        self.__balance = 0        # private

    def deposit(self, amount):
        self.__balance += amount

    def get_balance(self):
        return self.__balance

class Animal:
    def sound(self):
        print('Some sound')

class Dog(Animal):
    def sound(self):
        print('Bark')

10. Sorting fundamentals (Python)

cpp

def bubble_sort(arr):
    n = len(arr)
    for i in range(n):
        for j in range(0, n - i - 1):
            if arr[j] > arr[j + 1]:
                arr[j], arr[j + 1] = arr[j + 1], arr[j]
    return arr

def insertion_sort(arr):
    for i in range(1, len(arr)):
        key, j = arr[i], i - 1
        while j >= 0 and arr[j] > key:
            arr[j + 1] = arr[j]
            j -= 1
        arr[j + 1] = key
    return arr

Operating System Basics

Scheduling, deadlock and memory management essentials.

Operating Systems

  • • Process versus thread and the cost of context switching.
  • • CPU scheduling: FCFS, SJF, Round Robin, Priority.
  • • Synchronisation with mutex versus semaphore; race conditions.
  • • Deadlock and its four necessary conditions.
  • • Paging, segmentation, virtual memory and page replacement.

Computer Networks

  • • OSI layers: Physical, Data Link, Network, Transport, Session, Presentation, Application.
  • • TCP (connection-oriented, reliable) versus UDP (connectionless, fast).
  • • DNS resolution flow, DHCP and ARP.
  • • Three-way handshake and congestion control.
  • • What happens after entering a URL in a browser — a favourite interview question.

DBMS Essentials

  • • Primary, foreign, candidate and composite keys.
  • • Normal forms: 1NF, 2NF, 3NF, BCNF and the anomalies each removes.
  • • Joins, GROUP BY/HAVING and subqueries.
  • • ACID properties and transaction isolation.
  • • Indexes speed reads but slow writes; use selectively.

Role-wise expectations

  • • Analyst track: strong aptitude, English communication, pseudocode tracing and easy coding.
  • • Software Engineer track: strong technical MCQs, medium coding, DSA and CS fundamentals.
  • • Both are assessed on the same test; role and package depend on overall performance, not just a pass/fail cutoff.
  • • Coding-round performance, technical interview, academic profile and business requirement all influence final role allocation.

4-Week Preparation Roadmap

From zero to test-ready in 28 days.

Week 1

Aptitude & English Foundation

  • 40 quantitative questions
  • 30 verbal/grammar questions
  • Revise one formula sheet section
  • 15 minutes of reading-aloud practice

Goal: Finish percentages, profit & loss, SI/CI, time & work, speed–time–distance and core grammar rules.

Week 2

Pseudocode & Technical MCQs

  • 20+ output-prediction questions
  • Revise OOP pillars
  • Revise OS and networking basics
  • 10 DBMS/SQL theory questions

Goal: Trace any loop, recursion or pointer question in under a minute.

Week 3

Game-based Cognitive Ability + PowerSkills

  • 2 timed memory/pattern games
  • 1 numerical-target game
  • 10 situational judgement scenarios
  • Review one PowerSkills trait per day

Goal: Comfortable with all four game types and consistent, process-driven behavioural answers.

Week 4–5

Coding — Easy to Medium

  • 5 easy array/string/math problems
  • 2 medium problems (two pointers, sliding window, hashing)
  • 1 SQL query practice set
  • Revise one DSA topic (stacks, trees, graphs)

Goal: 50+ easy problems and 25+ medium problems solved from memory, including Kadane's, subarray-sum-K and number of islands.

Week 6

Mock Tests + Interview Prep

  • One full timed mock (technical + English + games + coding)
  • Record and review HR answers
  • One peer mock technical interview
  • Revise project story and OOP/DBMS/OS answers

Goal: Two full assessment simulations completed and a crisp, rehearsed project explanation.

Exam Day Strategy

Score targets and time allocation.

Section targets

  • Technical MCQs & Pseudocode (~40 Qs): 40–50 min — trace on paper, bank easy MCQs first.
  • English Communication (~30 Qs): 30 min — read questions once, avoid overanalysing grammar edge cases.
  • Game-based Cognitive (4 games): 20–30 min — read instructions fully, prioritise accuracy over speed.
  • PowerSkills (situational): 20–25 min — pick the option that shows communication and ownership.
  • Coding (2 problems): 45–90 min — attempt the easier problem first, test edge cases before submitting.
  • Buffer: Keep 5 minutes to review flagged questions across sections.

Coding time split (50 min)

  • Read both problems — ~5 min
  • Solve the easier problem first — ~30–35 min
  • Second problem — ~30–40 min
  • Edge cases and re-runs (empty input, duplicates, negatives) — ~10 min
  • Solving both fully raises your chance of the Software Engineer mapping

Interview Process

What follows the online test.

Technical Interview

  • • Explain your final-year project: your role, architecture and tech stack.
  • • OOP: explain the four pillars with examples; overloading vs overriding.
  • • DBMS: normalisation, keys, and a query for the second-highest salary.
  • • OS: process vs thread, deadlock, CPU scheduling.
  • • Networks: OSI layers, TCP vs UDP, three-way handshake, what happens after a URL is entered.
  • • Simple whiteboard coding: reverse a linked list, first non-repeating character, binary search.

HR Interview

  • • Tell me about yourself; why Capgemini?
  • • Which programming language do you prefer and why?
  • • Describe a time you disagreed with a teammate and how you resolved it.
  • • Describe a time you learned a new technology quickly.
  • • Are you willing to relocate and comfortable with shifts?
  • • Where do you see yourself in five years?

Mock Test Plan

Four simulations to run before the real test.

Mock 1 — Technical MCQ & Pseudocode Sprint

  • • 40 questions in 45 minutes
  • • Log every output-tracing mistake and revisit the rule

Mock 2 — English Communication

  • • 30 questions in 30 minutes covering grammar, RC and listening
  • • Review missed grammar rules immediately after

Mock 3 — Game-based Cognitive Simulation

  • • Time 4 different game types back-to-back
  • • Focus on instructions and accuracy, not raw speed

Mock 4 — Coding Round

  • • 2 problems in 75 minutes at easy-to-medium difficulty
  • • Test with empty, single-element and duplicate inputs

Mock 5 — Interview Simulation

  • • 25 min technical covering OOP, DBMS, OS, networks and project
  • • 15 min HR covering shifts, relocation and motivation

Final Checklist

Tick all of these before test day.

Must-do: percentages, profit & loss, SI/CI, time & work, speed–time–distance formulas memorised
Must-do: 20+ pseudocode traces solved correctly under time (increment/decrement, division, scope)
Must-do: arrays, strings, sorting, searching and basic math problems coded from memory
Must-do: OOP four pillars, DBMS normalisation and a second-highest-salary SQL query ready
Must-do: OSI layers, TCP vs UDP, deadlock conditions and CPU scheduling basics
Should-do: two pointers, sliding window, hashing, prefix sums and BFS/DFS practised
Should-do: at least two full timed mocks covering every stage of the assessment
Interview-ready: rehearsed project story with role, stack, architecture and hardest bug

Recent Interview Experiences

First-hand write-ups from students who actually sat the Capgemini process.

Be the first to share a Capgemini interview experience.

Frequently Asked Questions

What is the Capgemini exam pattern in 2026?

A multi-stage online assessment: technical MCQs and pseudocode (~40 Qs, 40–50 min), English communication (~30 Qs, 30 min), game-based cognitive ability (4 games, 20–30 min), a PowerSkills behavioural section (20–25 min) and usually 2 coding problems (45–90 min), followed by a technical interview and an HR interview.

What is the difference between Analyst and Software Engineer hiring at Capgemini?

Both roles are usually assessed through the same test. Analyst leans on strong aptitude, English and pseudocode with basic coding; Software Engineer expects stronger technical MCQs, coding and DSA. Final role and package depend on coding performance, overall score, interview and business requirement — not just clearing the cutoff.

How hard is the Capgemini coding round?

Usually easy to medium for Analyst-level hiring, with stronger candidates in the medium range considered for Software Engineer or higher tracks. Expect 2 problems in 45–90 minutes depending on the drive.

What is the Capgemini game-based cognitive test?

It replaces a conventional aptitude paper with 4 games measuring working memory, pattern recognition, deductive reasoning, planning and numerical ability. Read every instruction fully — accuracy matters more than speed, and there is no hidden scoring trick to reverse-engineer.

Is the Capgemini PowerSkills/behavioural round an elimination round?

It is generally non-elimination but scored, and it feeds into your overall profile alongside the interview, so answer consistently in favour of communication, ownership and following process.

What should I revise for the Capgemini technical interview?

Your final-year project in depth, OOP four pillars, DBMS normalisation and SQL (especially the second-highest-salary query), OS basics (process vs thread, deadlock, scheduling) and networking basics (OSI layers, TCP vs UDP, three-way handshake).

Want the full structured prep for Capgemini?

The Premium Vault covers Aptitude, Core CS, DSA, SQL and HR rounds with module-wise courses and drill sheets.

Next steps chosen from the Capgemini pattern and other IT Services (Mass Hiring) recruiters.

Other IT Services (Mass Hiring) companies

Core CS subjects for this pattern

Recommended practice path