Candidates describe KPMG software engineer interviews as a mix of screening, resume-driven technical conversations, and behavioral or manager rounds. Stack depth and format vary widely by team and hiring route.
$105K
Avg. Base Comp
$130K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
KPMG software engineer interviews, as candidates describe them, lean more on conversation than on hard algorithm puzzles. The most repeated theme is the resume. Several candidates say the technical discussion was built around the projects and skills on their CV, including what they built, what they contributed and what they would improve. One candidate was asked to walk through projects in Git, which made the round feel like a practical conversation about real work.
The format varies a lot. Some candidates describe a campus-style funnel with an aptitude or online assessment, a group discussion, technical rounds and HR. Others report a short CV screen, an HR call, and a manager conversation. One candidate went through psychometric games and group exercises before a final partner interview.
Technical content tends to be fundamentals. Candidates mention OOP, DSA, DBMS and basic SQL, such as joining two tables or finding the highest salary. One reported a live binary search tree question. Stack-specific depth shows up in some reports, including Java and Spring, JavaScript and Node, SAP ABAP and UI5, and session fixation and hijacking. Practice the technologies you list rather than a generic question set.
Several reports also stress communication and fit: English fluency, why KPMG, and teamwork. Timelines are inconsistent. One candidate reported about a day, another a little over a month, and one said a role went on hold after documents were submitted. Ask recruiters about next steps early. Outcomes in this set skew toward no offer, so rehearse specific, honest project stories.
Synthesized from 15 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 Kpmg process.
The interview started with a self-introduction in English, which felt pretty straightforward. After that, things got interesting — the technical questions came through in Vietnamese, which caught me off guard. I'd prepared for standard coding problems, but the emphasis here wasn't just on algorithm complexity. They were really focused on understanding how I thought about operational and technical trade-offs, asking things like how I approach overtime and work-life balance in high-pressure situations. The soft skills portion mixed English and Vietnamese as well, so they were testing both my technical communication and my ability to articulate ideas across languages. The whole thing wrapped up in about thirty minutes. What stood out most was that they seemed equally interested in my problem-solving approach and my values around working sustainably — it wasn't a pure coding grind. I also learned afterward that there's an online assessment component (Pulsify) that comes into play earlier in their process, with a mix of easy coding questions and a lot of mission-alignment questions to gauge cultural fit.
Prep tip from this candidate
Be ready for technical questions delivered in languages other than English, and prepare thoughtful answers about work-life balance and operational trade-offs — KPMG weighs both your technical chops and your alignment with sustainable work practices. The online assessment emphasizes mission fit as much as coding ability, so research KPMG's values before you start.
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 Kpmg
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Rolling Bank Transactions | |
| P-value to a Layman | |
| Longest Streak Users | |
| Hurdles In Data Projects | |
| Spam Classifier | |
| Modifying a Billion Rows | |
| Algorithm Reliability | |
| Scalable Data Pipelines | |
| Testing Constraints | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Statistically Significant Test | |
| Delivery Online | |
| Branch Sales Pivot | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Size of Joins | |
| Top 3 Users | |
| Raining in Seattle | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Skyscanner Partner ETL | |
| Sort Strings | |
| Real-Time Transaction Streaming | |
| Normalize Grades | |
| Resumable Fact Table Load | |
| Cyclic Detection |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings. Some describe a CV review followed by an HR call about background, interests and motivation. Others describe an aptitude or online assessment covering aptitude, verbal and coding, and one mentions a personality test.
A few candidates describe a group discussion before the technical interviews. One reports psychometric games plus group exercises with Legos and virtual reality in a fast, roughly one-day process. This stage does not appear in every report, so it may depend on the team or hiring route.
Candidates typically report that the technical interview was driven by the projects on their CV. Topics mentioned include OOP, DSA, DBMS, SQL joins, Java and Spring, JavaScript and Node, SAP ABAP and UI5, session security concepts and, in one report, a binary search tree. Depth appears to vary by team, and some describe it as light or conversational.
Candidates report manager or behavioral conversations covering teamwork, background, project contributions and why they want to join KPMG. One described the managerial round as a stress test, while others found it relaxed. Prepare concrete examples from your own projects.
Some candidates report a final HR or partner conversation covering background, expectations and salary. Follow-up was reported as slow or unclear in several accounts: one waited about two weeks with no word, and one saw a role placed on hold. It is reasonable to ask about timing and role status directly.
