KPMG India Interview Guide (2026)

1Snapshot, read this first#

The one framing that changes everything: you are hired as a consultant who happens to do tech, not a coder who happens to talk to clients.

• The person across the table is imagining you in front of their client in six months.
• If they cannot picture you explaining a cloud migration to a CFO calmly, your SQL skill does not save you.
• Every answer should turn a technical choice into a business outcome: time saved, risk removed, money protected.

2Getting the call (the part most guides skip)#

KPMG India fills tech roles through three doors: campus placements, off-campus assessment drives, and experienced-hire referrals. For a services firm, one move beats all others.

Referral first, everything else second.

• An existing employee submitting your profile skips the resume black hole.
• It often drops the assessment link into your inbox within a day or two.
• One warm referral is worth fifty cold portal applications.
• Find KPMG tech consultants from your college or past teams on LinkedIn, send a short specific note, ask for a referral against a named role ID.

No referral? Then speed and timing.

• Apply through the KPMG India careers portal and LinkedIn on the day a role posts.
• Recruiters screen the earliest applicants hardest; a role live for three weeks is often already in interviews.
• Watch the off-campus assessment campaigns KPMG runs through testing platforms every few months. Plenty of early-career candidates get in purely by registering and clearing the cutoff.

Resume rules. One page for early-career, two max for experienced.

• Lead every bullet with a verb, end it with a number.
• Weak bullets describe duties; strong bullets prove impact.
• The test for every line: could a lazier version of you have written it? If yes, add the number that makes it yours.

Weak: "Worked on data pipelines and reporting."

Strong: "Built an automated SQL + Python reporting pipeline that cut a manual month-end close from 3 days to 4 hours for a 12-person finance team."

ATS keywords. Mirror the posting's exact phrasing, not a synonym.

• A human may never see your resume if the parser does not match.
• Recurring terms for KPMG tech roles: SQL, data modeling, ETL, Python, cloud (Azure/AWS/GCP), Power BI/Tableau, the relevant ERP (SAP/Oracle).
• Softer phrases that recur: "stakeholder management," "requirement gathering," "client delivery."
• If the posting names a specific platform, put it in the top third of the page, where both the parser and a skimming recruiter catch it in ten seconds.

How people actually get shortlisted here: a clean, keyword-matched resume, plus either a referral or an early application, plus a passed online assessment. The assessment is the real gate. I have seen people with great resumes never reach a human because they missed the cutoff by two questions.

3The loop at a glance#

The four stages and exactly what each one is grading.

Not every candidate gets all four.

• A campus drive may compress technical and case into one 45-minute conversation.
• An experienced hire may get an extra domain deep-dive with a practice lead.
• The order and count flex; the three gates (aptitude, fundamentals, communication) do not.

4The technical rounds, patterns, not problems#

For KPMG India the coding bar is lighter than a product company, but the aptitude and applied-fundamentals bar is real and sharp. Here is where the questions cluster, in rough order of how often they decide the outcome.

Aptitude (the gate). Classic quantitative and reasoning, the campus-placement families, under tighter time.

• Quantitative: percentages, ratios and proportion, profit and loss, time-speed-distance, time and work, averages, simple and compound interest, permutations and probability basics.
• Logical reasoning: seating arrangements, blood relations, syllogisms, coding-decoding, number and letter series, data sufficiency.
• Verbal: reading comprehension, sentence correction, para-jumbles, vocabulary in context.
• Data interpretation: tables, bar and pie charts, computing ratios and growth under time pressure.

Speed matters as much as accuracy here.

• A question you solve in 90 seconds scores the same as one you agonize over for four minutes, except the four-minute one cost you two other questions.
• Practice by section, time yourself to the second, build the skip-and-return reflex.
• Mark the hard one, bank the easy points, come back if time allows.
• The candidates who clear are rarely the smartest. They are the ones who did not freeze on question seven.

Pseudocode / technical section. Many assessments include a short block.

• Output prediction, loop and recursion tracing, basic data structures (arrays, strings, hash maps), language basics.
• You are rarely asked to invent a hard algorithm.
• You are asked to read code correctly, trace a loop to the right final value, reason about time complexity.
• Drill the "what does this print" style. Pure points if you slow down for the off-by-one.

Technical fundamentals (interview). Depending on the track:

