ruidy/hiring-without-whiteboards
1
0
Fork 0
mirror of https://github.com/rjNemo/hiring-without-whiteboards synced 2026-06-06 02:26:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge #1142

Browse source 
1142: +Checkr r=poteto a=MECU

## Add/Update/Remove Checkr

- [X] I have read the [contributing guidelines](https://github.com/poteto/hiring-without-whiteboards/blob/master/CONTRIBUTING.md)
- [X] I agree to the [Code of Conduct](https://github.com/poteto/hiring-without-whiteboards/blob/master/CODE_OF_CONDUCT.md)
- [X] I have followed the [format](https://github.com/poteto/hiring-without-whiteboards/blob/master/CONTRIBUTING.md#format) prescribed in the contributing guidelines
- [X] (OPTIONAL) In your pull request message, add additional context on the interview process if necessary

## Notes
- After the initial 1 hour tech screen, a decision will be made to stop or continue on to the longer set of interviews.
- The process can vary by team. For example, more front-end focused teams will employ a React refactoring problem and a JavaScript/React focused build.
- The sequence of the four interviews is not important. They do not cover the same topic and can be done in any order.
- The manager chat can happen before or after the four interviews and is sometimes used as a decision point.
- The level of the position can alter the amount and type of interviews. The example shown is for a mid-level or senior role. Internships will have less interviews and be simpler. Staff level will have a larger system focus, longer (some are 1.5 hours), and perhaps more (6) interviews.

Co-authored-by: Michael Hoppes <MECU@users.noreply.github.com>
This commit is contained in:
bors[bot] 2021-10-25 02:33:26 +00:00 committed by GitHub
commit f992ff9e4b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
README.md
View file

@ -176,6 +176,7 @@ Also check out [No Whiteboards](https://nowhiteboards.io) to search for jobs at
- [Chama The App](https://chamatheapp.bamboohr.com/jobs/) | Amsterdam, The Netherlands | Cultural fit interview, home test, technical interview with the team and then interview with the leadership
- [Chargify](https://chargify.com/jobs) | San Antonio, TX / Remote | Take-home project & pair on a problem similar to daily work
- [Checkout 51](https://checkout51.com/jobs) | Toronto, Canada | Phone conversation (15-20 minutes) followed by on-site pair programming and discussion focused on understanding decisions made during on-site work
- [Checkr](https://checkr.com/company/careers) | San Francisco, CA / Denver, CO / Orlando, FL / Remote | 1 hour CoderPad problem, if pass, then four 1 hour interviews: API Design using your computer and languages, Refactoring in language of your choice, Object Design (no coding), System Architecture (no coding) and sometimes a 30 minute manager chat [read more](https://medium.com/checkr/an-engineers-guide-to-interviewing-at-checkr-fc28f9e8014b)
- [Cheerful](https://www.cheerfulgiving.com) | Denver, CO / Remote | Take home small project which tests the adaptability of the developer with the stack used by the company, followed by a feedback interview (15 min) then a tryout offer (2 weeks / 1 month) or a permanent offer is made depending on the project results.
- [Chef](https://www.chef.io/careers) | Seattle, WA / Remote | Take home small project testing the ability to implement real world problems. Phone/Zoom interviews discussing the said project. Checking if the candidate would be a good cultural fit.
- [Chesapeake Technology](http://ctic-inc.com/careers/) | Denver, CO / Santa Barbara, CA / Camarillo, CA / Dulles, VA / California, MD / Remote | Phone screen (30 minutes), take home at leisure question based on real development followed by in person review of solution and general technical questions with actual team and opportunity for you to ask questions and provide feedback ( 2-3 hours)