McKesson logo

McKesson Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 44 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at McKesson.

Showing 3 of 44
McKesson logo
McKesson

Software Engineer

Engineering · more than a year ago

Mid Average No offer 2 rounds
Interview process
Recruiter call Phone screen Onsite Technical screen
Interview formats
Technical Behavioral

So I applied online and a few weeks later they called me for a phone interview. We talked about my background a bit and then they asked me some easy C++ questions that got progressively harder. Eventually they were asking about compiler specific stuff related to virtual functions and v tables, and I just couldn't answer anymore. Then about a week later, I went in for an in person interview. It was about an hour long and there was a panel asking me questions about C# syntax, SQL, and database internals. I think I did okay, but I blanked on some basic C# things I don't usually think about, like they showed me some code with boxing/unboxing and I wasn't sure if it would work. After that, they said thanks and I never heard back.

Confirmed questions6 questions
  • Can you explain how inheritance is implemented in C++?
  • How does C++ implement virtual functions using v tables?
  • Describe C# syntax.
McKesson logo
McKesson

Software Engineer Intern

Engineering · more than a year ago

Intern Easy Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Offer
Interview formats
Behavioral

I gave them my resume at a college career fair. A few weeks later, I got an interview. It was mostly behavioral questions, and no tough technical questions. They asked about relocating. I said I was willing, but would prefer not to. They made accommodations and put me at a location near my home. Eventually I got a call from them wanting an in person interview at a location. However, later they said they didn't have it properly scheduled, and I got a phone interview instead. Still no real technical questions. General questions about working and skills. They took several weeks to get back to me, but eventually called and said they'd send me an offer. I accepted.

Confirmed questions2 questions
  • Are you willing to relocate?
  • Tell me about your work experience and skills.
McKesson logo
McKesson

Software Engineer

Engineering

Entry Easy Positive experience Decline offer 1 round
Interview process
Technical screen Recruiter call
Interview formats
Technical Coding

So, they brought me into a room, and the whole team was there. They asked me some questions about my resume and the projects I've worked on. They didn't really ask me a ton of questions, honestly, mostly just asked if I had any questions for them. It was all done in less than an hour. Just to clarify, I haven't accepted or declined anything yet, so the offer is still up in the air, and I have another interview coming up.

Confirmed questions1 question
  • They gave me a written SQL test with 9 questions, and I had about 20 minutes to complete as much as I could.

McKesson Software Engineer Interview Questions

Quoted word for word from McKesson interview reports.

What is the difference between an abstract class and an interface?

Read reports

Can you write a function to find the repeated number in an array of 1001 elements containing numbers from 1 to 1000?

Read reports

Could you analyze this C# code snippet involving boxing/unboxing and determine its behavior and validity?

Read report

Can you explain how inheritance is implemented in C++?

Read report

Could you explain the distinctions between an array and a linked list?

Read report

Can you explain absolute positioning in CSS and provide scenarios for its use?

Read report

How would you implement database connectivity for the bookstore application?

Read report

Formats, difficulty and experience

Across all 44 McKesson interview reports.

Interview formats

Technical 37.6%
Behavioral 32.7%
Coding 20.8%
Group 3%
System Design 3%

Interview difficulty

Easy 25%
Average 70.5%
Difficult 4.5%

Candidate experience

Neutral 21.4%
Negative 11.9%
Positive 66.7%