McMaster-Carr logo

McMaster-Carr Interview Questions
& Process

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

Based on 685 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
50.1% Positive experience

Which role are you interviewing for?

30 roles · 685 reports

Candidate interview experiences

First-hand accounts from people who interviewed at McMaster-Carr.

Showing 4 of 685
McMaster-Carr logo
McMaster-Carr

Management Trainee

Operations · nearly a year ago

Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Background check Offer
Interview formats
Behavioral Technical

A recruiter reached out on LinkedIn. First was a 1-on-1 with the recruiter about my experience, location, and citizenship. Then, I had a relaxed first interview with an HR director, discussing my experiences and asking STAR questions. The final round was in-person, with travel and hotel covered. It started with a facility tour, followed by back-to-back interviews with VPs and directors. The talks were easy, focusing on work and improvements, with some STAR behavioral questions. I didn't get an offer, receiving a rejection email about 3 days later. It's a bit frustrating to not get feedback after taking time off work for interviews.

Confirmed questions1 question
  • What improvement would you suggest for our warehouse and how would you implement it?
McMaster-Carr logo
McMaster-Carr

Customer Solutions

Sales · nearly a year ago

Entry Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral

Got contacted and went through the whole thing, ending with a 2.5-hour on-site that included a tour, another interview, and an assessment. The recruiter and the people who showed me around were nice and professional. However, things felt a bit unorganized. The recruiter tried to set up a prep call on a Sunday for a Monday interview. What was really off was the assessment. They said I wouldn't need a background in supply chain or equipment because of their 6-month training, but the assessment was super technical. It's a bummer to spend so much time during the holidays and then get tested on stuff I was told wasn't necessary. They should make sure their message about 'no experience needed' actually matches the tests. Also, giving some feedback after a long on-site should be a thing.

Confirmed questions1 question
  • Can you tell me about the metrics you've worked with before?
McMaster-Carr logo
McMaster-Carr

Software Engineer

Engineering · nearly a year ago

Entry Difficult Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Behavioral Technical Coding

So the whole thing started with a recruiter call, then I had to share a project with them. After that, there was a technical chat with an engineer, not coding though, just talking. Then the final step was a full day of onsite interviews. My impression is it's a good place to grow, but it's pretty intense and you always need to be performing at your best to avoid being laid off. Everyone seemed nice during the interviews, but be aware that the coding part of the final day focuses heavily on web dev, so if that's not your strong suit, it might be tough.

Confirmed questions3 questions
  • Can you tell us about the project you worked on?
  • How did you take ownership of this project?
  • What challenges did you face during this project, and how did you overcome them?
McMaster-Carr logo
McMaster-Carr

Software Engineer

Engineering · a year ago

Senior Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical Coding

A recruiter hit me up on LinkedIn. Booking the interview was self-serve and straightforward. I also applied on their website myself. The first interview was with the hiring manager after the virtual screen. It was pretty chill, mostly checking for cultural fit, and I got to ask my own questions. The company's setup is different from the usual downtown tech scene, so it was cool to learn how they do things. After that, there were more technical interviews, focusing on standard college-level algorithms and math problems. The whole process felt efficient, giving enough time to prep without dragging on. Unfortunately, the role was primarily .NET, which didn't align with my preferred tech stack.

Confirmed questions1 question
  • Can you tell me about your cultural fit and expectations for working in a software role at a factory location?

McMaster-Carr Interview Questions

Quoted word for word from McMaster-Carr interview reports.

How do Go routines compare to using multiple single-threaded Node instances in terms of benefits?

Read reports

What are the reasons for using multiple shipping companies for product delivery instead of just a single one?

Read reports

What is your reasoning for our company not featuring brand names in its catalog?

Read reports

Imagine a customer got 3 lightbulbs instead of the 9 they ordered. How would you figure out where that mistake happened?

Read reports

If you had really wanted to, do you believe you could have gotten straight-As in college?

Read report

What are your thoughts on why we might store larger items in the warehouse, considering the typical loss incurred when storing and selling them?

Read report

Show me an example of a website you think is bad, and how would you improve it?

Read report

Do you have any thoughts on why certain products are stored at the front of the warehouse?

Read report

Imagine you owned a sandwich shop; what strategy would you use to decide on inventory types and amounts?

Read report

Formats, difficulty and experience

Across all 685 McMaster-Carr interview reports.

Interview formats

Behavioral 51.1%
Technical 23.8%
Presentation 10.4%
Other 7.8%
Case 4.2%

Interview difficulty

Easy 29.9%
Average 60%
Difficult 10.1%

Candidate experience

Positive 50.1%
Negative 18.8%
Neutral 31.2%

Reports by job function

Operations 386
Other 119
Engineering 74
Sales 45
Analytics 15
Design 9