Grainger logo

Grainger Software Engineer Interview Questions
& Process

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

Based on 24 interview experiences · FREE TO READ

2.2 Rounds average
Average Typical difficulty
62.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Grainger.

Showing 3 of 24
Grainger logo
Grainger

Software Engineer

Engineering · nearly a year ago

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Technical

I was contacted by a recruiter. It took ages to get an interview, and it felt really disorganized. They ended up ghosting me even after I followed up. The whole thing was super unprofessional. They seem like a private club and don't seem to be actively searching for new and different skill sets.

Confirmed questions1 question
  • Could you describe how you would go about developing an API?
Grainger logo
Grainger

Software Engineer Intern

Engineering · nearly a year ago

Intern Average Positive experience Decline offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical System Design

The interviewers were super nice and most have been with the company for a while. It wasn't the typical LeetCode style, more object-oriented programming focused. There were 2 rounds: first a technical interview, then a mix of technical and system design.

Confirmed questions1 question
  • How would you design a system for tracking customer orders?
Grainger logo
Grainger

Software Engineer

Engineering · a year ago

Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Technical screen
Interview formats
Behavioral System Design Coding

It started with a recruiter call, then I met the Hiring Manager. After that, there was a System Design interview and a Full Stack Interview. It was pretty easy going until the full stack part where they hit me with CSS questions. I don't know much CSS because we have a separate team for that. Turns out, my knowledge was just enough to not get the job. They also said my full stack app had fundamental Spring Boot issues, which was weird because I've been using the same methods for the last 4 years. I usually get the feedback, but this time I was really disappointed.

Confirmed questions1 question
  • Could you tell me why you are interested in Grainger and what your career aspirations are?

Grainger Software Engineer Interview Questions

Quoted word for word from Grainger interview reports.

Given a string, arrange the character counts in descending order.

Read reports

How would you design a system for a manufacturer to notify a user about their delivery status?

Read report

Could you define and create a few functions for a given class in a programming language you prefer?

Read report

How would you design a system for tracking customer orders?

Read report

How would you approach updating content on our intranet CMS on a weekly basis?

Read report

How would you manage a situation with a coworker who is upset or angry?

Read report

Formats, difficulty and experience

Across all 24 Grainger interview reports.

Interview formats

Technical 31.6%
Behavioral 28.1%
Coding 21.1%
System Design 19.3%

Interview difficulty

Easy 29.2%
Average 62.5%
Difficult 8.3%

Candidate experience

Negative 16.7%
Positive 62.5%
Neutral 20.8%