Coding questions
How to Prepare for Genpact
Genpact roles vary from pure process to tech. Many campus drives prioritize aptitude, communication, and basic tech. Match the JD.
What Genpact actually tests
First round: Genpact aptitude / role assessment
Time split that matches how candidates report outcomes (not a marketing pie chart):
- Aptitude 40%
- Coding basics 30%
- Core CS 20%
- HR 10%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Hiring flow you should prep for
| Stage | Time | What they check |
|---|---|---|
| Assessment | timed | Aptitude / communication |
| Interviews | varies | HR + basic tech |
Time allocation
- Aptitude (40% time) - Practice quantitative, logical reasoning, and verbal ability
- Coding (30%) - Solve problems in C, C++, Java, or Python
- Technical Concepts (20%) - Review DBMS, OOPs, OS, and networking basics
- Interview Preparation (10%) - Practice technical and HR interview questions
Daily loop (90-120 minutes)
- One timed block that matches Genpact’s first round (aptitude + coding OA)
- Log misses: topic + why you failed (speed, concept, carelessness)
- Re-solve yesterday’s misses cold
- Twice a week: 10 minutes of resume/project narration out loud
6-8 week service-company plan
| Week | Focus | Exit criteria |
|---|---|---|
| 1-2 | Quant + reasoning speed | 2 full aptitude mocks, >70% accuracy |
| 3-4 | Verbal + programming logic / pseudo-code | Comfortable under sectional timers |
| 5-6 | Coding basics + CS fundamentals | 1-2 coding problems solvable cleanly |
| 7-8 | Full mocks + interview answers | Sectional cutoffs cleared in mocks |
Round-by-round strategy
Online Assessment
- Sectional cutoffs matter more than a hero score in one section
- Quant/reasoning: skip time sinks after 90-120 seconds
- Verbal: accuracy over vocabulary flex
- Coding/pseudo: get one clean full solve before polishing a second
Technical interview
- OOPs, DBMS, OS, Networks - definitions plus one example each
- Be ready to write a simple program on paper/editor
- Project explanation: problem → your work → result (numbers if any)
HR
- Why Genpact, gap years, location preference, bond/notice if asked
- Speak clearly; service HR rounds fail quiet candidates more than imperfect ones
Genpact-specific drills
- Aptitude + verbal
- Communication practice
- Basic Excel/SQL if analyst track
Topic checklist
- Aptitude speed with sectional accuracy
- One coding language for basic problems
- OOPs, DBMS, OS one-liners you can expand
- HR answers: why company, relocation, gaps
- Pseudo-code / output prediction
- Essay or communication modules when present
- Full-length mock every other day
- Light revision only - no new rabbit holes
- Sleep, ID proofs, machine/network checklist for test day
Final stretch
30 days out: 3+ full Genpact-pattern mocks per week; build an error log by section.
7 days out: one mock every other day; revise only error-log topics; rehearse HR answers aloud.
Day before: light revision, no all-nighters - sectional exams punish fatigue.
Common mistakes for Genpact aspirants
- Over-indexing on hard DSA for process/analyst roles - fix this first
- Preparing only interviews while failing Genpact’s first round
- Collecting notes without timed mocks
- Listing five frameworks on the resume and defending none
- Changing language/stack one week before the drive
- Grinding LeetCode hard while failing aptitude cutoffs
Practice on this site
- Genpact aptitude / mock quiz
- Genpact coding questions
- Genpact interview experience
- Genpact previous year papers
- Genpact 2026 guide
- Genpact hub
- PDF: Genpact Placement Papers PDF (2026)

