Envié una solicitud electrónica. El proceso duró 3 semanas. Acudí a una entrevista en Checkr en jul 2025
Entrevista
same as what others have posted and did onsite. they ghosted me tho. kind of messed up. speaks to the quality of employees they have. unless you want to waste your time. dont bother applying
Preguntas de entrevista [1]
Pregunta 1
name matching exercise, rules matching algorithm, upload csv and create endpoints
Envié una solicitud electrónica. Acudí a una entrevista en Checkr (San Francisco, CA) en sept 2025
Entrevista
Spoke with recruiter about prior experience and potential alignment with the role. Went over current products of the company, day to day expectations for the role, and logistics. Was then given a link for an online assessment.
Preguntas de entrevista [1]
Pregunta 1
Code Assessment mimicking potential business logic within the API layer. Code must pass test cases (not all known). Done in hacker rank IDE. Given about one hour to do it.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Checkr (Denver, CO) en jul 2025
Entrevista
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
Preguntas de entrevista [1]
Pregunta 1
Name matching code challenge; object oriented design; api development; code refactoring; vibe and behavioral questions
