cswork / libraryOpen practice workspace

Interview guides · KPMG Philippines

KPMG Philippines Software Engineer Interview Guide

KPMG Philippines Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at KPMG Philippines, you are not merely writing code; you are building the technological backbone that powers high-stakes professional services. You will be responsible for developing, maintaining, and scaling software solutions that drive efficiency for both internal operations and external client-facing projects. This role demands a blend of technical precision and the ability to translate complex business requirements into robust, secure, and performant systems. The impact of this position is significant. You will contribute to digital transformation initiatives, potentially working on infrastructure advisory, data-driven reporting, or automation tools that simplify professional workflows. Because KPMG operates in a highly regulated environment, your work will be scrutinized for security, scalability, and maintainability.

This guide is scoped to a Software Engineer candidate at KPMG Philippines.

Focus areas

  • SQL
  • SQL JOINs
  • SAP S/4HANA Cloud

The KPMG Philippines interview process

KPMG Philippines candidates report 5 rounds over 4-6 weeks. The stages below are what candidates describe, not a published process.

Application Review

Initial review of your application to assess qualifications and fit.

What to demonstrate

  • Initial review of your application to assess qualifications and fit
  • Depth in SQL

How to prepare

  • Be able to walk your CV end to end in two minutes, and say why this company specifically.
  • Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.

Technical Screening

Foundational technical assessments including online coding challenges or live technical sessions.

What to demonstrate

  • Foundational technical assessments including online coding challenges or live technical sessions
  • Depth in SQL

How to prepare

  • Answer aloud and timed: What are the fundamental principles of ITSM (IT Service Management) that impact software development?
  • Answer aloud and timed: Can you explain your experience with specific tech stacks mentioned on your resume?

Manager Discussion

Deep-dive discussions with managers to evaluate your problem-solving style and potential for growth.

What to demonstrate

  • Deep-dive discussions with managers to evaluate your problem-solving style and potential for growth
  • Depth in SQL

How to prepare

  • Answer aloud and timed: How do you approach deleting duplicate records in a large SQL database?
  • Answer aloud and timed: Describe your biggest software implementation project and the challenges you overcame.

Behavioral Interview

Focus on previous projects, handling past failures, and team-based collaboration.

What to demonstrate

  • Focus on previous projects, handling past failures, and team-based collaboration
  • Depth in SQL

How to prepare

  • Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
  • Re-read the description of the behavioral interview above and write down what you would ask to confirm before it.

Leadership Interview

Final discussions with leadership to assess cultural fit for client-facing teams.

What to demonstrate

  • Final discussions with leadership to assess cultural fit for client-facing teams
  • Depth in SQL

How to prepare

  • Answer aloud and timed: Walk me through how you would design a system to address a specific business bottleneck.
  • Answer aloud and timed: Describe a situation where you faced difficulty with incorrect or inconsistent data.

Where candidates lose points

Own your resume

Be prepared to discuss every project listed in detail. If you mention a technology, be ready to explain it at an expert level.

Think out loud

During coding sessions, explain your thought process. We are more interested in how you approach a problem than if you reach the perfect solution immediately.

Ask meaningful questions

Use the time at the end of the interview to ask about the team’s current challenges or the firm's approach to technology. It shows you are already thinking like a member of the team.

Prepare for behavioral questions

Use the STAR method (Situation, Task, Action, Result) to structure your answers for all behavioral and situational questions.

Questions & practice

Describe your biggest software implementation project and the challenges you overcame.

Medium · Problem-Solving & Coding

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Given a string manipulation task, how would you optimize your solution for time and space complexity?

Medium · Problem-Solving & Coding

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

How do you approach a problem that requires dynamic programming to solve efficiently?

Medium · Problem-Solving & Coding

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

How do you approach deleting duplicate records in a large SQL database?

Medium · Technical & Domain Knowledge

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

Hold a per-tenant active cap against concurrent creates

Hard · write skew · isolation levels · constraints

A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.

Approach

  1. Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
  2. Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
  3. Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
  4. State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.

Follow-up

  • A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
  • The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?

Explain the difference between star and snowflake schemas and provide the pros and cons of each.

Medium · Technical & Domain Knowledge

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What are the fundamental principles of ITSM (IT Service Management) that impact software development?

Medium · Technical & Domain Knowledge

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Walk me through how you would design a system to address a specific business bottleneck.

Medium · Problem-Solving & Coding

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

Listing latency scales with page size, not with filters

Easy · n+1 · latency · query batching

