Genpact Interview Experience For Consulting Engineering Full Time (On-Campus)
Interview Experience
I would like to share my experience with the on-campus placement procedure for Genpact, where I interviewed for a full-time consulting engineering role. The joining was sc...
Full Details
I would like to share my experience with the on-campus placement procedure for Genpact , where I interviewed for a full-time consulting engineering role. The joining was scheduled after the completion of the degree, and the compensation package offered ranged between ₹630,000 to ₹700,000 per annum. The work location was PAN India. Hiring Process Overview The hiring process for the Genpact role consisted of the following rounds: Speech Test Pre-Placement Talk Online Test Group Discussion Technical Interview Project Submission
Round 1 Speech Test The first round was the Speech Test, which was designed to assess your listening, speaking, and writing skills. This round tested your communication abilities, including clarity, coherence, and language proficiency.
Round 2 Pre-Placement Talk The second round was the Pre-Placement Talk, where the company provided an overview of Genpact as an organization. This session included key information about the company’s culture, the role being offered, salary distribution, and the probation period of 4 to 6 months.
Round 3 Online Test The third round was an online assessment, where the focus was on testing your computer science fundamentals and coding skills. The difficulty of the coding questions ranged from easy to medium. In addition to coding, the test also included questions related to general problem-solving and logical reasoning.
Round 4 Group Discussion The fourth round was a Group Discussion (GD), held offline. This round was crucial as it served as the main elimination round. The panel evaluated candidates based on their soft skills, including communication, teamwork, and how effectively they could express their opinions in a group setting. Strong interpersonal skills were a key factor for selection in this round.
Round 5 Technical Interview In the Technical Interview round, candidates were asked about language-specific fundamentals, Object-Oriented Programming (OOP) concepts, and basic coding questions. The interview was relatively straightforward, but it was important to demonstrate a solid understanding of programming principles and problem-solving skills.
Round 6 Project Submission The final round was the Project Submission. After the technical interview, candidates were given a deadline to create and submit a real-world full-stack working project. This project was the deciding factor for many candidates. Those who completed and submitted the project within the given timeframe were selected for the role. Conclusion Genpact’s hiring process is thorough, with each round designed to assess different aspects of a candidate’s abilities, from communication and soft skills to technical expertise and project execution. The process includes a mix of individual and group activities, and a strong performance in all rounds is essential to securing the position. Good luck to anyone preparing for Genpact's placement process!
About This Question
This is a candidate experience report from a genpact interview for a fullstack role during the oa round reported in 2024.
It covers the following topics: Oop, Sql, Stack Queue, Probability Stats, Stack .
Difficulty rating: Easy
Topics
More Genpact Interview Questions
About Genpact Interview Reports
This question was reported by a candidate who interviewed at Genpact. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Genpact are the higher-signal extractions to take from this report.
For broader preparation context, the Genpact interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Genpact reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Genpact Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Genpact reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.