C.H. Robinson logo

C.H. Robinson Software Engineer Interview Questions
& Process

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

Based on 34 interview experiences · FREE TO READ

2.4 Rounds average
Average Typical difficulty
58.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at C.H. Robinson.

Showing 3 of 34
C.H. Robinson logo
C.H. Robinson

Software Engineer Intern

Engineering · nearly a year ago

Intern Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding

The interview process started with a recruiter call, then went into a technical interview. The technical part had some C# specific questions, like asking about the meaning of "using", and also database design questions, specifically asking how to design a relational database for students, classes, and registration.

Confirmed questions2 questions
  • Can you explain the meaning of "using" in C#?
  • Describe how you would design a relational database for students, classes, and registration.
C.H. Robinson logo
C.H. Robinson

Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
System Design Technical

Applied for a Senior Software Engineer role and spoke with a recruiter, and we agreed on a salary. Then I went in for an in-person technical interview. There were three interviewers: two general developers and someone focused on databases. They asked me to design software for an online store. I asked for clarification on what they wanted me to focus on, like APIs, database schema, or user experience. They told me to start wherever. I began with the database design. The database specialist challenged my design, but I explained why I disagreed, and the other developers agreed with me. After a while, I asked if they wanted me to move on to APIs and business logic. They said yes, but it seemed like they weren't sure of their own process or what they were looking for. The recruiter later told me they don't hire external Senior Devs, as they prefer internal promotions. She also mentioned the salary cap would be about $5k lower than we discussed. I declined further consideration.

Confirmed questions1 question
  • How would you design software for an online store?
C.H. Robinson logo
C.H. Robinson

Software Engineer

Engineering · more than a year ago

Entry Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Technical Coding

The whole thing took about a month. Started with a recruiter call. Then there was a week wait before the first interview, which was a pretty weak technical interview. The second round was a full technical interview where I had to write code. It was with two older guys who seemed really unhappy in their jobs. They mentioned it was their first job and they'd been there ages, which is why they never left. They made me code in a language I chose, but they only knew C#. So I coded in Python, and they couldn't understand the syntax and said I was wrong. But I got the code done in the language I picked. Afterwards, they said HR would email feedback if I didn't get an offer. I didn't get an offer, and HR never got back to me even though I followed up multiple times. They basically just closed my application after the interview.

Confirmed questions4 questions
  • What makes you want to join this company?
  • How do you deal with difficult colleagues?
  • Can you reverse a string?

C.H. Robinson Software Engineer Interview Questions

Quoted word for word from C.H. Robinson interview reports.

In a terminal, how would you halt a program stuck in an infinite loop?

Read reports

Can you explain the difference between controlled and uncontrolled React components?

Read report

Can you explain the difference between asynchronous and synchronous programming?

Read report

Formats, difficulty and experience

Across all 34 C.H. Robinson interview reports.

Interview formats

Technical 37.5%
Behavioral 32.5%
Coding 15%
System Design 6.2%
Group 5%

Interview difficulty

Easy 23.5%
Average 70.6%
Difficult 5.9%

Candidate experience

Positive 58.8%
Negative 26.5%
Neutral 14.7%