PwC Data Scientist interview typically runs 2 rounds: an HR screening and a technical/business case interview with the hiring manager. The process takes about two weeks and is notably consulting-focused, emphasizing business case analysis over algorithmic coding.
$119K
Avg. Base Comp
$210K
Avg. Total Comp
2-3
Typical Rounds
2-3 weeks
Process Length
What strikes us most across PwC data scientist experiences is how consistently the process skews toward consulting-style evaluation rather than anything resembling a LeetCode screen. Multiple candidates reported that the centerpiece of their process was a business case — one involved analyzing a data acquisition process for an advertising company, another was a full group case with a live presentation to managers. The message is clear: PwC wants to see how you structure ambiguity, not just whether you can code.
A recurring theme is the expectation that candidates can move fluidly between technical depth and business communication. One candidate noted the interviewer was especially interested in how GenAI ideas had been applied in practice — RAG pipelines, prompt engineering, LLM integration — but always in the context of solving a real problem. Another flagged that the technical follow-up was specifically about tools they had mentioned, meaning vague name-dropping will backfire. If you claim SQL or Power BI, expect to be pressed on specifics. The soft-skills dimension is also more prominent here than at most data science shops — questions about conflict, teamwork, diversity, and even "what gets you up in the morning" appeared across multiple rounds.
The candidate who declined the offer described the process as professional and well-aligned with the role, which tells us something important: PwC's bar isn't arbitrary. It reflects what the job actually demands — client-facing communication, structured reasoning under pressure, and the ability to translate messy business problems into analytical ones. Candidates who treat this like a standard ML interview tend to struggle.
Synthetized from 3 candidates 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 that the conversation stayed very business-focused rather than turning into a pure coding screen. I was asked to walk through how I usually start by understanding a stakeholder’s problem and translating it into an analytical use case, so I spent a lot of time talking about how I frame business questions before jumping into modeling. From there, the discussion moved into my hands-on work with data preprocessing, feature engineering, and building models in Python and SQL. I also talked through the machine learning methods I’ve used, including regression, classification, and boosting, and then shifted into a few examples from deep learning work for NLP. The interviewer seemed especially interested in how I’ve applied newer GenAI ideas in practice, so I discussed prompt engineering and a RAG-based solution where we integrated LLMs with vector databases to improve response accuracy. I also mentioned collaborating closely with DevOps, since that came up as part of how I’ve worked across teams.
Overall, it felt like they were evaluating whether I could connect technical work to real business impact and communicate that clearly to non-technical stakeholders. It wasn’t framed as a hard algorithmic interview, but it did require being precise about the kinds of problems I’ve solved and the tools I used. I didn’t get an offer, so for me the main takeaway was that this process rewarded candidates who can speak comfortably about the end-to-end workflow, not just modeling in isolation. If I were doing it again, I’d be ready to explain concrete examples of how I’ve taken a business problem from scoping through deployment or handoff, especially where Python, SQL, and GenAI all played a role.
Prep tip from this candidate
Be ready to explain how you turn stakeholder problems into analytical use cases, then tie that directly to examples of preprocessing, feature engineering, and model building in Python and SQL. It also helps to have a concrete RAG or prompt-engineering project ready, since GenAI use cases came up alongside collaboration with DevOps.
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
How would you assess the validity of the result?
| Question | |
|---|---|
| Slow SQL Query | |
| Data Preparation for Imbalanced Data | |
| Overfit Avoidance | |
| Electricity Supply | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| User Journey Analysis | |
| Clustering Basketball Players | |
| Third Party Ad Pricing | |
| Feedback Sentiment Analysis | |
| 2nd Highest Salary | |
| Raining in Seattle | |
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| Revenue Retention | |
| Using R Squared | |
| Cyclic Detection | |
| Assumptions of Linear Regression | |
| Sort Strings | |
| Precision and Recall | |
| Missing Housing Data | |
| Find Duplicate Numbers in a List | |
| Classification and Regression | |
| Forecasting New Year Revenue | |
| Spam Classifier | |
| Bias vs. Variance Tradeoff | |
| FAQ Matching | |
| Multicollinearity in Regression | |
| Late Deliveries |
Synthesized from candidate reports. Individual experiences may vary.
An initial phone call with HR to confirm interest, schedule next steps, and conduct a basic background and fit check. This round is largely administrative and does not involve technical questions.
Candidates work through a business case in a group setting, then prepare and deliver a structured presentation to managers. This round closely mirrors a real client-style working session and evaluates problem structuring, communication under pressure, and business thinking.
A combined technical and behavioral interview with a hiring manager, often someone already met during the case round. Topics include hands-on experience with SQL, Python, Power BI, machine learning methods, and GenAI tools like RAG and prompt engineering, alongside soft-skill questions on teamwork, conflict resolution, and motivation.