HR interview questions
Common PwC HR questions, sample answer frames, and STAR tips.
PwC Interview Experiences
How PwC fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
PwC placement process in 2026 (from student reports) 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 application to offer.
Eligibility (from student reports): 6.0 CGPA throughout (10th, 12th, graduation).
Fresher package ballpark (from student reports): Analyst/Associate: ₹6-10 LPA. Confirm on your offer letter.
Round-wise process
Section titled “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
Section titled “Real interview experiences”These are condensed from public candidate write-ups, not composites. PwC’s fresher loop is notably lighter on DSA than product-company loops - most reported drives have no coding round at all, and the aptitude test is the main filter.
Experience 1: Technology Consultant, on-campus (GeeksforGeeks write-up)
Section titled “Experience 1: Technology Consultant, on-campus (GeeksforGeeks write-up)”Reported background: Non-CS/IT branch student, comfortable with Python, C++ and SQL.
Round 1 - Assessment test (45 min)
- 45 questions, 15 each from Quantitative Aptitude, Logical Reasoning and General English.
- Marking was +1 / -0.25, so blind guessing hurt. No coding section.
Round 2 - Technical interview (~30 min)
- Python dictionaries; SQL joins.
- Write bubble sort in C++; sort an array in Python without using built-in functions.
- “Why do you want to join PwC?”
Round 3 - HR (~10 min) and Round 4 - Partner round
- HR was short: introduce yourself, what do you know about PwC, have you read the JD, expected compensation.
- The partner round was a conversation about education, family background and career aspirations rather than a test.
Outcome: Selected. This candidate reported being told that once you clear the technical interview you are close to 90-95% of the final selection - the later rounds eliminated very few people.
Experience 2: PwC Acceleration Centre, on-campus 2022 (GeeksforGeeks write-up)
Section titled “Experience 2: PwC Acceleration Centre, on-campus 2022 (GeeksforGeeks write-up)”Round 1 - Aptitude + MS Excel
- MCQs on quantitative aptitude, English, and basic MS-Excel operations. No negative marking.
- The candidate rated the questions as conceptually basic but “very tricky”, and recommended timed aptitude practice.
Round 2 - Combined technical + HR (15-20 min)
- Two interviewers, both managerial-level with 10+ years of experience.
- Introduce yourself; walk through your project (a machine learning project here).
- Difference between machine learning and deep learning; advantages and disadvantages of cloud computing.
- Why PwC?
Outcome: Selected; the result mail came from the college placement cell the next day.
What both accounts share: the aptitude test is the real filter, the technical round is a resume-and-fundamentals conversation rather than a whiteboard grind, and being able to explain your own project plainly matters more than DSA depth. Group Discussion appears in some drives but not all - one reported GD topic was the pros and cons of a 70-hour work week.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Simple array or string warm-up. Usually expects two pointers / hashing
- SQL joins and aggregations. Usually expects GROUP BY, window functions
- OOPs design for a small system (ATM / library). Usually expects classes and relationships
- Discussion on SQL and logic, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why consulting?
- A client-facing or communication example
- Willingness to travel
- A time you influenced a decision
Practical tips for PwC
Section titled “Practical tips for PwC”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain SQL in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of PwC panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, PwC usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.