The candidate journey

The workflow is designed to be as close to the normal working conditions for developers as possible.
What does a normal workflow mean?

  • Downloading and uploading code from a remote repository (git)
  • Using software for building and modifying code on the local machine
  • Running tests on the local machine (TDD)
  • Getting status reports on code uploads by a web service (CI/CD)
Candidates complete workflow with Coderhead, from start to finish:
  1. Candidate gets welcome email
  2. In email, clicks link to Coderhead web service
  3. Sets a password
  4. Is informed about recommended software to install
  5. Is informed about test in general
    1. Task goals
    2. What to prioritize
    3. What the test will be like
  6. Test is started and access to the test is provided
  7. Candidate downloads test
  8. Detailed instructions about the tests are provided both on the web service and as part of the downloaded test
  9. Candidate solvs tasks on their own machine and uploads solutions
  10. Test status is presented after every upload on the Coderhead web service
  11. Candidate clicks a button on the Coderhead web service when done

Picture of developer on bed

The recruiter journey

This section describes working directly with Coderhead as a recruiter. If you have Teamtailor see, ATS Integration.

A recruiter can get a complete overview of all candidates inside Coderhead, and where they are in the pipeline. For finished or actively working candidates, the individual results can be viewed as well.

When adding a new candidate, all that is needed is name and email. After adding a candidate there is not much for the recruiter to do until a notification arrives that the candidate is done.
A finished candidate is bundled with a brief report:

  • How many of the tests are passed / failed
  • How long time did the test took
  • The complete solution and git history

Book a demo

Picture of meeting