
PwC Data Analyst interviews reported here combine motivation and behavioral conversations with variable assessments, cases, and role-specific technical discussion such as SQL, database design, or business analysis.
$102K
Avg. Base Comp
$115K
Avg. Total Comp
2-4 rounds
Typical Rounds
4-4 weeks
Process Length
PwC Data Analyst candidates should prepare for a process that can test both communication and applied analytical judgment. Across the reports, motivation and behavioral answers recur more consistently than one universal technical screen: candidates were asked why PwC, why the role, to walk through their background, and to discuss teamwork, conflict, leadership, or achievements. Have concise examples that connect your experience to the position rather than relying on a generic company answer.
Technical content varies materially by team. One candidate described SQL written for a logistics scenario and a database-design discussion. Other reports instead centered on audit or accounting fundamentals, or a business case involving fluctuation analysis. Prepare to explain your reasoning aloud, state assumptions, and turn analysis into a clear business recommendation.
Several candidates also encountered assessments or group formats, including numerical and logical reasoning, abstract figure rotations, language exercises, and collaborative case work. Practice communicating a structured approach under pressure and contributing clearly in a group. Because reports differ by role and location, expect the mix of technical, case, and assessment elements to vary.
Synthesized from 11 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Pwc process.
What stood out to me most was how much PwC cared about communication and fit, not just technical knowledge. My process had four stages. The first interview was mostly motivational: why I applied, why PwC, and why this firm instead of the other Big Four. That part felt very conversational, but they definitely wanted a clear answer on what differentiated PwC in my mind. The second round was a case interview, and that was the toughest part for me. I got a Fermi-style estimation case where I had to estimate the number of Netflix users, then talk through how I’d use that kind of thinking to increase sales. It was less about getting a perfect number and more about structuring the problem and explaining my reasoning out loud.
The later rounds leaned more into skills and personality. There were questions around basic data practices like EDA, data modeling, and machine learning models, but the biggest emphasis was on how I would present findings to a team or stakeholders. They also brought up Python, SQL, and R, with a lot of attention on Python libraries since those seemed especially important for the role. In the more senior conversation, the tone was very conversational and behavioral, and I was expected to answer from recent experience, including situations from the last 12 months. That round also included a tour of the office, which made the process feel more personal and formal at the same time. Overall it was a difficult process and I didn’t get the offer, but the main takeaway was that PwC wanted someone who could think clearly, explain tradeoffs, and handle stakeholder-facing discussions as much as someone who could do the technical work.
Prep tip from this candidate
Practice a clean Fermi estimation framework and be ready to explain how you’d turn an estimate into a sales or business recommendation. Also prepare recent behavioral stories from the last 12 months, since the interviewers seemed to probe for concrete examples of leadership, challenge, and stakeholder communication.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Pwc
Write a query to return the two students with the closest test scores and the score difference
| Question | |
|---|---|
| Experiment Validity | |
| Size of Joins | |
| Sort Strings | |
| Hurdles In Data Projects | |
| RAG Strict Source Control | |
| Slow SQL Query | |
| Data Pipelines and Aggregation | |
| Data Preparation for Imbalanced Data | |
| Overfit Avoidance | |
| Company Acquisition Choice | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| User Journey Analysis | |
| Data Cleaning Experiences | |
| Clustering Basketball Players | |
| Feedback Sentiment Analysis | |
| Creating Companies Table | |
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Longest Streak Users | |
| Top 3 Users | |
| Raining in Seattle | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Revenue Retention | |
| P-value to a Layman | |
| Normalize Grades | |
| Fair Coin | |
| Using R Squared |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report HR or initial conversations focused on why PwC, why the specific role, prior experience, achievements, and professional goals. These discussions were often described as friendly or conversational, but clear and specific explanations of motivation were still expected.
Some candidates report numerical and logical reasoning, abstract figure-rotation exercises, language or English tests, competency tests, or timed video answers. These elements are not universal, but they suggest practicing concise reasoning and calm communication under a time limit.
Reported technical content ranges from SQL and database design to estimation, data practices, audit fundamentals, SAP, accounting standards, or a business case. Candidates may be asked to explain assumptions, write or discuss an approach, and translate analysis into a recommendation.
Candidates report later conversations with managers, directors, or partners that probe teamwork, conflict, leadership, stakeholder communication, pressure, and role fit. One report described a partner and manager as back-to-back conversations, while another described a final partner round.