The interview process starts with a HR screen, before proceeding to a first round code screen. The exercise wasn’t terribly difficult, but you are on a time crunch. My interviewer was nice, but I feel like towards the end they led me down the wrong path. I just really don’t like these live coding interviews where you have to get the question right and you’re tested on “collaboration.” Can you even truly test collaboration, when the interviewer already knows the answer? In the end I feel like I was close, but stumbled due to anxiety about wanting to make it to the next round. I recommend just relaxing and hopefully you are good at solving problems while someone stares at you and maybe gives not so helpful hints. It’s also telling that probably most of the ppl who here probably got the same question, yet rejected after the first round 🤔 I doubt it is due to true incompetence.

After applying, a Checkr recruiter reached out with the preliminary name matching code challenge described in detail in other posts. This was followed by a 30-minute recruiter phone screen. There was then a pretty exhaustive set of technical challenges: 1) object oriented design diagram for a new checkr feature 2) an api dev exercise 3) a core refactoring challenge. They were all straightforward and you’re given details for each challenge in advance. The process wrapped up with a conversation with the hiring manager. Overall, the interviews were fair and reflective of actual software engineering work