• SQL is almost universal: joins, GROUP BY and HAVING, window functions, subqueries, and writing a query live from a word problem. Expect to type it, not just describe it. A classic: "second highest salary per department," which forces a window function or a correlated subquery and separates people who memorized syntax from people who understand it.
• Programming: the four OOP pillars, some Python or Java, string and collection manipulation, and time and space complexity for whatever you write.
• Data and analytics tracks: data modeling (star vs snowflake), ETL concepts, slowly changing dimensions, and one BI tool you can actually demo.
• ERP and cloud tracks: the specifics on your resume and nothing more. Do not list SAP or Azure unless you can answer the second and third follow-up, not just the first.

A SQL pattern worth drilling until it is reflex, the second-highest-value-per-group query:

SELECT department_id, salary
FROM (
  SELECT department_id,
         salary,
         DENSE_RANK() OVER (
           PARTITION BY department_id
           ORDER BY salary DESC
         ) AS rnk
  FROM employees
) ranked
WHERE rnk = 2;

How to win the round. In consulting the reasoning is the product, so make it visible.

• Think out loud so the interviewer sees your reasoning, not just your result.
• Restate the problem and clarify assumptions before you write a line.
• When you write SQL, narrate what each clause does and why you chose it over the alternative.
• State the complexity or the trade-off even when nobody asked.
• Sanity-check against a small example you invent on the spot, say a three-row table.
• A reasoned "here is my approach, and here is where it could break" beats a silent correct answer almost every time, because the silent answer does not tell them whether you got lucky.

5CS fundamentals & the case/scenario round#

Because KPMG is services-first, the design round is usually a case or scenario plus fundamentals, not a scale-to-a-billion-users whiteboard. Prepare two things.

CS fundamentals (be crisp, not deep). The goal is a confident one-liner with a concrete example, not a textbook paragraph.

• OOP: encapsulation, inheritance, polymorphism, abstraction, each with a one-line real example. "Polymorphism: a generateReport() method that behaves differently for a PDF vs an Excel exporter."
• DBMS: normalization (1NF to 3NF), indexing and when an index hurts writes, ACID, primary and foreign keys, join types, and when a NoSQL store beats a relational one.
• OS: process vs thread, the four deadlock conditions, basic scheduling, memory vs disk trade-offs.
• Networking: the OSI and TCP/IP layers at a high level, HTTP vs HTTPS, and the full "what happens when you type a URL and press enter" walk from DNS to render.

The case/scenario round. You may get "a client's monthly reporting is slow and error-prone, how would you approach it?" or "a bank wants to migrate on-prem data to cloud, walk me through it."

• These are open on purpose. The interviewer wants to watch you impose structure on a vague problem, which is exactly the job.

• Use a simple consulting framework and say the steps out loud.

• Clarify the goal, constraints, timeline, and who the stakeholders are. Ask before you assume.

• Structure the problem into 2-4 buckets, for example current state, target state, risks, and plan.
• Reason through each bucket with a hypothesis and the data you would gather to test it.
• Recommend a concrete next step and name the trade-offs you are accepting.
• Quantify the impact where you can: hours saved, error rate cut, cost avoided, risk reduced.

The interviewer grades structure and communication more than the single "right" answer. There usually is not one right answer. Narrate your thinking and check in as you go ("does that framing match what you had in mind?"), because a consultant who never reads the room loses the client.

6Behavioral & culture fit#

KPMG's culture is anchored in its global values, and they show up directly in the HR and partner round: Integrity, Excellence, Courage, Together, and For Better.

What they are actually listening for behind each value:

• Integrity: do you do the right thing even when it is inconvenient.
• Excellence: do you set a high bar for your own work.
• Courage: will you speak up and take the hard problem instead of the safe one.
• Together: are you a genuine team player across levels and across the client's org.
• For Better: do you want your work to create real impact beyond the invoice.

Do not recite the values. Show one in a story and let them connect the dots.

Build your STAR bank. Write 6-8 stories (Situation, Task, Action, Result) covering:

• A conflict you resolved.
• A deadline you saved.
• A time you owned a mistake.
• A time you influenced without authority.
• A time you learned something fast.
• A leadership or ownership moment.

Always end on a quantified result, keep each story to about 90 seconds spoken, and rehearse out loud. A story that reads well on paper often rambles when you say it cold.

One full worked STAR example:

