In this tutorial, I'll show how you can leverage candidate states to track the interview progress for each of your candidates.
Candidate's Interview Lifecycle
Whenever you invite someone to complete a DevSkills assignment, they automatically get the "Invited" state. From this point on, they'll have seven days to accept the GitHub invite they have received until it expires.
When the candidate accepts their GitHub invite, they move on to the "Accepted" state. It's always good to communicate to the candidate in advance that you'd send them an assignment and that they should expect an email from GitHub (and remind them to check their spam folder).
Sometimes candidates get stuck with their assignment, and to make progress, they might ask for support by creating a GitHub issue on their assignment repository. Whenever that happens, they'll move to the "Support needed" state. The candidate will remain in this state until there are no open issues on their assignment repository.
Ready for Review
Once the candidate has completed their work, they create a Pull Request in GitHub. That is when their state will change to "Ready for review" so that you know who's ready for the code review part of the assignment. The candidate will remain in this state until there are no open Pull Requests on their assignment repository.
Did this article help?