Documentation menu

Candidate reports

Last updated on Disponible en Français

Select an item from the list below to get more information:

Finding a report

To find a candidate’s report, go to your Tests list and select the relevant test.

The main screen dashboard is shown and the tests item is highlighted in the left nave screen.

Select the candidate from the candidates list.

The candidates list is shown.

The candidate report pops out on the right.

  • Click Actions to export the report as PDF, share it, or anonymize/delete a candidate and their results.
  • Click View detailed report to access the candidate’s full report including completed answers.
The report tab got a candidate test is shown. It's broken down between Java results and SQL results. The test history for the candidate is below that.

Candidate report and score

Comparative score

For the comparative score, we compare your candidate to all candidates who have taken a similar test on the platform (across all organizations). For each question in your test, we compute the success rate of the question based on this historical data.

Based on all question success rates, we derive a statistical simulation of 1000 candidates with their point score. Then we just position your candidate in this leaderboard of 1000 simulated candidates (based on their point score).

The image is an infographic consisting of four parts, explaining a candidate evaluation process:

1. Historical Success Rates:
   - Titled "Historical success rates".
   - Includes an icon of a clipboard with a chart.
   - Text: "We calculate the average success rate of each question in your test based on historical data."
   - An example is shown where "Question 1 = 60%", meaning that 60% of the candidates answered question 1 correctly.

2. Population Distribution:
   - Titled "Population distribution".
   - Contains an icon of three people with bar graphs behind them.
   - Text: "We analyze the distribution of candidates to determine how 1000 random candidates would perform on your test."
   - An example shows "Candidate 4" with icons representing three questions and the text "30 points in 22min".

3. Simulated Leaderboard:
   - Titled "Simulated leaderboard".
   - Features an icon of a podium.
   - Text: "We rank these candidates based on their point score."
   - An example leaderboard shows "Candidate 1" with 50 points, "Candidate 2" and "Candidate 3" with 40 points, "Candidate 4" with 30 points, and "Candidate 1000" with 15 points. An arrow points to "Candidate 4".

4. Comparative Score:
   - Titled "Comparative score".
   - Includes an icon of a person and a bar chart.
   - Text: "Where does your candidate rank in this simulated leaderboard?"
   - An example illustrates "Your candidate" with 25 points on a bar chart indicating a comparative score above the 99th percentile.

The background is dark gray, and the text and icons are in yellow, white, and lighter gray, making for a high-contrast design. The sections are numbered 1 to 4, indicating the sequence of the process.

ℹ️ If it’s a new question with little comparative data, the score will be based on question difficulty.

To view the comparative score, go to the test’s Candidates list.

An arrow is pointing to the comparative score column.

To see the finer details about a comparative score, click on the candidate’s name; you’ll see a pop-up similar to the image below. The highlighted graph in the top left represents the candidate’s level. Here, the candidate is better than 96% of developers tested on the same or similar questions on Screen.

A red box surrounds the "Better than 96% developers" display on the candidate report.

Click on the information circle to see information about the rating.

The text of the information circle: "This data allows you to rank your candidate against developers who have taken a similar test." then a link to find out more.

The panel on the right reflects time spent on the test in relation to the total time allocated, as well as the candidate’s score in relation to the questions asked.

The display of candidate rank (1 of 8), test duration (22 minutes out of 53 minutes) and points (1560 our of 1920, or 81%).

Underneath, each domain your candidate has been evaluated on has a dedicated comparative score. 

Points and candidate results broken out by language. For Java, candidate is better than 88% of developers, for sql it is 92%.

Assessment criteria

Candidates are also awarded a score per assessment criteria.

Results broken down by criteria; here it is design, language knowledge, problem solving, and reliability.

When you hover over the criteria, you will be able to see more information on that specific criteria:


This measurement gives and indication of the candidate's ability to implement standard solutions to common problems. A developer with a good level of proficiency in this skill will contribute to increase the quality (maintainability, extensibility) of your applications. It does not rely specifically on technology.

Language knowledge

Measuring this skill allows us to determine the candidate's level of experience in the practice of a specific programming language.

Problem solving

This skill corresponds to the candidate's ability to understand and to structure his reasoning in order to find efficient solutions to complex problems. It does not rely specifically on technology. This skill is particularly important if, for example, you are looking for R&D developers.


Each of your test’s questions influences one or more of these criteria.

View detailed report

Click on View detailed report to view a candidate’s answers.

The answer your candidate selected is specified by the grey dot.

If a candidate’s answer is incorrect, Candidate’s answer is red,  and the correct answer is green below. You’ll also see a red X next to the question.

An example of a wrong answer result. There is a red x next to the question title and number at the top, a red x next to the word "result" at the bottom, and on the right it has the answer and the words "candidate's answer" is in red. the correct answer is shown as green.

If a candidate’s answer is correct, Candidate’s answer is green, and the correct answer is green below. You’ll also see a green tick next to the question.

An example of a wrong answer result. There is a green check mark next to the question title and number at the top, a green check next to the word "result" at the bottom", and on the right it has the answer and the words "candidate's answer" is in green. the correct answer is shown as green.

Sharing a report

To share a report with a colleague who does not have a Screen account, go to the test report you’d like to share. 

Click Actions.

A candidate results screen with an arrow pointing towards the "actions" button at the bottom.

There are a two ways to share the report:

Share via URL

Select Share link.

The actions button menu has been clicked and the menu list is displatyed. Share link menu item has a red arrow pointing towards it.

The link to the report copies to the clipboard.

Confirmation modal that says "url copied to clipboard".

Download the detailed report

After clicking Actions, select Export.

Actions menu list displayed with an arrow pointing towards the export menu item.

Choose the export format, report type, whether to anonymize your candidate, and whether to include test ranking and the comparative score.

The export modal with an arrow pointing towards "export format" with the options "pdf file" and "csv file". Another arrow pointing towards "report type" with the options "simplified report" and "detailed report".

❗ Do NOT share detailed reports with candidates as they contain test questions. 

Click Export to download the PDF or CSV file.

Export modal with a red arrow pointing towards the export button at the bottom.

Reviewing candidates tutorial video

For more information on reviewing your candidates’ test results, check out this Reviewing candidates with CoderPad Screen video tutorial: