Kpmg Software Engineer interview typically runs 3-4 rounds: online assessment, technical interview, behavioral interview, and sometimes HR or manager round. Timeline is usually a few weeks to over a month, and the process is structured but can move slowly.
$104K
Avg. Base Comp
$114K
Avg. Total Comp
4-6
Typical Rounds
2-5 weeks
Process Length
We’ve seen KPMG evaluate software engineers less like a pure algorithm shop and more like a firm that wants to verify whether you can operate across fundamentals, client-facing communication, and the stack you claim on paper. Multiple candidates reported that the interviewers kept pulling directly from their resumes and past projects, asking them to explain systems, connectors, Git work, and concrete contributions in detail. That means the real signal is whether your experience sounds lived-in, not rehearsed. If you list Java, Spring, SAP, or backend work, expect the conversation to go past surface-level familiarity and into specific implementation choices.
A recurring theme is that KPMG likes to mix broad CS basics with domain-specific checks. We’ve seen questions on BSTs, DSA, SQL joins, OOP, DBMS, Java 8, Spring Boot, and even security concepts like session fixation and session hijacking. In other words, they’re not chasing exotic problems; they’re checking for solid fundamentals plus stack credibility. Candidates also repeatedly mentioned English fluency, clarity, and how comfortably they could explain their thinking, which suggests the interviewers are listening for precision as much as correctness.
The non-obvious part is how much the process rewards calm, direct communication. Several candidates described polite, structured interviewers who were more interested in how they discussed prior work, teamwork, and improvements than in trying to trap them. Even the more relaxed conversations still circled back to project ownership and practical understanding. Our candidates report that the people who do best here are the ones who can connect their resume to real technical depth without overexplaining or drifting into generic answers.
Synthetized from 7 candidates 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 process was pretty straightforward and felt more technical than behavioral overall. I went through three rounds: first an online assessment, then a DSA-focused round, and finally a behavioral interview. The OA was the usual screening step, but the second round was where they really checked whether I could solve problems live. The main coding question I got was on a binary search tree, so I made sure to talk through my approach clearly instead of rushing straight into code. That round felt manageable if you were comfortable with core data structures and could explain your reasoning as you went.
What stood out to me was that they cared a lot about prior hands-on knowledge too, not just algorithms. In the behavioral/conversation part, they kept circling back to what I had worked on before, especially systems, tools, connectors, and basic IAM-related concepts like RBAC and Linux. English fluency also seemed to matter in the way the interview was run. The interviewers were very polite and direct, and the whole process felt fair. I finished all three rounds without much trouble, but I ultimately didn’t get the offer. If you’re preparing, I’d focus on being able to discuss your past projects clearly and brush up on BST basics and foundational IAM/system concepts, since that combination seemed to drive most of the evaluation.
Prep tip from this candidate
Be ready for a live BST question in the DSA round, and don’t neglect basic IAM/system vocabulary — they seemed to probe connectors, tools, RBAC, Linux, and your past project experience pretty directly.
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
Explain what a p-value is to someone who is not technical
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Testing Constraints | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Raining in Seattle | |
| Cyclic Detection | |
| Sort Strings | |
| Find Duplicate Numbers in a List | |
| Slow SQL Query | |
| Yelp-like System | |
| Swap Variables | |
| Subway Machine Learning Model | |
| String Palindromes | |
| Seller Type Modeling | |
| Impossibly Iterative Fibonacci | |
| Stakeholder Communication | |
| Text Editor With OOP | |
| Client Solution Pushback | |
| Simple Explanations | |
| Creating Companies Table | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Comments Histogram |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with a resume or CV review before any live interviews. In some cases, candidates also had an initial phone call to confirm basics like programming level, English fluency, background, and availability.
Candidates commonly complete an online screening test before technical interviews. The assessment may include aptitude, verbal reasoning, logic, DSA, coding, and even psychometric or game-based tasks such as memory or sequence exercises.
Some candidates reported a group discussion or assessment-center style exercise after the online test. These sessions included structured group dynamics such as Lego-based or virtual reality activities, along with short individual presentations.
This round focuses on coding fundamentals, data structures, algorithms, and resume/project deep-dives. Questions varied by background and role, including live problem solving, SQL, OOP, DBMS, Java/Spring, JavaScript/Node, SAP technologies, and security basics like session fixation and session hijacking.
Interviewers assess communication, teamwork, motivation, and fit with KPMG’s culture. Candidates were asked about past projects, contributions, conflict handling, curiosity, strengths, interests, and why they wanted to join the company.
The final stage is typically an HR or closing conversation, sometimes followed by a manager or partner interview depending on the track. This round often covers compensation, documentation, expectations, and final fit checks before a decision is made.