• Situation: During my final-year project, our 4-person team was two weeks from a client demo and the data-cleaning step was failing on 30% of records, blocking everything downstream.
• Task: As the person who owned the pipeline, I had to make the demo reliable without missing the date.
• Action: I profiled the failures, found that malformed date and currency fields caused most of them, wrote validation and normalization rules, and added a rejected-records log so the team could see what was dropped and why. I also set a daily 15-minute standup so we caught blockers early.
• Result: Clean-through rate went from 70% to 98%, we delivered the demo on time, and the client approved the project for a second phase. The rejected-records log became the template my juniors reused the next semester.

Why that one lands:

• The number in the result is the proof, not the claim.
• The rejected-records log is honesty made visible (integrity).
• The daily standup is teamwork shown, not stated (together).
• Values shown beat values named, every time.

7Your prep plan#

Pick the plan that matches your runway. All three front-load the gate (aptitude) and back-load the talking (STAR and case).

4-week plan

• Week 1: Rebuild aptitude. One section per day (quant, LR, verbal, DI), always timed. Relearn SQL joins and window functions until they are reflex.
• Week 2: CS fundamentals (OOP, DBMS, OS, networking) compressed into crisp one-liners with examples. Write 20 SQL queries from word problems, no peeking at syntax.
• Week 3: Deep-dive your resume stack and one domain until you can survive three follow-ups on each line. Draft 6-8 STAR stories. Practice two case prompts out loud with a timer.
• Week 4: Full timed mock assessments, a mock HR round with a friend playing partner, polish resume keywords against the exact posting, and read up on KPMG's five values and recent tech-consulting work so your "why KPMG" is specific.

2-week plan

• Days 1-4: Aptitude daily, timed, plus SQL drills.
• Days 5-8: Fundamentals one-liners plus two case scenarios narrated aloud.
• Days 9-11: STAR stories written, then rehearsed until they are 90 seconds and natural.
• Days 12-14: Two full mocks, resume and values review.

2-day crash plan

• Day 1: Two timed aptitude sections, 15 SQL queries, memorize the OOP and DBMS one-liners, skim KPMG's five values.
• Day 2: Write 5 STAR stories, rehearse a case out loud twice, prepare 3 questions to ask, and confirm logistics and your test setup (camera, mic, stable connection, a quiet room).

8Why people get rejected at KPMG India#

The six failure modes, in the order they actually cost people offers.

1. Failed the aptitude gate. Treated the online test as a warm-up, got stuck on one hard question, ran out of time with easy points unanswered. It is the real filter, and most rejections never make it past here.
2. Resume skills they could not defend. Listed SAP, Azure, or ML and froze on the first real follow-up. List only what you can discuss three questions deep. A short honest resume beats a padded one that collapses live.
3. Answered like a coder, not a consultant. Jumped straight to a solution without clarifying the problem or framing the business impact. The interviewer cannot tell a client-ready consultant from a heads-down engineer this way, so they pass.
4. Weak communication. Mumbled, over-used jargon, or could not explain a technical choice to a non-technical interviewer in plain words. Translate or lose them.
5. No structure in the case round. Rambled instead of using buckets, so the interviewer lost the thread and could not grade the reasoning.
6. Flat HR round. No questions at the end, no genuine "why KPMG," no story that actually showed integrity or teamwork. A flat close undoes three strong rounds.

The assessment filters the pile; the case round picks the hire; the partner round confirms it. Prepare in that order.

9The offer, comp & negotiation#

For early-career tech-consulting roles in India, total compensation typically lands in the ₹7-14 LPA range, built from a fixed base, a performance-linked variable or bonus, and sometimes a joining bonus or retention component.

• Niche skills (cloud architecture, specialized ERP, data engineering) and higher levels push the number up.
• Experienced hires are banded by level and skill scarcity, not a fixed fresher scale.
• The same title can mean very different numbers depending on the practice and your leverage.

Negotiation tips for KPMG's context:

• Anchor on a competing offer or a documented current CTC. Services firms respond to concrete market data far more than to a number you simply want. "I have an offer at X" moves a band; "I was hoping for X" rarely does.
• If base is capped by the band, negotiate the joining bonus, variable target, or an early six-month review instead. These levers are often more flexible than fixed pay, which is tied to a grade.
• Weigh level and project allocation, not just base. In consulting, the practice you join and the clients you get shape your growth and your next two raises more than a small base difference. Ask directly what you would be staffed on and which practice you are landing in.

10FAQ#

Want this turned into a personalized, dated prep plan around your interview date and your specific track? Map your target date backward from here and start with whichever section above is your weakest, because that is the one that decides the loop.