Understanding the coding assessment submissions view

The coding submissions screen is shown per question, not as one single combined history for the entire assessment. This guide helps you read it correctly.

The coding assessment submissions screen is one of the easiest places to misread candidate performance.

What the submissions view actually shows

The submissions panel is tied to individual coding questions.

That means:

  • the code shown may belong to one specific question
  • the test case results may belong to one specific question
  • a failed output on one question does not mean the candidate failed the entire coding assessment

A common misunderstanding

Sometimes teams open the coding submissions view, see failing test cases, and assume:

  • the candidate failed the whole coding round
  • the platform mixed up the submission history
  • the candidate got everything wrong

In most cases, the page is simply showing question-level submission data, not a single merged view of the full assessment.

How to review the assessment correctly

When evaluating a coding attempt, check:

  1. which question is currently selected
  2. how many total questions were part of the assessment
  3. whether the candidate submitted answers to multiple questions
  4. the overall completion and final score, not just one failing case

Best practice

Do not judge the full coding round from one failed test case screen alone.

Instead, review:

  • all attempted questions
  • completion status
  • overall performance
  • final evaluation context

When to contact support

Please contact support if:

  • the wrong question appears attached to a submission
  • the attempt history looks incomplete
  • the final result seems inconsistent with the visible question data

Please include the attempt link, candidate name, and role/job title.

On this page