What questions are asked in PwC interviews?

PwC interviews commonly cover DSA coding (Basic array / string manipulation; SQL joins and aggregation), core CS (OOPs, DBMS/SQL, OS basics where relevant), project discussion, and topics tied to the business such as SQL, logic, case. Behavioural questions check ownership, teamwork, and why PwC.

How many rounds are there in the PwC interview?

PwC typically has 4 stages: Online Aptitude Test (60–90 min), Group Discussion (if conducted) (20–30 min), Technical Interview (30–45 min), HR Interview (20–30 min). Some drives skip GD or merge HR with managerial. Always check the mailer for that cycle.

How should I prepare for PwC interviews?

For PwC, prioritise DSA practice with timed mocks, revise OOPs and SQL, prepare a crisp project narrative, and read up on SQL and logic. Use STAR for behavioural answers and ask one thoughtful question at the end.

PwC Interview Experience 2025–2026 — Real Candidate Stories

PwC interview experience

These write-ups reflect how PwC fresher interviews usually go — campus and off-campus. Patterns shift by year and role, so use this as a prep map, not a script.

PwC placement process in 2026 (candidate-reported) includes: 1. Online Aptitude Test (60-90 minutes) — Quantitative aptitude, logical reasoning, verbal ability. 2. Group Discussion (20-30 minutes) — Current affairs and business topics. 3. Technical Interview (30-45 minutes) — Domain knowledge and problem-solving. 4. HR Interview (20-30 minutes) — Motivation, teamwork, and company fit. Total duration: 2-3 weeks from…

Most drives expect a clean academic record (often around 6.0–6.5+ CGPA with no active backlogs). Candidate-reported detail: PwC eligibility criteria for freshers 2026 (candidate-reported) include: Degree required: B.Tech/B.E./M.Tech/MCA/MBA in any discipline. Batch: Final year students and recent graduates. Academic Record: Typically 60% or…

Fresher offers (candidate-reported) often land around andidate-reported): Analyst/Associate: ₹6-10 LPA (CTC, including base salary and benefits). The compensation. Treat numbers as directional — confirm on your offer letter.

Round-wise process

Round	Duration	What they test
Online Aptitude Test	60–90 min	Quant, logical, verbal
Group Discussion (if conducted)	20–30 min	Current affairs / business topic
Technical Interview	30–45 min	SQL, OOPs, projects, basics
HR Interview	20–30 min	Communication, client readiness

Real interview experiences

Experience 1: Analyst / Technology Consultant (2025)

Profile: B.Tech CSE, 7.8–8.4 CGPA, tier-2 college, 1 internship, decent DSA practice (150+ problems)

Online / written round

Focus stayed on problem-solving speed and clean code, not trick questions.
Cleared with full or near-full test cases; shortlist mail came in a few days.

Technical rounds

Coding: Basic array / string manipulation — approach used: two pointers. Interviewer cared about complexity and edge cases.
Follow-up coding: SQL joins and aggregation — GROUP BY, window functions.
Domain discussion around SQL and logic — they wanted practical trade-offs, not buzzwords.
Project deep dive: why you chose the stack, what broke in production/testing, what you would redo.

HR / managerial

Why consulting?
Client-facing communication example
Keep answers short and specific. Name the conflict, what you did, and the result.

Result: Selected What helped: Explaining approach before coding, admitting unknowns early, and linking project work to PwC’s domain (SQL).

Experience 2: Analyst / Technology Consultant (2024–2025)

Profile: B.Tech IT / ECE, 7.2 CGPA, strong projects, average competitive programming

What differed

OA felt tougher on time; one medium-hard problem needed an optimised solution to clear the bar.
Second technical leaned more into case and system design basics (APIs, DB choice, failure modes).
Coding warm-up: Simple OOPs design for a library / ATM — classes + relationships.

Mistakes to avoid

Jumping into code without clarifying constraints
Treating HR as a formality — PwC still filters on communication and intent
Memorising system design jargon without a simple capacity / bottleneck story

Result: Selected after a managerial / HR round Takeaway: For PwC, consistent DSA plus a clear story on SQL beats a perfect CGPA with weak explanation.

Questions that come up often

Coding / technical

Basic array / string manipulation — typically expects two pointers
SQL joins and aggregation — typically expects GROUP BY, window functions
Simple OOPs design for a library / ATM — typically expects classes + relationships
Discussion on SQL and logic — capacity, failure modes, simple APIs
Project deep dive — architecture, hardest bug, what you would change

HR / behavioural

Why consulting?
Client-facing communication example
Willingness to travel
Tell me about a time you influenced a decision

Practical tips for PwC

Practise DSA under a timer. Clearing the OA matters more than polishing a perfect resume line.
For domain rounds, be ready to talk about SQL in plain language — inputs, outputs, bottlenecks.
Revise OOPs and SQL; many PwC panels still open with fundamentals.
Keep HR answers concrete. One story with a clear result beats five buzzwords.
If you do not know something, say so and outline how you would find out. Guesswork wastes the round.

PwC HR Interview Questions — common HR questions and how to answer them
PwC Preparation Guide — round-wise prep plan
PwC Coding Questions — practice problems with approaches
PwC Previous Year Papers — past papers and patterns
PwC Placement Papers — company overview, eligibility, and process

Last updated: August 2026