Redbox logo

Redbox Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

2 Rounds average
Average Typical difficulty
75% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Redbox.

Showing 3 of 5
Redbox logo
Redbox

Software Engineer II

Engineering · more than a year ago

Mid Average Negative experience Accept offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral Other

The interview process was a bit inconsistent and felt like they were trying to gauge my political alignment. It seemed like they favor liberal viewpoints and are not fond of conservative ideas or Christianity. They specifically wanted to know if I leaned liberal.

Confirmed questions2 questions
  • Do you support LBGT and Obama?
  • Are you liberal or Republican?
Redbox logo
Redbox

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Onsite Offer Background check
Interview formats
Behavioral Technical Coding

A recruiter from redbox reached out about software development roles on the client team, who handle software for the redbox machines nationwide. I let them know I was on a tight schedule with other interviews and potential offers. They set up an on-site interview. I dressed formally, but the office culture turned out to be very casual, which was a relief. First, I met with the VP of software. He had me detail my past projects, asking me to whiteboard their architecture and draw UML diagrams for system workflows. He also asked some high-level technical questions about RESTful web services. Next, the two most senior client team members interviewed me. After a brief summary of my work, I was given a C# code snippet with LINQ and asked to trace it, explaining variable values and noting LINQ's deferred evaluation. They then asked why I wanted to work there and what made me a good fit. I discussed salary at the very end for negotiation. They were very accommodating with my salary expectations. I accepted the offer verbally, then received and signed the offer letter and benefits. I started two weeks later, received new hardware immediately, and found the team to be very welcoming and collaborative. The company was doing well, providing good perks. The system was complex, taking time to master. My main issue was the high turnover of contractors, requiring constant retraining of new hires.

Confirmed questions1 question
  • Given that this is a Microsoft shop with MSDN licenses, expect many .NET Framework questions. The only part that tripped me up was being asked to manually evaluate variables in LINQ statements, which involves the concept of deferred execution, meaning the return value of LINQ statements might not actually update until execution is strictly necessary, even if the statements themselves change. You should look this up.
Redbox logo
Redbox

Software Engineer

Engineering

Mid Average Positive experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical Coding System Design

It was a good technical round. Questions were based on algorithms and sorting complexity. There was also a quick whiteboard question for distributed computing solution for a data problem. Most questions were theoretical and white board questions was based on solving time complexity.

Confirmed questions2 questions
  • Data Structures questions and a whiteboard session
  • Can you explain the time complexity of sorting algorithms and discuss DS questions?

Redbox Software Engineer Interview Questions

Quoted word for word from Redbox interview reports.

Could you estimate the number of people who flew out of Chicago last year?

Read reports

Can you explain the time complexity of sorting algorithms and discuss DS questions?

Read reports

Given that this is a Microsoft shop with MSDN licenses, expect many .NET Framework questions. The only part that tripped me up was being asked to manually evaluate variables in LINQ statements, which involves the concept of deferred execution, meaning the return value of LINQ statements might not actually update until execution is strictly necessary, even if the statements themselves change. You should look this up.

Read report

Formats, difficulty and experience

Across all 5 Redbox interview reports.

Interview formats

Technical 33.3%
Coding 33.3%
Behavioral 16.7%
System Design 8.3%
Other 8.3%

Interview difficulty

Easy 0%
Average 100%
Difficult 0%

Candidate experience

Positive 75%
Negative 25%