Checkr logo

Checkr Software Engineer Interview Questions
& Process

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

Based on 48 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
35.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Checkr.

Showing 3 of 48
Checkr logo
Checkr

Software Engineer

Engineering · a year ago

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

So I started with a recruiter call, then there was a name matching exercise and then a hiring manager round. I was pretty surprised that after the third round, the hiring manager still had to run my resume by his team. Like, seriously, this is a huge waste of my time. I really can't recommend interviewing here. And if they don't give feedback when they reject you at this point, it says a lot about the company and their culture. They should really respect a candidate's time.

Confirmed questions1 question
  • A coding round involved a name matching exercise.
Checkr logo
Checkr

Software Engineer

Engineering · a year ago

Mid Average Positive experience Accept offer 4 rounds
Interview process
Take home Recruiter call Technical screen Onsite
Interview formats
Coding Technical Presentation Behavioral

So after applying, a recruiter from Checkr hit me up about a preliminary name matching code challenge that's detailed elsewhere. Then we had a 30-minute recruiter phone screen. After that, there was a pretty thorough set of technical challenges: 1) designing an object oriented diagram for a new Checkr feature, 2) an API development exercise, and 3) a core refactoring challenge. They were all pretty straightforward and we were given details beforehand. The whole thing ended with a chat with the hiring manager. Honestly, the interviews felt fair and pretty representative of actual software engineering tasks.

Confirmed questions5 questions
  • The name matching code challenge
  • Object oriented design for a new feature
  • An API development exercise
Checkr logo
Checkr

Software Engineer

Engineering · a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

Easily the worst interview experience I've ever had. Applied online, was contacted by Checkr recruiter, and scheduled first phone screening. Interviewer was immediately standoffish, had no interest in having a conversation, and was generally unpleasant on the phone. After being berated by the interviewer, I opted to end the phone call after only 6 minutes, to which the interviewer replied "sounds good" and hung up.

Confirmed questions2 questions
  • Can you walk me through your work history and your timeline for starting?
  • Could you detail your previous roles and when you're available to start?

Checkr Software Engineer Interview Questions

Quoted word for word from Checkr interview reports.

Implement a `name_match` method that takes a list of known aliases and a record name. Return True if the name matches any alias, False otherwise.

Read reports

Does `name_match` handle cases where the middle name is missing in the alias?

Read reports

Does `name_match` work when a middle initial matches a middle name?

Read reports

Can the first and middle names be transposed for `name_match`?

Read reports

Bonus: Does `name_match` account for transposed first and middle names?

Read report

Could you parse an address string and extract components like street, unit number, and zip code?

Read report

How would you compare a given name to a list of names?

Read report

How would you design a model for the game of battleship?

Read report

Write code for a name matching function within a 1-hour technical phone screen on CoderPad.

Read report

Formats, difficulty and experience

Across all 48 Checkr interview reports.

Interview formats

Coding 31.4%
Technical 27.3%
Behavioral 25.6%
System Design 11.6%
Presentation 1.7%

Interview difficulty

Easy 12.5%
Average 75%
Difficult 12.5%

Candidate experience

Negative 50%
Positive 35.4%
Neutral 14.6%