Question-specific components: Programming problems
This topic is about the details that you will see about each programming problems in a candidate report.
 
| 
 S. No.  | 
 Description  | 
| 
 1  | 
 Question type  | 
| 
 2  | 
 Number of questions answered  | 
| 
 3  | 
 Total score obtained by the candidate  | 
| 
 4  | 
  | 
Notes
- Candidates can give multiple inputs to test their code.
 - Based on the score obtained the best submission will be displayed.
 
| 
 S. No.  | 
 Description  | 
|---|---|
| 
 1  | 
 Unique submission ID assigned to the submission and the date/time on which the submission was made Description  | 
| 
 2  | 
 Total score obtained by the candidate  | 
| 
 3  | 
 Average of the total time taken for the candidate's code to compile successfully  | 
| 
 4  | 
 Memory used by the candidate's code to compile successfully  | 
| 
 5  | 
 Language in which the candidate has written the code  | 
| 
 6  | 
 Input submitted by the candidate  | 
| 
 7  | 
 Indicates the result of each input  | 
| 
 8  | 
 Time taken to compile candidate's input  | 
| 
 9  | 
 Amount of memory used by the input  | 
| 
 10  | 
Score obtained for the input | 

| 
 S. No.  | 
 Description  | 
|---|---|
| 
 1  | 
 Helps you to understand where the compilation error occurred and why  | 
| 
 2  | 
 Candidate's code  | 
| 
 3  | 
 Play the candidate’s code as a video HackerEarth Recruit's code player records candidate’s keystrokes such that it can be played back as a video. This helps you to verify their approach to the solution and minimize any possibility of cheating.  |