Prerequisites

Supported browser
versions
• ​Internet Explorer: Version 11 and
above

• ​Chrome: Version 15 and

• ​Firefox: Version 15 and

• ​Safari: Version 7 and above

• Opera: Version 12 and above

Internet
speed

• Minimum 512 kbps/candidate

Other
Requirements

• JavaScript should be
enabled

• Width or height of the screen should be greater than

• Cookies should be enabled

FAQs

1. Candidates are unable to view the questions

2. Candidates are unable to view the code

Refresh the
screen

3. Will refreshing the page log the candidate

N
o

4. What does the Reset function

Be careful while activating the ​Reset ​function for any candidate. When you reset a test, it
deletes all the

saved submissions and attempts of the candidates and no record of any activity remains for
reference.

This function should ideally be used when a candidate faces system

5. Does the platform automatically save a candidate’s

• For programming questions: Yes, the platform will automatically save key strokes,
however, the

candidate still needs to submit after compiling the

• For MCQs: No, the platform does not automatically save a candidate’s activities. The
candidates

must press Submit after attempting a question, else it will not be

6. What does “System compatibility

It checks the
following:
 a. Operating system
version

b. Browser version

c. JavaScript
enabled

d. Screen
size

e. Cookies
enabled

Candidates
FAQs

1. What is wrong
answer?

Your program ran successfully but gave an incorrect answer. Most probably your program
contains a bug,

or you are not interpreting the problem text correctly. If your code shows that it has passed the
sample

input correctly, then remember that there are multiple input and output cases for which your
code is

supposed to be evaluated, which is why despite passing the sample input cases, you’re still
getting a

wrong
answer.

2. I keep getting various types of runtime errors. What am I

A runtime error means that the program was compiled successfully, but it exited with a runtime
error or

crashed. You will receive an additional error message, which is most commonly one of the
following:

a. SIGSEGV: This is the most common error, i.e., a "segmentation fault". This may be
caused e.g. by

an out-of-scope array index causing a buffer overflow, an incorrectly initialized pointer,

signal is generated when a program tries to read or write outside the memory that is
allocated

for it, or to write memory that can only be read. For example, you’re accessing
a[-1] in a

language which does not support negative indices for an

b. SIGXFSZ "output limit exceeded": Your program has printed too much data to
output.

c. SIGFPE "floating point error": This usually occurs when you’re trying to divide a number
by 0, or

trying to take the square root of a negative

d. SIGABRT: These are raised by the program itself. This happens when the judge
aborts your

program in the middle of execution. Due to insufficient memory, this can be

e. NZEC (non-zero exit code): This message means that the program exited returning
a value

different from 0 to the shell. For languages such as C/C++, this probably means you
forgot to add

"return 0" at the end of the program. It could happen if your program threw an exception
which

Prerequisites | HackerEarth Recruit

was not caught. Trying to allocate too much memory in a vector. For interpreted
languages like

Python, NZEC will usually mean that your program either crashed or raised an
uncaught

exception. Some of the reasons being in such cases would be the runtime errors
mentioned

above. Or, for instance usage of an external library which is causing some error, or
not being

used by the
 judge.

f. MLE (Memory Limit Exceeded): This error means that your program tried to allocate
memory

beyond the memory limit indicated. This can occur if you declare a very large array, or
if a data

structure in your program becomes too

g. OTHER: This type of error is sometimes generated if you use too much memory. Check
for arrays

that are too large, or other elements that could grow to a size too large to fit in memory.
It can

also be sometimes be generated for similar reasons to the

Some ways to avoid runtime

• Ensure that you aren't using variables that haven't been initialized. These may be set to 0 on
your

computer, but aren't guaranteed to be on the

• Check every single occurrence of accessing an array element and see if it could possibly be
out of

bounds. Ensure you aren't declaring too much memory. 64 MB is guaranteed, but having
an array

of size [100000][100000] will never

• Ensure you aren't declaring too much stack memory. Any large arrays should be
declared

globally, outside of any functions - putting an array of 100000 ints inside a function
probably

won't
work.

3. What is the difference between Compile and

Every problem page has particularly two

• Submit

When you click ​Compile and Run​, the code that you have submitted is tested against the
Sample Input

and Sample Output. This is for your convenience to check whether the code is working
properly for the

sample test cases or

When you click ​Submit​, the code is checked against the internal testcases. These test
cases are

complicated and take your program through rigorous checks so that only the perfect code can
pass the all

the test
cases.

4. What do the test cases check the code

• The code should run within the stipulated time otherwise it will throw Time Limit
Exceeded(TLE)

Prerequisites | HackerEarth Recruit

• The code should run within the give memory size otherwise it will throw Memory
Limit

Exceeded(ML
E)

• Some testcases are tricky that are made only to check for Runtime
Error(RE)

• Wrong answer(WA) means simply that your program is not printing out the correct answer.
Make

sure your program is conforming exactly to the output format required, and not
printing out

unnecessary
information.