I was a former engineer here, so this review will be more from my perspective of Checkr engineering. I'm not sure if it will necessarily be applicable to other teams and functions.
The first thing everyone should know is that Checkr is very much a startup, which indeed means it is very fast-paced, chaotic, and cutthroat at times. Like with many startups, you will likely be asked to go above and beyond your initial role and responsibilities, and you would likely need to pivot very quickly.
I don't think these are necessarily bad things, but it is not for everyone. Maybe recruiting can do a better job in making these things clear upfront during the interview process so people won't be caught by surprise later?
I've heard of multiple complaints regarding management incompetency, and how that likely directly contributes to issues with retention and morale. Given that most managers likely had to take on more than what they initially signed up for, since, like with any startup, all levels of folks likely absorb new responsibilities, I think we can be sympathetic towards their situations. Everyone, after all, is trying their best given the hand they are dealt with.
As mentioned in the 'Pros' section, Checkr is not for everyone. Frequent chaos combined with role and responsibility creep, again while it is common for startups, will eventually lead to burnout, which in turn has negative consequences across the org. In my perspective, a lot of this comes from C- and E-level management, where the message is a resounding "do more with less."
First, you will be asked to complete an online assessment. No camera or mic is required. It contains one coding question. Then, you will get the HR call. I didn't get the next step after that.
Started with a 60-minute technical exercise on CoderPad, the name-matching exercise already discussed. Got an email pretty soon after that to schedule a three-part interview and was given a PDF with basic info about it. The interviewers were polite,
The interview process is quick and transparent. Got some feedback at the end. The questions are not hard, but it is ambiguous on purpose. The office looks nice, with a great view in downtown SF. The work doesn't seem very interesting. It's mostly
First, you will be asked to complete an online assessment. No camera or mic is required. It contains one coding question. Then, you will get the HR call. I didn't get the next step after that.
Started with a 60-minute technical exercise on CoderPad, the name-matching exercise already discussed. Got an email pretty soon after that to schedule a three-part interview and was given a PDF with basic info about it. The interviewers were polite,
The interview process is quick and transparent. Got some feedback at the end. The questions are not hard, but it is ambiguous on purpose. The office looks nice, with a great view in downtown SF. The work doesn't seem very interesting. It's mostly