What is a HackerRank test?

A HackerRank test is an online assessment a company builds on HackerRank's platform and sends you by invitation link, usually as the first step of screening. The company picks the questions, the languages, the time window and the integrity settings. HackerRank runs your code against test cases, adds up the points and sends the report to the company.

HackerRank's candidate FAQ for before the test describes it this way: "HackerRank tests are online assessments conducted by companies to assess a candidate's skills required for different roles in their organization". It also says where the test sits: "Typically, HackerRank Tests are the first step in a company's candidate screening process, and those who clear the test qualify for an online coding interview on HackerRank Interviews".

Everything on this page comes from HackerRank's own candidate and employer help pages and its sample test, checked November 18, 2026. Where HackerRank publishes nothing, the page says so. Read your invitation first, because the company sets most of what follows.

What does a HackerRank test look like?

A HackerRank test opens from the invitation link, with no account needed, on a laptop or desktop in a current browser. You get a dashboard of questions, a code editor whose language dropdown shows only what the company enabled, Run Code for the sample tests and Save & Proceed to submit each answer. A timer runs throughout.

The before-the-test FAQ says no account is needed: "Open the test link from your invitation email and enter the details requested in the test login form". On hardware, "you must use a PC or Laptop," and phones and tablets are listed as unsupported. Tests "are best supported on the latest versions of Google Chrome or Mozilla Firefox".

Languages are the company's call. The during-the-test FAQ says "You can choose only from the languages enabled for that question. The hiring company decides which languages are available based on the skills they want to evaluate". HackerRank's employer page on scoring a coding question says coding questions "support more than 35 programming languages," so the dropdown you see is a subset.

QuestionWhat HackerRank saysSource
Account needed?No; open the link and fill in the login formBefore-the-test FAQ
Device?PC or laptop only; phones and tablets unsupportedBefore-the-test FAQ
How long?Set by the company; the timer shows orange then red alerts near the endDuring-the-test FAQ
Can you pause?Not published; the timer keeps running if you go offlineDuring-the-test FAQ
Which languages?Only those the company enabled per question, from 35+ supportedDuring-the-test FAQ, scoring page
Does Run Code count?No; running your code does not affect your scoreDuring-the-test FAQ
How is it scored?Each test case has a fixed score; pass earns it all, fail earns zeroScoring page
Sample test cases?Worth zero in HackerRank's example; they check basic logicScoring page, during-the-test FAQ
Pass mark?Not published; the company decidesNone
Do you see your score?Not published on the candidate pages; the submission goes to the hiring teamAfter-the-test FAQ
Reschedule or retake?Not through HackerRank; the hiring company manages itBefore-the-test FAQ
Proctored?Only if the company turns it on; the invitation email tells youBefore-the-test FAQ
Practice?A 30-minute, 3-question sample test, repeatableSample test page

How is a HackerRank test scored?

HackerRank scores a coding question test case by test case. Each case carries fixed points; pass it and you get all of them, fail it and you get none. There is no partial credit within a test case. Sample test cases are worth zero in HackerRank's own example, and hidden test cases carry the points.

The scoring page says "Each test case has a predefined score," and that a pass earns "the full predefined score" while a fail earns "a score of zero". It adds that "Partial scoring does not apply," and that the total "equals the sum of the scores for all passed test cases".

HackerRank's worked example has "11 total test cases, including 2 sample test cases and 9 hidden test cases". The two samples are worth 0 points each; the hidden cases are worth 5, 10 or 20 points by difficulty, for 95 possible. A candidate who passes all three easy, three of four medium and one of two difficult cases gets 65: "In this example, the candidate earns a total score of 65 out of 95".

Two consequences follow: a solution that handles only the examples can score zero, and slow code loses every test case it cannot finish, which the FAQ shows as a "Terminated due to timeout" status.

What are hidden test cases on HackerRank?

Hidden test cases on HackerRank are the test setter's corner cases and boundary scenarios, with the expected output withheld. When you click Run Code they execute, and you may see your own output and debug output, unless the company turned that off. They carry the points, so they decide your score.

HackerRank's candidate article on hidden test cases says "Hidden test cases include your test setter's corner cases or different scenarios defined to validate your coding solution". On what you can see: "They do not display the expected output of the test case". On running them: "When you click Run code, the hidden test cases get executed, where your output and debug output are displayed".

The same article warns: "Sometimes, your test setter might have disabled the output for hidden test cases". The during-the-test FAQ explains the gap between samples and the rest: "Sample test cases check basic logic. Other test cases often include edge cases and boundary conditions".

What happens when the HackerRank timer runs out?

When the HackerRank timer runs out, the system submits the last compiled version of your code for each coding question. Logging out ends the attempt and submits the latest saved code. Losing your connection does not stop the clock, and the test still ends at the scheduled time.

The during-the-test FAQ says: "If the test ends before you submit, the system automatically submits the last compiled version of your code". On logging out: "If you log out before clicking Submit, the system automatically submits the latest saved code in the editor before ending the test". On connection loss: "The timer continues to run while you are offline, and the test ends at the scheduled time even if you are disconnected".

