> For the complete documentation index, see [llms.txt](https://docs.skolar.li/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skolar.li/hiring/manage-job-positions/action-menu/view-candidate/add-candidate/view-dossier/coding.md).
# Coding
The Coding Assessment is used to review and evaluate a candidate’s coding, technical thinking and practical knowledge.
A **Coding Dossier** provides a detailed analysis of a candidate’s performance in a coding assessment. It helps recruiters and evaluators understand not only the final score but also how the candidate performed throughout the assessment.
Click on Assessment will show Assessment Metrics (Trust%, Violation count, Duration), Code & Code Reviews, Proctoring & Violations Section, Audio & Transcription, Reviewer Notes.
Code Assessment
At the top of the page, the following details are displayed:
**Assessment Details:**
* **Assessment Name:** Shows the name of the coding assessment.
* **Assessment Date and Time:** Displays when the assessment was taken.
* **Assessment Status:** Indicates the current result or status, such as **Disqualified**.
* **Trust Score:** Displays the candidate’s overall assessment integrity score.
* **Violations:** Shows the total number of violations detected during the assessment.
* **Duration:** Displays the total time spent on the assessment.
* **Integrity Checks:** Shows the number of integrity checks successfully passed.
**Round Summary:**
Provides a quick summary of the candidate’s assessment monitoring and performance details.
#### Coding Performance
The **Coding Performance** section displays the candidate's overall performance, including:
* **Overall Score:** The percentage of marks scored in the assessment.
* **Marks Obtained:** The marks achieved out of the total marks.
* **Time Taken:** The total time spent completing the coding questions.
* **Programming Language:** The language used by the candidate for the assessment.
* **Total Questions:** Displays the number of coding questions in the assessment.
#### Question-wise Performance
Each coding question displays:
* **Question Number**
* **Question Title**
* **Difficulty Level** such as Easy, Medium, or Hard
* **Programming Language Used**
* **Date and Time**
* **Question Status** such as Partial or Incorrect or correct
* **Correctness:** Number and percentage of test cases passed
* **Performance:** Evaluation of the code performance, where available
* **Final Score:** Percentage scored for that specific question
* **Marks:** Marks obtained out of the total marks
Each question also includes the following options:
* **View Problem:** Opens the complete coding question.
* **View Code:** Displays the code submitted by the candidate.
* **Code Review:** Allows the evaluator to review the submitted solution.and also can re-run review.
* **What’s Assessed:** Shows the evaluation criteria or skills assessed for that question.
**Integrity Checks**
Integrity Checks are automated validations used to detect **suspicious or unfair behavior** during an assessment. This is tightly linked to the **Trust Score** and the “High Risk” flag.
There are multiple **Integrity Check’s:**
Webcam active, Microphone active, Full screen maintained, single person, Identity Verified, No Phone detected, no virtual cameras, Single IP, Browser Focus.
**Violations**
A violation is triggered when a candidate **breaks proctoring rules** or shows suspicious behavior during an assessment.
It helps recruiters evaluate assessment integrity and candidate authenticity.
**This section directly impacts:**
* Trust Score
* Risk Level (Low / Medium / High)
* AI Candidate Summary
**Common violation types**
* Face not visible
* Multiple faces detected
* Candidate leaves frame
* Switching browser tabs
* Copy/paste actions
* Right Clicks – Dev Tools (when off in assessment)
* Phone detected
* Noise detected
* Gaze away
* Mic Muted
**Snapshots**
Displays all snapshots captured during the assessment. Snapshots are captured periodically and during flagged events (like movement, tab switch, etc.) to ensure test integrity.
The snapshot strip loads with images after the assessment is completed.
Clicking a snapshot opens it in an enlarged modal view. This displays status, Time, Face match% & no of faces visible in the frame.
Status Label: “**Clean**” Indicates no suspicious activity detected in this snapshot.
Users can navigate between snapshots using the left and right arrows between multiple snapshots.
**Reviewer Notes:**
Allows the reviewer to add comments or feedback for the assessment round.
Have 2 Decision Buttons :
**Go / No-Go Decision:**
Enables the reviewer to mark the candidate as **Go** or **No-Go** after reviewing the assessment.
**Email Summary:**
Allows the reviewer to send or view an email summary of the assessment.
**History:**
Display the Review history
At the bottom, the page also displays the **number of rounds reviewed** and provides options to **Share** the dossier or **Schedule an Interview** with the candidate.
