Pwc AI Research Scientist interview typically runs 2 rounds: TA interview, hiring manager interview. The process takes about 1-2 weeks and includes a salary discussion.
$157K
Avg. Base Comp
$173K
Avg. Total Comp
4-5
Typical Rounds
2-4 weeks
Process Length
Our candidates report that PwC’s AI Research Scientist process can feel split between two very different modes: one side is highly scripted, while the other is much more grounded and prepared. In this experience, the TA conversations came across as templated and basic, but the hiring manager had clearly reviewed the resume and asked in a way that felt more substantive. That contrast matters, because it suggests the company is not only evaluating technical background, but also whether the candidate can engage credibly with a more business-facing, consulting-style conversation.
A recurring theme is that compensation becomes part of the signal. Multiple moments in the process centered on salary expectations, and the candidate felt the target was pushed well below prior earnings. We’ve seen that kind of framing create friction fast, especially when it’s paired with heavy emphasis on benefits and insurance as a selling point. For candidates, that usually means the interview is not just about capability; it’s also a test of how flexible you are on package and how you respond when the company anchors low.
The other non-obvious factor is professionalism in the small moments. The late start and excuses from the TA, combined with the repetitive questioning, left a strong negative impression even though the hiring manager interaction was better. For us, that points to a process where candidate experience can vary sharply by interviewer, and where polish, preparation, and respectfulness are part of the evaluation whether they’re stated or not.
Synthetized from 1 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.
I applied online and the process started with an interview with a TA and the hiring manager, followed by a salary discussion. The first conversation was pretty uneven: the TA mostly asked templated, very basic questions, nothing substantial, and it felt like she was just reading from a script. It was so generic that the hiring manager actually cut her off at one point because it was dragging. In contrast, the hiring manager came across as much more professional and clearly had looked at my resume beforehand, which made that part of the conversation feel more grounded.
What stood out to me, though, was that the compensation conversation took over the process. They kept pushing salary expectations that were far below what I had been earning, and the way it was framed did not feel respectful. There was also a lot of selling around the company insurance and benefits, almost as if they were trying to make them sound unusually exceptional rather than standard. I had a second interview with the TA, and it was more of the same: still pushing the lower salary target, plus she showed up about 20 minutes late and had excuses for the delay. Overall, the process gave me a lot of red flags, and I declined the offer.
Prep tip from this candidate
Be ready for a very basic, templated screening conversation with TA and a separate salary discussion that may come early. If compensation is important to you, go in with a firm range and don’t assume the process will be focused on technical depth.
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 | |
|---|---|
| Hurdles In Data Projects | |
| Sort Strings | |
| Slow SQL Query | |
| Overfit Avoidance | |
| Data Preparation for Imbalanced Data | |
| Your Strengths and Weaknesses | |
| Data Cleaning Experiences | |
| Why Do You Want to Work With Us | |
| Clustering Basketball Players | |
| Feedback Sentiment Analysis | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Raining in Seattle | |
| Using R Squared | |
| Maximum Profit | |
| Testing Price Increase | |
| Bias vs. Variance Tradeoff | |
| Fair Coin | |
| Cyclic Detection | |
| Assumptions of Linear Regression | |
| Precision and Recall | |
| Missing Housing Data | |
| Mouse Search | |
| Find Duplicate Numbers in a List | |
| Classification and Regression | |
| Spam Classifier | |
| String Palindromes |
Synthesized from candidate reports. Individual experiences may vary.
The process begins with an online application. In this case, the candidate applied directly through PwC's careers process before being contacted for interviews.
The first interview was with a talent acquisition representative and consisted mostly of templated, basic screening questions. The conversation was fairly generic and focused on initial fit rather than deep technical evaluation.
The hiring manager joined the process early and asked more substantive questions after reviewing the candidate's resume. This conversation felt more grounded and professional than the TA screen, and it was part of the initial interview sequence.
A separate salary conversation followed, where PwC pushed for expectations below the candidate's prior compensation. The discussion also included significant emphasis on benefits and insurance as part of the overall offer pitch.
A second conversation with the TA occurred later in the process and repeated much of the earlier salary-focused discussion. The candidate reported that this stage was delayed and that the TA arrived about 20 minutes late.
The process concluded with an offer that the candidate declined due to concerns about compensation, professionalism, and the overall interview experience.