In the standard configuration, no. HackerRank does not stream or record video of your desktop. What a test can be configured to do is take still webcam snapshots, log every time the browser tab loses focus, flag pasted code, force full screen, and in the strictest setup lock you into a controlled browser environment. Those are separate switches an employer turns on individually, and you can work out which ones you were sent before the timer starts.
The switches an employer can flip on a HackerRank test
Proctoring on HackerRank is not one setting. It is a small stack of them, and most tests sit near the bottom of the stack rather than the top. The useful question is not "is it proctored" but "which of these is on", because they capture very different things.
| Tier | What it physically captures | What it cannot see | The tell before you start |
|---|---|---|---|
| 1. Nothing enabled | Your submissions, per-question timestamps, and the editor's own typing timeline | Anything outside the test tab. No camera, and no focus events surfaced to the reviewer | Invite mentions duration and question count only, with no camera or rules language |
| 2. Activity and focus logging | Browser blur and visibility events: that the tab lost focus, at what time, for how long, how often. Paste events into the editor, with size | Which app or tab you moved to, the contents of that window, or anything on a second monitor | Instructions tell you not to navigate away, and a warning banner appears the first time you leave the tab |
| 3. Webcam image proctoring | Still frames from your webcam at intervals, pulled through the browser's ordinary camera API. Often one photo at the start | Your screen. The camera faces you and the room, not the display | A browser camera permission prompt, a live preview of yourself in the device check, and the camera indicator light |
| 4. Full-screen enforcement | Nothing visual. It uses the browser's Fullscreen API and logs each exit from full screen | What you did while out of full screen, or anything drawn by another application | Clicking Start throws the browser straight into full screen, and pressing Escape produces a warning plus a counted event |
| 5. Secure or lockdown mode | Your environment. It restricts what the session permits, blocks pasting in from outside, and may check for extra displays or a virtual machine | Varies by configuration, and you should assume the boundary is wider than you can verify | The invite warns you in advance, because it needs setup: a specific browser, an extension, or a download |
| 6. A bolted-on third-party proctor | Whatever that service does, which commonly does include continuous screen and webcam recording | Assume nothing is out of scope | The invite names a second product, or you install software before the HackerRank link will open |
Tier six is the only one where "HackerRank is recording my screen" is a fair description, and even then it is not HackerRank doing it. That distinction matters when you are reasoning about one specific invite sitting in your inbox rather than about the platform in the abstract.
Three checks that tell you which tier you were sent
None of this is hidden from you. A camera cannot be switched on inside a browser without asking, and a test that enforces rules has to state them. The information is sitting in three places you can read before the clock starts.
Read the invite email, not just the button
The invite carries the duration, the question count, and normally a line about proctoring. Search it for proctor, webcam, camera, full screen and browser. If it names a second product or asks you to install anything, you are at tier five or six and everything below is academic. An invite that gives you a link, a window of a few days and nothing else is usually tier one or two.
Read the instructions page while the timer is still stopped
Between the link and the first question there is a page listing the rules for that specific test, and the clock has not started. A proctored test says so here. This page is per-test rather than boilerplate, so it beats anything you read on a forum about how HackerRank "usually" behaves. Read all of it, including the sentence about what happens if you leave the window.
Watch the device check and the first ten seconds after Start
If the system check asks for your camera and shows a preview of your own face, snapshots are on. No permission prompt and no preview means no webcam capture, because a browser cannot hand over a frame silently. If clicking Start pushes you into full screen, enforcement is on. Check the camera indicator light as well: it is a hardware signal that does not depend on trusting the page.
What the recruiter actually receives
The report is less cinematic than people imagine. For tiers one and two it is a score, your code, per-question timing, and a short activity summary: how many times the tab lost focus, roughly how long for, and whether large blocks of code arrived as pastes rather than keystrokes. The editor keeps a typing timeline, which is why a 300-character function that appears in a single event reads differently from one typed over four minutes. Similarity and plagiarism checks run on the submitted code after the test, not during it.
With image proctoring on, the reviewer additionally gets a grid of webcam stills. It is a set of photographs, not a video, and nobody is watching live. Reviewers tend to open it only when something else in the report already looked odd, such as a perfect score submitted in four minutes.
One honest caveat: HackerRank changes its product, and enterprise accounts can be configured in ways the public documentation does not spell out. Treat the tiers above as the shape of the system rather than a guarantee about your particular invite, and let the instructions page be the authority.
Screen-capture exclusion does not apply here, and it is worth being blunt
Because this site publishes a Windows overlay excluded from screen capture at the operating-system level, we get asked whether that property helps on a HackerRank test. Capture exclusion removes a window from the screen-capture pipeline: screen shares, recordings, screenshots. That is the whole of it. It has no effect whatsoever on a webcam feed, because the camera points at your face and your room, and no compositor setting changes what a lens sees. It has no effect on a lockdown browser, because secure mode governs what your test session permits rather than how the desktop is composited. And it does nothing about the oldest signal of all, which is a person watching your eyes track back and forth across something they cannot see.
So on a tier three, four, five or six HackerRank assessment, the answer is that OfferPilot AI is the wrong tool and using it would breach rules you accepted on the instructions page. We would rather write that plainly here than have you find out halfway through an assessment that matters.
Where a coding copilot is genuinely useful
Before the assessment, not during it. HackerRank rounds draw from a predictable pool of patterns, and the usual gap is recognising which pattern a problem belongs to fast enough to leave time for edge cases. That is a practice problem.
- Working through problems on your own time. Code Copilot screenshots a problem with
Ctrl+Alt+S, handles a statement that spans several scrolls, and returns the intuition, a dry run and the Big-O rather than a block of code you could not defend in a follow-up. The intuition is the part that transfers to test day. - Rounds where assistance is explicitly permitted. Some take-home and pair-programming rounds state outright that documentation and tools are allowed. That is a different situation from a proctored assessment, and the rules of your round decide it, not the software.
- The conversation afterwards. A HackerRank pass usually leads to a call where someone asks you to walk through your solution and defend a trade-off. The company Q&A generator builds a question bank for that company and role, which is preparation you do days in advance.
The short version
HackerRank is not filming your desktop unless somebody deliberately added a service that does. It is far more likely to be counting tab switches, watching how code arrives in the editor, and possibly photographing you through a camera you granted permission to. All of that is visible before you click Start, provided you read the invite, read the instructions page, and watch what the device check asks for.
Related guides
- Does HackerEarth Use Your Camera? Every Proctoring Toggle
- What Recruiters See in Your HackerRank Report: Field by Field
- Does HackerRank Record Your Screen? What Each Test Mode Captures
- How Strict Is CodeSignal Proctoring? Six Channels, Ranked
- Can HackerRank Detect Copy and Paste? What the Report Shows