Save a working version early and improve from there, so the submitted version is one you chose.

Does HackerRank detect plagiarism?

HackerRank runs plagiarism detection on every test by default, comparing your code with others in its database using Moss. Companies can add AI plagiarism detection, which also reads copy-paste activity, tab switching, typing patterns and how the code evolved; when it is on, you must consent before the test starts. Flags go to the company for a human to review.

HackerRank's AI plagiarism detection article says: "Standard plagiarism detection is enabled by default for all tests. It uses Moss (Measure of Software Similarity) to compare a candidate's code against others in our database". For the AI model: "When AI plagiarism detection is enabled, candidates must consent before starting the test". Its signals include "Copy-Pasting: Significant portions of code copied from external sources" and "Tab-Switching: Switching away from the active test tab during execution".

HackerRank is candid about the model's limits: flags are "correct 85% of the time," and "The AI Plagiarism Detection feature currently supports only Coding questions". On writing code elsewhere: for Projects with an offline workflow, "no cheating flag is triggered," but "if candidates solve a standard coding question in an external IDE and copy and paste their code into the HackerRank platform, the system is likely to flag this behavior as suspicious activity".

Copy and paste are also logged without any add-on. The test integrity page says "When candidates copy or paste text, the system records the action automatically," and pasted content appears in your report. And "Tab Proctoring tracks how often and for how long a candidate leaves the test window". The before-the-test FAQ's warning is plain: malpractice "can get captured in your test report and may lead to disqualification from subsequent rounds".

Is a HackerRank test proctored?

A HackerRank test is proctored only if the company turns proctoring on, and the invitation email tells you when it is. The modes run from Secure Mode, which locks the browser to full screen and blocks copy and paste, to Proctor Mode, which adds webcam images every five seconds, screenshots every 15 seconds and AI analysis of both.

The before-the-test FAQ says "Use a web camera-enabled computer to take a proctored test. If your test is proctored, you will be notified in your test invitation email". The test integrity page describes the first mode: "Secure Mode runs tests in a controlled browser environment. It enforces full-screen mode, blocks copy and paste actions, prevents the use of multiple monitors, and alerts when candidates switch tabs".

The Proctor Mode article describes the stricter mode. Before the test, "Candidates review and acknowledge a list of prohibited actions, such as switching tabs or using external tools, and must give consent to proceed". Then "Candidates can continue only if a single monitor is in use," and "The system prompts candidates to share their entire screen". During the test the platform "Captures webcam images every five seconds" and "captures screenshots every 15 seconds".

Clear your desk, close other windows and set up a single screen before you open a proctored link.

How should you practise for a HackerRank test?

Practise for a HackerRank test on its sample test first: 30 minutes, 3 questions, repeatable with a new email address each time. Then solve problems in the language you expect to use, write your own edge-case inputs for each one, and watch the run time, since slow code fails hidden test cases by timeout.

HackerRank's sample test page says "This is a sample test to help you get familiar with the HackerRank test environment," and lists "Test duration 30 mins No. of questions 3 questions". The before-the-test FAQ confirms "You can attempt the sample test multiple times. For every attempt, you must log in with a unique email address".

In the real test, use the run button freely. The during-the-test FAQ says "Running your code does not affect your score". If you write in Java, C# or Scala, the FAQ warns that "you must name your main class Solution". Company guides on this site that name HackerRank include Accenture, Goldman Sachs, Nvidia and Uber.

Can you get extra time or reschedule a HackerRank test?

Extra time, rescheduling and retakes on a HackerRank test all go through the company that invited you, not through HackerRank. The before-the-test FAQ says the platform does not reschedule tests itself. HackerRank says its tests meet WCAG 2.1 AA accessibility standards, and it points candidates with other needs to the hiring team.

The FAQ states that "The HackerRank platform does not support rescheduling tests directly," and that the hiring company manages those decisions. On timing, "You can take the test during the time window mentioned in your invitation email". On accessibility, HackerRank "complies with the WCAG 2.1 AA standards to make the content accessible to a broader range of candidates with disabilities". None of the pages opened for this guide publish an extra-time process, so ask the recruiter before the window opens.

What happens after you submit a HackerRank test?

After you submit a HackerRank test, your attempt goes to the hiring team for review, with or without a confirmation email. HackerRank's candidate pages do not say whether you will see your score; that is the company's choice. Questions about the questions themselves go to the hiring team.

The after-the-test FAQ says "Whether or not you receive an email confirmation, your test is submitted once you click Submit or when the timer runs out". And: "Once you click Submit, your submission is automatically sent to the hiring team for review". For problems with a question, it says to "contact the hiring team directly".

Other screens that often sit beside a HackerRank test have their own guides: the Codility test scores in a similar hidden-test way, the CCAT test is a timed aptitude test, and pymetrics games measure traits. Employers' published rules on AI during tests are collected in employer AI interview policies.

For the interview that follows, the software engineer interview questions page covers what interviewers listen for, and the free interview questions tool takes the job posting and the round and lists likely questions. Prept's Mock room lets you answer out loud on a clock and scores each answer out of 10.