KPMG Software Engineer interviews typically combine an online assessment or recruiter screen with a resume-driven technical round covering SQL, DSA, or stack-specific topics, plus behavioral conversations; rounds and timelines vary by team and track.
$105K
Avg. Base Comp
$125K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
KPMG's Software Engineer interviews are less about LeetCode grinding and more about proving you can defend what's already on your resume. The technical rounds lean heavily on project walkthroughs. Candidates describe interviewers pulling questions straight from their resumes and asking them to walk through projects, explain their own contributions, and suggest improvements; one candidate walked through projects in Git. SQL comes up repeatedly, ranging from joining two tables and finding the highest-salaried person to getting one table from another and naming an alternative approach. Data structures also appear, including a live binary search tree problem where talking through the approach mattered, along with OOP and DBMS basics.
Stack-specific depth seems to track the team rather than one fixed rubric. One candidate faced Java 8 streams, final versus finally, Hibernate, and Spring Boot actuators. Another had a 50-minute deep dive on ABAP and SAP UI5. A third got advanced JavaScript and Node architecture questions. Security basics such as session fixation and session hijacking, and IAM concepts like RBAC and Linux, surfaced in a couple of interviews.
Expect HR and fit conversations too, covering your background, why KPMG, team communication, and strengths. One managerial round used situational questions that felt like a stress test. Some campus-style tracks add aptitude or psychometric tests and group exercises before the technical interview. Timelines vary from a single day to a little over a month, and a couple of candidates were left waiting after late-stage rounds. Clarify next steps and offer status as you go.
Synthesized from 14 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 starting with a CV screen, an HR conversation, or an online assessment. Reported tests include aptitude, verbal, coding, core CS, and DSA. One candidate described psychometric games such as memorizing number sequences, and another received a personality test link. These early steps appear designed to filter candidates before deeper technical rounds.
Some campus-style candidates report a group discussion round. One candidate described two separate group dynamics, one using Legos and another using virtual reality, which followed short individual presentations. This stage appears in campus-style pipelines and may not apply to every applicant, so confirm your track with the recruiter.
The core technical round typically centers on your resume: interviewers ask you to walk through projects and your own contributions. Candidates report SQL prompts such as joining tables or finding the highest salary, a live binary search tree problem, and OOP and DBMS basics. Stack-specific deep dives covered Java 8/Spring, JavaScript/Node architecture, or ABAP/SAP UI5, suggesting the technical bar shifts with the team.
Most reports include an HR or behavioral conversation covering background, education, interests, why KPMG, team communication, and strengths. One candidate was asked whether they are a curious person. Another was asked about remaining university or military obligations. Salary expectations came up in at least one HR discussion.
Several candidates describe a closing round with a manager or partner. Reports range from relaxed conversations about background and past projects to a situational round that felt like a stress test. Outcomes and timing varied: one offer came after a process of a little over a month, and some candidates heard nothing after late-stage rounds.
