Interview experience
PwC Interview Questions and Answers (2026)
Overview
Section titled “Overview”PwC Acceleration Centers (AC, PwC’s technology delivery hubs and the entry point for most CS/IT campus hires) run a 3-5 stage process - aptitude screening, sometimes a Hackathon, resume-heavy technical interviews, and a closing HR round - though some pipelines stretch into a months-long Launchpad training program before interviews even begin.
PwC interview process at a glance
Section titled “PwC interview process at a glance”| Round | Duration | What they test |
|---|---|---|
| Online Aptitude Test | 60-90 min | Quant, logical, verbal |
| Hackathon (select drives) | Multiple hours, multi-stage | Building/solving under pressure, technical depth |
| Technical Interview(s) | 30-45 min each | Resume/project depth, SQL, OOPs, problem-solving |
| HR Interview | 20-30 min | Communication, client readiness, fit |
Online Aptitude Test
Section titled “Online Aptitude Test”A standard aptitude screen on quantitative, logical, and verbal ability. On some 2025-cycle drives, this was replaced or preceded by PwC’s Launchpad program - three online exams used for initial shortlisting before months of training even began.
Common questions
- Quant: percentages, ratios, time-and-work
- Logical reasoning and data interpretation
- Verbal ability: comprehension, grammar
Hackathon (select drives)
Section titled “Hackathon (select drives)”Run on some PwC AC drives after initial screening - a multi-hour event (reported as roughly 3 hours with 9 stages on one drive) that candidates and reports describe as genuinely tough, testing both building something functional and solving problems under time pressure.
Common questions
- Build/solve a multi-stage technical challenge under a hard time limit
- Debug or extend a partially-built system within the event
- Present or defend your solution choices to evaluators
Round-by-round breakdowns are on the PwC interview experience page.
Technical Interview(s)
Section titled “Technical Interview(s)”Mostly resume-based - interviewers dig into your project’s stack, architecture, and failure modes, with difficulty varying noticeably by candidate. Some drives run one round online and a second in-person on campus.
Common questions
- Walk through your project’s architecture, stack choices, and the hardest bug you fixed
- SQL joins and aggregation on a sample schema
- OOPs concepts - explain with a small system design (ATM/library)
- General problem-solving on an ambiguous, open-ended scenario
- What would you change if you rebuilt this project today?
HR Interview
Section titled “HR Interview”Checks communication skills, motivation for PwC, and client-readiness - standard consulting-fit territory, usually the final gate before an offer.
Common questions
- Tell me about yourself and why PwC
- Describe a time you had to explain a complex issue to someone without a technical or financial background
- How do you stay current with changing regulations, technology, or industry trends relevant to your role?
- A time you worked under a hard deadline - how did you manage it?
- Are you comfortable with the location and shift PwC AC has offered you?
Sample answer frameworks for each of these are on the PwC HR interview questions page.
Audit/Tax vs AC/Technology: why the track matters
Section titled “Audit/Tax vs AC/Technology: why the track matters”PwC hires across genuinely different business lines - Audit & Assurance, Tax, Advisory/Consulting, and Acceleration Centers (AC, the technology delivery hubs doing actual software, data, and analytics work). This page describes the AC/technology track most CS/IT campus hires enter: aptitude screening, sometimes a Hackathon, a resume-heavy technical interview, and HR. Audit and Tax hiring, aimed largely at commerce and accounting graduates, runs a lighter process built around aptitude, group discussion, and HR, with no coding or Hackathon component. Confirm which business line your offer letter or registration email names before you prep.
Common technical interview questions and answers
Section titled “Common technical interview questions and answers”Q: Explain the difference between INNER JOIN, LEFT JOIN, and FULL OUTER JOIN.
INNER JOIN returns only the rows where the join condition matches on both sides, so unmatched rows vanish from the result. LEFT JOIN returns every row from the left table, filling the right table’s columns with NULL where there is no match - this is how you find customers with no orders, by adding WHERE o.order_id IS NULL. FULL OUTER JOIN returns all rows from both tables, padding with NULL on whichever side is missing. The classic mistake PwC interviewers watch for: placing a filter on the right table in the WHERE clause of a LEFT JOIN silently turns it into an INNER JOIN, because NULL fails any comparison - that condition belongs in the ON clause instead.
Q: Write a SQL query showing total revenue per region, only for regions above a threshold.
Use GROUP BY for the aggregation and HAVING for the post-aggregation filter: SELECT r.region_name, SUM(o.amount) AS total_revenue FROM orders o JOIN regions r ON o.region_id = r.region_id WHERE o.status = 'COMPLETED' GROUP BY r.region_name HAVING SUM(o.amount) > 100000 ORDER BY total_revenue DESC; The distinction interviewers test is that WHERE filters individual rows before grouping while HAVING filters the grouped results afterwards, so a condition on SUM cannot go in WHERE. Filtering on status inside WHERE is deliberate - it removes cancelled orders before they ever reach the aggregate.
Q: What is the difference between WHERE and HAVING, and between DELETE, TRUNCATE, and DROP?
WHERE filters rows before grouping and cannot reference aggregate functions; HAVING filters after grouping and is where aggregate conditions belong. DELETE removes rows one at a time, can carry a WHERE clause, fires triggers, and is fully logged so it can be rolled back within a transaction. TRUNCATE removes all rows by deallocating data pages, so it is far faster but takes no WHERE clause, generally does not fire row triggers, and resets identity counters - it is DDL, so on many engines it also implicitly commits. DROP removes the table structure itself along with its data, indexes, and constraints. The safe mental model: DELETE for selective removal inside a transaction, TRUNCATE for a fast full reset of a table you intend to keep, DROP when the table should stop existing.
Q: Explain the four OOPs concepts using an ATM or library system.
Encapsulation: an Account class holds balance as a private field and exposes only withdraw() and deposit(), so no external code can set a balance directly and skip the overdraft check. Abstraction: the ATM interface offers withdrawCash() while hiding the card authentication, bank network call, and cash dispenser mechanics behind it. Inheritance: SavingsAccount and CurrentAccount both extend Account, inheriting balance handling while overriding interest and overdraft rules. Polymorphism: the ATM holds a reference of type Account and calls withdraw(), and the runtime dispatches to the correct subclass implementation - meaning a new account type can be added without touching the ATM code at all. That last point, extensibility, is what makes the answer land rather than just the definitions.
Q: What is database normalization, and when would you deliberately denormalize?
Normalization structures tables to remove redundancy and the insert, update, and delete anomalies it causes. 1NF requires atomic column values with no repeating groups; 2NF additionally requires every non-key attribute to depend on the whole composite key, not just part of it; 3NF removes transitive dependencies, so a non-key column must not determine another non-key column. You would deliberately denormalize in reporting and analytics workloads - a star schema with a wide fact table and dimension tables avoids joining a dozen normalized tables for every dashboard query. The trade-off is explicit: normalized schemas optimise for write correctness, denormalized ones for read speed, and you accept the redundancy because the reporting layer is refreshed from a controlled ETL rather than edited by users.
Q: How would you approach an ambiguous, open-ended client problem?
Start by clarifying scope and success criteria rather than solving immediately - ask who the users are, what the current process costs in time or money, and what a good outcome looks like in measurable terms. Then structure the problem into mutually exclusive parts, for example splitting data quality, process automation, and reporting, so the analysis is exhaustive rather than a list of whatever occurred to you first. State your assumptions out loud and label them as assumptions, because in a consulting setting an unstated assumption is the thing that derails a deliverable three weeks later. Close with a prioritised recommendation and what you would need to validate it. PwC scores the structure of your reasoning here far more than the specific answer.
Q: Walk me through your project’s architecture and the hardest bug you fixed.
Describe it as data flow rather than a technology list: what enters the system, which components transform it, where it is stored, and what the user finally sees - then name the stack and, crucially, why you picked it over the alternative you considered. For the bug, give the symptom, how you narrowed it down, the root cause, the fix, and how you verified it did not recur; the diagnostic method matters more than the bug’s difficulty. Be honest about what you would rebuild differently, since PwC’s technical rounds are heavily resume-driven and interviewers deliberately push on vague claims until they find the edge of your actual knowledge. Owning a limitation reads as credibility, whereas overclaiming a component a teammate built is the fastest way to lose the room.
Q: How would you handle confidential client data on an engagement?
Work from least-privilege access: request only the fields the analysis actually requires, and never take a full production extract when a filtered subset will do. Keep client data inside approved firm systems rather than personal drives, email, or external AI tools - PwC assessments and engagements typically bar GenAI tools outright, and pasting client data into one is a disclosure event, not a shortcut. Use masked or synthetic data in development and testing environments, and ensure anything shared externally is anonymised and reviewed. If you ever discover data you should not have access to, escalate it immediately rather than quietly deleting it, because the reporting obligation is the part the firm is actually testing for.
Frequently asked questions about PwC interviews
Section titled “Frequently asked questions about PwC interviews”What is the PwC interview process for freshers?
For PwC Acceleration Centers (AC, PwC’s technology delivery hubs and the entry point for most CS/IT campus hires), the process runs 3-5 stages depending on the drive: 1. Online screening tests - aptitude plus, on some drives, a multi-month Launchpad training-and-assessment program with recurring exams. 2. A Hackathon round on select drives - multi-hour, multi-stage, genuinely hard. 3. Technical Interview(s) (online or in-person) - mostly resume-based, difficulty varies by candidate. 4. HR Interview - motivation, fit, communication. Total duration: 2-3 weeks for a standard drive, months for a Launchpad-style pipeline.
What questions are asked in PwC interviews?
Standard-drive OAs cover quant, logical, and verbal aptitude. Where a Hackathon is run, expect a multi-hour, multi-stage build-and-solve format that’s explicitly described as tough. Technical interviews are largely resume-driven - your project’s architecture, decisions, and failure modes - plus SQL, OOPs, and general problem-solving. HR checks client-communication skills and motivation for PwC.
How many rounds are there in the PwC interview?
PwC typically runs an Online Aptitude Test, a Technical Interview (sometimes two - one online, one in-person), and an HR Interview - 3-4 stages for a standard AC drive. Select drives add a Hackathon round after initial screening, and some 2025 pipelines ran a months-long Launchpad training program before interviews even started.
How should I prepare for PwC interviews?
Practise timed aptitude and one project narrative you can defend under close questioning - PwC technical interviews are heavily resume-based, so vague project claims get picked apart. If your drive includes a Hackathon, practise building something functional under a hard multi-hour deadline, not just solving isolated problems. Use STAR for HR answers, and note GenAI tools are typically barred during assessments and interviews.
What is PwC Acceleration Center, and is the interview different from Audit or Tax roles?
PwC Acceleration Centers (AC) are PwC’s technology and delivery hubs in India - it’s what this page’s process describes: aptitude screening, sometimes a Hackathon, a resume-heavy technical interview, and HR. PwC’s core Audit, Tax, and Assurance hiring runs a separate, largely non-coding process built around aptitude, group discussion, and HR, aimed mainly at commerce/accounting graduates.
What is PwC’s Launchpad program?
A structured pipeline PwC ran starting January 2025: online exams for initial shortlisting, then months of online classes and technical training with recurring qualifying exams (candidates who failed to keep qualifying were eliminated along the way), followed by a Hackathon and Technical/HR interview rounds for those who made it through. It’s a longer, training-heavy alternative to a standard multi-round campus drive - not every PwC AC drive runs this format.