Taro Logo

Software Engineer Interview Experience - United States

April 1, 2022
Negative ExperienceNo Offer

Process

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, so the negative rating isn’t because of that but rather the process afterward. About a week after the technical interviews, I got an email to set up a coffee chat with a team manager. This was not an actual interview per se; the manager explained what the team was like.

I was jerked around for two weeks after that and finally got a rejection. This was a full month after the technical interviews.

My advice is to filter more strongly in those stages so you aren’t wasting time.

Questions

  1. Name matching problem (already given in another interview).

  2. Object design: Given some existing classes/features, add some more (in Miro).

  3. Refactoring code (in an IDE/language of your choice).

  4. Explaining the design of a project you’ve done (again, using Miro).

Also, each of the interviewers in the three-parter asks two behavioral questions that are based on their values.

Was this helpful?

Interview Statistics

The following metrics were computed from 24 interview experiences for the Checkr Software Engineer role in United States.

Success Rate

8%
Pass Rate

Checkr's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive25%
Neutral21%
Negative54%

Candidates reported having very negative feelings for Checkr's Software Engineer interview process in United States.