Connect a GitHub repository containing the programming assignment and invite the candidate, optionally setting a timebox
Candidate works on a solution
The candidate receives an e-mail with instructions on how to clone a unique Git repository that's specific to them, and starts working on the challenge, using the tools they're familiar with
Review pull requests
Once the candidate commits their solution, a pull request is opened for you and your team to review
Lives on GitHub
The challenges and the solutions reside in your GitHub repository. No need to worry about adding collaborators or creating a private repo for every candidate.
Timebox
Timebox challenges to limit the time candidates can spend working on a solution. The clock starts when a candidate clones the repository.
Review interface you know
Candidates solutions result in pull requests, making it easy for you and your team to review, comment, and communicate about their work.
Any stack, any editor
Let candidates work with the tools they're most comfortable with, instead of limiting them to web-based editors.
Custom challenges
Contents of any private GitHub repository can be issued as a programming challenge.
Challenge library
soon
Our ready-to-use programming challenges include generic, as well as language-specific, challenges for Python, TypeScript, and many more programming languages.
How do I issue custom programming challenges? Any of GitHub repositories you grant access to can be issued as a challenge. Set up a private GitHub repository, commit challenge instructions (README.MD works well) along with any code and other files you want the candidate to receive to master branch and issue the challenge using Zero In.
What happens when a candidate submits their solution? Once a candidate submits their solution (or the timebox expires, if set – see next question), Zero In opens a pull request in the repository containing the challenge, against a per-candidate "review" branch pointing to the exact commit used for issuing the challenge. That way, you can keep updating the master branch and altering the challenge, while still getting a review diff representing work done by each candidate.
Can one candidate see other's solutions? No – each candidate is provided with a dedicated Git repository containing only the challenge issued, and can not see other candidates branches or solutions.
