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	Time limit: Indicates the time limit within which the candidate's code should compile successfully Memory limit: Indicates the maximum amount of memory that the candidate's code can use to compile successfully

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

Submission status

Candidate's submission might result in the following:

S. No.	Icons	Description
1		Input is accepted
2		Input is partially accepted
3		Compilation error
4		Runtime error, Fatal error, Output is too large, Floating point error, segmentation fault, Non-zero exit code
5		Time limit exceeded
6		Memory limit exceeded
7		Incorrect input

S. No.

Description

Helps you to understand where the compilation error occurred and why

Candidate's code

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.

Articles in this section

Submission status

Comments