Does HackerRank Detect Multiple Monitors?

Yes, when the employer has enabled Secure Mode, Proctor Mode, or Desktop App Mode. As of September 9, 2026, HackerRank documents a monitor check before those tests start, lets the test continue only when a single display is in use, and in Proctor Mode and Desktop App Mode keeps verifying during the session. A HackerRank test that uses only the default tab and copy-paste tracking has no documented monitor check at all.

So the useful question is not whether HackerRank can detect a second monitor. It is which check runs on the specific test you were sent.

Which HackerRank modes check for a second monitor

HackerRank's Secure Mode documentation says the mode "Detects the use of multiple monitors and allows candidates to continue only if a single monitor is in use". The onboarding flow it describes includes granting permission for monitor verification and confirming a single-monitor setup before full-screen mode launches.

The Proctor Mode documentation adds a second check that runs for the whole session: "The platform continuously verifies that only one monitor remains connected. It flags any new monitor connections made during the test". Plugging in a display halfway through is logged, not just blocked.

Desktop App Mode goes furthest. HackerRank's Desktop App Mode documentation says the app detects and flags "multiple monitors and screen mirroring", and that when extra displays are found, "Candidates must disconnect them to continue".

How a web page can tell you have two screens

Secure Mode and Proctor Mode run inside a browser, and a browser cannot see your desk. What it can read is a single bit exposed by the Window Management API, Screen.isExtended, which reports whether the desktop spans more than one display and requires no permission prompt. Counting displays or reading their layout needs a further call that does prompt, which is the likely source of the "monitor verification" permission in HackerRank's onboarding.

HackerRank does not document which API its check uses, so that mechanism is an inference from what a page is able to observe, not a HackerRank statement. The specification detail and the differences between a page, a screen share, and a native app are covered in what a coding interview can learn about a second monitor.

Desktop App Mode is not a page. It enumerates displays through the operating system, which is why it can also distinguish a mirrored display from a single one.

What counts as a second monitor

The check is about what the operating system reports, not what you are looking at.

• A laptop screen plus an external display is two displays. Either unplug the external display or run the laptop closed so the OS reports one, then confirm in your display settings before starting.
• A display that is connected but switched off can still be enumerated on many setups. HackerRank's instruction is to disconnect, not to power down.
• An iPad used as a Sidecar display, an AirPlay receiver, or a wireless display counts while it is connected.
• Virtual display drivers and dummy plugs present as real displays to the OS.
• Mirroring is documented as flagged only in Desktop App Mode.

What the check cannot see

HackerRank is candid about the limits of browser-side monitoring. Its own article on tab proctoring lists what that layer misses: "Smartphones, tablets, or additional computers used for research", printed material, and "Help from other people in the room" (HackerRank, Tab-Proctoring: What It Catches and What It Misses). A second computer is not a second monitor, and no display check detects it.

That is exactly why the monitor check is one layer among several. Proctor Mode adds screenshots and webcam analysis, and Desktop App Mode adds webcam checks for phones and, where available, gaze analysis. The full list by mode is in what HackerRank proctoring detects and records.

What a monitor flag does

A detected display at setup stops you from starting until it is removed. A display connected mid-test in Proctor Mode or Desktop App Mode is logged as an integrity event with a timestamp and appears in the recruiter's report, where the session is rated High or Medium for integrity. HackerRank documents no automatic submission or termination for it, and it does not notify the candidate. The recruiter decides what the event means.

What this means for candidates

Handle the display question before the timer, not during. Unplug external displays, end any Sidecar or AirPlay session, and check that the OS lists one display. The monitor check happens on the setup screen, so a problem there costs nothing but time; the step-by-step HackerRank proctored test walkthrough shows where in the flow it appears.

If a dock or cable reconnects a display by accident during a Proctor Mode test, note the time and tell the recruiter afterward. A logged event with an explanation reads differently from a logged event with silence.

If your invitation does not mention Secure Mode, Proctor Mode, or a desktop app, the test probably has no monitor check, but the rules on the consent screen still govern what you may use. Read them before deciding whether a second screen is allowed rather than whether it is detected.