Skip to content
English
Back to Scalyz
  • There are no suggestions because the search field is empty.

Recruiter Checklist Before Sending a Test

This article provides the complete checklist recruiters should follow before sending a Scalyz test: selecting the right lab, confirming candidate data, setting expectations, defining evaluation criteria, and preparing internal follow-up.

Before sending a technical assessment through Scalyz, recruiters should ensure that the selected test fits the role, that the candidate is properly informed, and that the internal pipeline is ready to review the results.
This checklist helps maintain a simple, consistent, and efficient testing process.

1. Define the hiring need

Before selecting a test, clarify:

  • The role (DevOps, Cloud, Backend, Data, SRE…).

  • The required seniority: Junior, Mid-level, Senior.

  • The purpose of the test within the hiring process:

    • Pre-screening,

    • Technical validation,

    • Comparing multiple candidates,

    • Final selection.

A clear definition ensures a relevant test choice.

2. Select the appropriate test

The lab should reflect the actual tasks of the role. Verify:

  • The difficulty matches the expected level.

  • The scenario covers key skills (Linux, Docker, CI/CD, Cloud, etc.).

  • The expected duration fits candidate constraints.

  • The test is representative of real job responsibilities.

A well-selected lab prevents false positives and false negatives.

3. Verify candidate information

Ensure the data used in the invitation is correct:

  • First and last name,

  • Valid email address,

  • Time zone if the candidate is international.

Accurate information ensures successful delivery.

4. Prepare and personalize the invitation

Before sending the test:

  • Add a short message explaining the purpose of the assessment.

  • Set a clear deadline.

  • Mention the conditions of the test:

    • Estimated duration,

    • Practical lab running in the browser,

    • No local installation required.

Clear communication increases completion rates.

5. Inform the candidate beforehand

The candidate should know:

  • The format: hands-on lab, real commands, log analysis.

  • The estimated time needed to complete the assessment.

  • The technical requirements: stable connection, modern browser.

  • The evaluation method: actions, commands, results, best practices.

Clear expectations reduce abandonment.

6. Prepare internal follow-up

Before sending the test, make sure internal tracking is ready:

  • Enable automatic reminders if needed.

  • Monitor statuses: Not Started, In Progress, Completed.

  • Schedule time to review the final report.

  • Sync with your ATS or CRM if applicable.

A structured follow-up speeds up decisions.

7. Define decision criteria

Plan in advance:

  • Minimum accepted score or performance level.

  • Key skills required for a “Go”.

  • Blocking elements leading to a “No Go”.

  • Balance between speed, accuracy, and best practices.

Clear criteria ensure consistent evaluation across candidates.

8. Final checks before sending

Before clicking “Send”:

  • The correct lab is selected.

  • The candidate’s email is verified.

  • The deadline and message are confirmed.

  • Internal review capacity is available.

A final check prevents sending errors.

Conclusion

This checklist helps recruiters use Scalyz efficiently and consistently. By following these steps, sending tests becomes easier, results become more actionable, and hiring decisions are faster.