Genpact software engineer candidates describe resume-driven interviews covering Java, OOP, SQL and core CS basics. Some add an aptitude or online test, a client technical round, and a manager or HR conversation.
$108K
Avg. Base Comp
$120K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describing Genpact software engineer interviews often say the conversation starts with their resume. Several report being asked to walk through their projects, the technologies they used, the challenges they faced and what they learned. One says the interview covered the technologies listed on their resume, so only list skills you can defend with real examples.
Technical content varies by team and track. Java shows up repeatedly. One candidate was tested on DSA and Java fundamentals with coding problems, and another was pressed on exact syntax for the Java Stream API and Executor Service. A third describes a pen-and-paper test at the office that leaned on system design, microservices patterns, JVM internals, design patterns and SOLID principles. SQL is another recurring theme, with reports of a second-highest-salary query, window functions and basic PL/SQL. Other candidates mention OOP, operating systems, networking basics such as subnets and default gateways, Unix, and Python tasks like a recursive factorial or reading a CSV file. Some describe the bar as basic.
Structure also differs. Some candidates describe a phone screen, an aptitude test or an online test before the interviews, including one technical round on HackerRank. Several mention a separate client-side technical round. Reported formats range from two to four rounds, often ending in a manager or HR conversation.
Outcomes are mixed. Some candidates report offers, while others were rejected after technical rounds. Communication matters throughout, and one candidate noted an emphasis on English proficiency. Practise explaining your reasoning aloud as well as writing code.
Synthesized from 25 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Genpact process.
My resume was shortlisted through Naukri, and the process kicked off with an internal technical evaluation. The first round was a pen-and-paper technical test conducted at their office, which covered a broad range of Java full-stack fundamentals but leaned heavily into architecture—system design, microservices patterns, and JVM internals. After clearing that, I moved into two rounds with the client side. The second round was another technical evaluation, and the third combined deeper technical discussion with a managerial component, where they assessed both my technical depth and how I'd fit into their team structure. The questions throughout were less about algorithm trivia and more about design patterns, SOLID principles, and the ability to reason about complex systems. The final step was an HR round to close things out. What surprised me most was how much emphasis they placed on architectural thinking rather than grinding through data structure problems—they wanted to see if I could design systems, not just optimize code. The entire process moved fairly smoothly, and I received an offer shortly after.
Prep tip from this candidate
Focus your preparation on system design and architecture patterns—microservices, JVM architecture, and SOLID principles appear consistently. Practice explaining design decisions and trade-offs rather than memorizing algorithms.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Genpact
Create top_ads with the top 3 ads and return the row counts for inner, left, right, and cross joins with ads
| Question | |
|---|---|
| Sort Strings | |
| Hurdles In Data Projects | |
| Cumulative Sales By Product | |
| Digit Accumulator | |
| Count Transactions | |
| loc vs iloc | |
| Branch Sales Pivot | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Find the Missing Number | |
| Retailer Data Warehouse | |
| Over-Budget Projects | |
| Maximum Profit | |
| P-value to a Layman | |
| Find the First Non-Repeating Character in a String | |
| First Touch Attribution | |
| Employee Project Budgets | |
| The Brackets Problem | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different entry points. These include a phone screen about background and education, a general aptitude test followed by a HackerRank technical round, an online test, or a pen-and-paper technical test at the office. Expect the format to depend on the hiring route.
Candidates typically describe a technical conversation anchored on their projects. Reported topics include Java and OOP, DSA coding problems, SQL queries and window functions, Python basics, and OS, networking or Unix fundamentals. Some call the difficulty basic, while one describes exact-syntax questions on the Java Stream API and Executor Service.
Several candidates describe a second technical round with the client side. One says it went deeper on complexity and optimization. Another describes two client rounds, the second combining technical depth with a managerial assessment. Not every candidate reports this stage.
The final stage is commonly reported as a manager and/or HR conversation. Candidates describe questions on their background and projects, soft skills backed by real-time examples, and how they would work with the team. Several note that clear communication is weighed heavily.
