Candidates for McKesson Product Manager roles describe recruiter and hiring manager conversations, then a team interview, a four-hour panel, or a full onsite day, with questions on resume detail, EMR experience, stakeholders and prioritization.
$126K
Avg. Base Comp
$158K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
McKesson Product Manager interviews, as three candidates describe them, reward specific, resume-grounded stories and healthcare product judgment. Each account began with a conversation with a recruiter or hiring manager, and the later stages differed: one candidate sat a panel of about four hours, another did five onsite sessions across a full day, and a third, who came through a staffing agency, finished with a team-member interview within a single day.
The questions were practical rather than technical. The panel candidate was pressed with detailed follow-ups on specific experiences and worked through a resource allocation scenario: two stakeholders wanted different features on different products, and there was budget and IT bandwidth for only one. The onsite candidate was asked about EMR-specific experience, working with difficult stakeholders, and how to improve a struggling product. The staffing-agency candidate was asked about handling conflict of interest issues, which that candidate read as pointing to the compliance side of the job.
The tone was friendly in each account, though not always polished. One recruiter screen felt scripted, and the team-member interview in another process followed a standard list of questions. Come with a few STAR-format examples, a clear way to explain prioritization trade-offs such as business impact, technical feasibility and shared dependencies, and a genuine reason healthcare technology interests you.
Synthesized from 5 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 Mckesson process.
{"experience":"I applied through LinkedIn and the first thing that stood out was how messy the scheduling was. I had a recruiter screening set up, but the recruiter never showed up, so I had to email the recruiting coordinator to get it rescheduled. Once it finally happened, the screen was pretty straightforward and mostly focused on my background and why I was interested in McKesson. The recruiter also spent time walking through benefits, the job description, and the company culture, which made it feel more like an early fit check than a deep evaluation. One of the main questions was simply what I knew about McKesson, so it helped to have a basic understanding of the business and why the role made sense for me. After that, I was told I’d move on to the hiring manager. That conversation was better and felt more like a real PM interview. It was a standard situational and behavioral round, and the hiring manager was very nice and easy to talk to. We covered my background and how I’d handle different product scenarios, but nothing overly technical or case-heavy. I was told there was a company meeting the following week and that I should hear back after that, but then I heard nothing for a few weeks. I followed up with the recruiting coordinator and even messaged the hiring manager on LinkedIn, but got no response from either. Overall the process was pretty light on technical depth, but the communication was frustrating and I ended up being completely ghosted. My main takeaway is to be ready to explain your background clearly, know why you want McKesson, and expect a very standard behavioral PM screen rather than anything highly structured. outcome":"No offer outcome_color":"red prep_tip":"Be ready to answer a simple but direct question about what you know about McKesson, and have a concise explanation for why the role fits your background. The hiring manager round sounded like standard PM situational and behavioral questions, so prepare a few examples that show how you handle product decisions and stakeholder situations."}
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 Mckesson
How would you answer when an Interviewer asks why you applied to their company?
| Question | |
|---|---|
| Debug Marriage Data | |
| Empty Neighborhoods | |
| Experiment Validity | |
| 2nd Highest Salary | |
| Button AB Test | |
| Hurdles In Data Projects | |
| Cumulative Distribution | |
| Size of Joins | |
| Instagram TV Success | |
| Group Success | |
| Last Transaction | |
| Always Excited Users | |
| Flight Records | |
| Google Maps Improvement | |
| Causal Email Journey | |
| Retailer Data Warehouse | |
| Job Recommendation | |
| Total Spent on Products | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| RMS Error | |
| Brain Cancer Treatment Outcomes | |
| Testing Price Increase | |
| Cumulative Reset | |
| Customer Success vs. Free Trial | |
| Detecting ECG Tachycardia Runs | |
| Success Measurement | |
| Slow SQL Query | |
| Random Forest Explanation |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates describe starting with a recruiter phone screen. One found it scripted, with a recruiter who did not seem familiar with the Product Manager role, and said the next phone interview with someone who knew the position was more substantive. A candidate who applied through a staffing agency instead had an initial conversation with the hiring manager, who had clearly read the resume closely.
Hiring manager calls were conversational. One candidate was asked how they would work with difficult stakeholders, whether they had EMR-specific experience, and how they would improve a struggling product. Another reported a fast-paced call that moved quickly and was built around resume detail. Prepare concrete examples of decisions you drove and be ready to explain your reasoning.
The staffing-agency candidate had a second interview with a team member that felt less polished, with questions read from a standard list. One asked about experience handling conflict of interest issues, which that candidate saw as specific to the compliance side of product management. This candidate's whole process wrapped up in one day.
Two candidates describe a longer final stage. One had an in-person panel of about four hours, with each panelist focused on a different skill set and detailed resume follow-ups, plus a resource allocation scenario. The other had five onsite sessions of 45 to 60 minutes, each with two interviewers, over a full day. Both described the interviewers as friendly and collaborative.
