What to expect in a McKesson Business Analyst interview: a phone screen, a hiring-manager conversation and a virtual panel, with behavioral questions about past projects. Includes pay estimates and prep tips.
$118K
Avg. Base Comp
$140K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
One McKesson business systems analyst candidate described a three-stage process: a 30-minute phone screen, an hour-long Zoom conversation with the hiring manager, and a virtual panel with four team members. That candidate, who received an offer, said the screen centered on walking through their experience against the job description.
The hiring-manager round was where the questions got substantive. The candidate was asked to describe a difficult project they had managed and how they navigated the challenges. They said the interviewer cared more about their problem-solving approach and how they handle adversity than about a single right answer.
A second candidate, who interviewed for a consultant role and also received an offer, described a recruiter screen followed by several conversations with managers and senior leaders. Most questions were behavioral, framed as "Tell me about a time when...". One round included a basic analytical scenario: building a staffing plan and then adding shrinkage factors. That candidate called the process slow and somewhat repetitive across interviewers.
The practical takeaway is to prepare two or three project stories with clear context, obstacles, your decisions and what you learned. Be ready to explain your reasoning aloud, and to refresh simple planning arithmetic. Both candidates said team fit mattered, so expect to be assessed on how you collaborate as well as on your analysis. Only a small number of reports exist, so treat the round order as one candidate's path rather than a fixed format.
Synthesized from 3 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.
I had a screening call with a recruiting agency a couple of weeks before my interview with the hiring manager for a three-month contractor role with conversion potential to FTE. Going in, I was expecting a straightforward conversation about the role and expectations, but things quickly felt off.
From the first five minutes, it was clear the hiring manager struggled to be concise. He spoke rapidly and with a lot of unnecessary detail about what he was looking for, which made the conversation uncomfortable. He asked about my software training experience, but his responses to my questions were so verbose and tangential that I couldn't get a clear picture of what I'd actually be doing. He'd promised me ten minutes to ask questions, but by the time he finished answering my one question with four minutes of rambling information, I barely had any time left. What struck me most was that despite all that talking, he never clearly described the deliverables I'd be expected to complete in the three-month window. It felt like he didn't have a concrete plan for how to use me.
The whole thing raised red flags. The pay rate didn't match the skills and responsibilities he was describing, and the job description bore little resemblance to what he was actually asking for. When he casually mentioned that another team member was leaving for reasons he couldn't quite articulate, that sealed it for me. After reflecting on the call, I realized this looked like an order-taker role with no realistic expectations on workload and a manager who didn't know how to lead. I withdrew my application.
Prep tip from this candidate
If a hiring manager can't clearly articulate deliverables or seems unprepared for the conversation, that's a genuine warning sign about management and project clarity—not a reflection on you. Trust that instinct before committing time to the rest of the process.
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 | |
| 2nd Highest Salary | |
| Cumulative Distribution | |
| Button AB Test | |
| Prime to N | |
| Experiment Validity | |
| Retailer Data Warehouse | |
| Hurdles In Data Projects | |
| Total Spent on Products | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Size of Joins | |
| Brain Cancer Treatment Outcomes | |
| Cumulative Reset | |
| Fair Coin | |
| Last Transaction | |
| Always Excited Users | |
| Flight Records | |
| Google Maps Improvement | |
| Promoting Instagram | |
| Sort Strings | |
| Testing Price Increase | |
| Percentage of Revenue by Year | |
| Assumptions of Linear Regression | |
| Instagram TV Success | |
| Detecting ECG Tachycardia Runs | |
| Group Success | |
| Success Measurement |
Synthesized from candidate reports. Individual experiences may vary.
One Business Systems Analyst candidate reports a 30-minute phone screen that felt conversational. The interviewer asked them to walk through their professional experience and how it matched the job description. A consultant candidate also describes a recruiter screen first, so a short intro call is likely, though its content may vary.
The Business Systems Analyst candidate reports a one-on-one Zoom meeting with the hiring manager lasting about an hour. They were asked to describe a difficult project they had managed and how they handled its challenges. They felt the focus was on problem-solving approach and adversity rather than a single correct answer.
The same candidate reports a final virtual panel with four team members. Candidates may find the panel collaborative in tone, as this one did, and an earlier conversation helped them tailor answers to team priorities. The consultant candidate also met several leaders, so other rounds with managers or senior staff are possible, with overlapping questions.
Candidates report mostly behavioral questions, such as "Tell me about a time when...", with interviewers probing reasoning and team fit. One consultant candidate also saw a basic analytical scenario about a staffing plan with shrinkage factors. Technical depth was described as light, but this rests on limited reports.