The tenant listing endpoint reads resource filtered by tenant_id and status, ordered by updated_at DESC, and returns each row plus the owner's display name from app_user and the actor of that resource's latest resource_revision. p99 is 55 ms at 10 rows per page and 1.4 s at 200. Database telemetry shows 401 statements per request, each under 1 ms, and nothing in the slow-query log. Diagnose the cause and give the fix, stating the statement count per request and the p99 you expect afterwards.

Approach

  1. Read the counters before forming a theory. 401 statements for 200 rows is one driver query plus two per row, and sub-millisecond execution with an empty slow-query log rules out a bad plan. The time is round trips, which is why it is invisible in every per-query metric and scales with rows returned rather than with filter selectivity.
  2. Name the two per-row statements from their normalised text: a single-row app_user lookup by user_id, and a resource_revision lookup by resource_id ordered by version DESC LIMIT 1. Confirm by dropping those two response fields and watching the statement count fall to one. That locates the calls in the serialisation layer, not the repository.
  3. Check that the arithmetic accounts for the whole gap. Measure one round trip to the replica in isolation; 400 trips at roughly 3 ms of network plus 0.2 ms of execution is about 1.3 s on top of a 55 ms baseline, which matches. If the multiplication had fallen short, the N+1 would only be part of the story and you would keep looking.
  4. Batch both lookups. Collect owner_user_ids and resource_ids from the driver query, then issue WHERE tenant_id = $1 AND user_id = ANY($2) for the users, and PostgreSQL's SELECT DISTINCT ON (resource_id) ... WHERE resource_id = ANY($2) ORDER BY resource_id, version DESC for the latest revision, which the UNIQUE (resource_id, version) index serves directly. On an engine without DISTINCT ON, use a lateral join or a row_number window. Three statements per request at any page size.

Follow-up

  • The page size is capped at 200 today. What breaks first if it is raised to 2,000, and is it still this bug?
  • How do you stop the next N+1 from reaching production, given that no individual query is slow and the endpoint's tests pass?

Suggested practice checklist

Built from the rounds and topics KPMG Philippines candidates report.

Day 1 — Map the KPMG Philippines loop

  • Write out the reported sequence: Application Review, Technical Screening, Manager Discussion, Behavioral Interview, Leadership Interview.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 5 reported rounds, with the weakest marked.

Day 2 — Work SQL

  • Spend the session on SQL, which KPMG Philippines candidates report being tested on.
  • Write one worked example in SQL and time yourself on it.

Deliverable: One timed worked example in SQL.

Day 3 — Work SQL JOINs

  • Spend the session on SQL JOINs, which KPMG Philippines candidates report being tested on.
  • Write one worked example in SQL JOINs and time yourself on it.

Deliverable: One timed worked example in SQL JOINs.

Day 4 — Work SAP S/4HANA Cloud

  • Spend the session on SAP S/4HANA Cloud, which KPMG Philippines candidates report being tested on.
  • Write one worked example in SAP S/4HANA Cloud and time yourself on it.

Deliverable: One timed worked example in SAP S/4HANA Cloud.

Day 5 — Answer out loud: Technical & Domain Knowledge

  • Answer aloud, timed: Explain the difference between star and snowflake schemas and provide the pros and cons of each.
  • Answer aloud, timed: How do you handle data integrity issues or misunderstandings of reports by stakeholders?

Deliverable: Spoken answers to 2 reported Technical & Domain Knowledge question(s), under time.

Day 6 — Answer out loud: Problem-Solving & Coding

  • Answer aloud, timed: Describe your biggest software implementation project and the challenges you overcame.
  • Answer aloud, timed: Given a string manipulation task, how would you optimize your solution for time and space complexity?

Deliverable: Spoken answers to 2 reported Problem-Solving & Coding question(s), under time.

Day 7 — Answer out loud: Behavioral & Situational

  • Answer aloud, timed: Describe a situation where you faced difficulty with incorrect or inconsistent data.
  • Answer aloud, timed: Tell me about a time you had to explain a technical limitation to a stakeholder.

Deliverable: Spoken answers to 2 reported Behavioral & Situational question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

How do you handle data integrity issues or misunderstandings of reports by stakeholders?

Medium · Technical & Domain Knowledge

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Can you explain your experience with specific tech stacks mentioned on your resume?

Medium · Technical & Domain Knowledge

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Describe a situation where you faced difficulty with incorrect or inconsistent data.

Medium · Behavioral & Situational

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Tell me about a time you had to explain a technical limitation to a stakeholder.

Medium · Behavioral & Situational

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Why are you interested in joining KPMG specifically, and how do you align with our mission?

Medium · Behavioral & Situational

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you handle feedback on your code from senior members of the team?

Medium · Behavioral & Situational

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?