Phone screen.

The first round coding problem is a string matching exercise having to do with matching names. The problem can be found online.

The final round is quite involved and a lot of work, and very much to ask for, especially for a junior (<2 years of experience) engineer. It is four 1-hour interviews, described as follows, in no particular order.

1. An object-oriented design problem where you are given some existing code and need to implement additional features using the best data structure/object-oriented design you can think of.
2. Code refactoring, a fairly straightforward description.
3. System architecture: they will ask you to design Checkr's product, and at the end will go over how your solution is different from the actual product, improvements, tradeoffs, etc.
4. Build an API with a framework/coding language of your choice. You will need to set up boilerplate code ahead of time.

I was scheduled for the onsite but withdrew because I had another offer, and I thought that prep, especially for the API design, was too much. Before each interview, a recruiter called and walked me through what to expect. They even walked me through the rubric of each onsite interview.

This might be nice for more experienced people, but it gave me a feeling that there was no way a junior could meet the expectations set forth by their rubric. I also felt there was pressure that 'you must perform almost perfectly because we told you what you will be asked.'

TLDR: This interview process would be good for senior people that have a lot of experience with system design and can build a REST API in less than an hour. There were no LeetCode-style questions. But I feel like for less experienced devs, the expectations and requirements are very high.

String matching exercise- someone else has posted the exact problem in another review.

Object Oriented Design Build REST API System Design (Architecture of Checkr's product) Code Refactoring