Does HackerRank Record Audio During a Test?

HackerRank's documented test proctoring does not list microphone access. As of September 9, 2026, the Proctor Mode documentation asks candidates for webcam and screen-sharing permissions and never mentions a microphone; Secure Mode and default tests request neither. The feature HackerRank calls "conversation detection" is a pattern in the code editor, not audio monitoring. Audio does enter the picture in HackerRank Interview and Chakra, because those formats are conversations. This article separates the two.

What Proctor Mode asks for

HackerRank's Proctor Mode documentation, last updated July 22, 2026, lists two permissions a candidate must grant to start: "Webcam access: Allows the system to monitor and record the candidate through the webcam during the test" and "Screen sharing access: Allows the system to monitor the candidate's screen activity during the test." There is no third line for a microphone.

The same document describes "Conversation detection in the code editor: Detects patterns where candidates type and delete content in the editor that may indicate external communication." The name suggests listening. The definition describes typing. It is a heuristic over editor keystrokes, the same signal family HackerRank's plagiarism model uses, and it does not require a microphone.

Webcam capture in Proctor Mode produces still images, not a video stream with sound. HackerRank documents that the system "captures webcam images every five seconds" for tests that include candidate personal information. Snapshots carry no audio.

What Secure Mode and default tests capture

Secure Mode stays inside the browser. HackerRank's Test Integrity overview says it "enforces full-screen mode, blocks copy and paste actions, prevents the use of multiple monitors, and alerts when candidates switch tabs." No webcam, no screenshots, no microphone.

A test with no integrity mode enabled still runs HackerRank's default tracking: copy-and-paste tracking and tab proctoring, which "tracks how often and for how long a candidate leaves the test window." Neither touches audio.

A browser cannot open a microphone silently. If a HackerRank test wanted audio, Chrome or Edge would show a permission prompt before the test began. The absence of that prompt on the setup screen is a reliable indicator for browser-based modes.

What the desktop app documents

Desktop App Mode runs outside the browser, so browser permission rules no longer constrain it. HackerRank's candidate setup guide lists the permissions it requests: webcam access, screen sharing, and on macOS additionally Screen Recording, System Events, and Accessibility.

One detail confuses people. On macOS 15 the operating system labels the screen-capture permission "Screen & System Audio Recording." That is Apple's name for the permission category, not a statement by HackerRank that it records audio. HackerRank's Desktop App Mode documentation describes webcam images every 15 seconds, full-screen recording in Session Replay, and application blocking. It does not describe microphone capture.

The honest boundary: audio recording in the desktop app is not documented, which is not the same as documented to be absent. A native application can request the microphone at any time, and the OS will show its own prompt and indicator when it does.

Where audio is recorded: Interview and Chakra

HackerRank Interview is a live call with an engineer. Chakra is HackerRank's autonomous AI interviewer, and it speaks with you. In both, audio is captured because the format is a conversation. The question there is not whether audio exists but what is kept and scored. What HackerRank's Chakra AI interviewer records covers that format, including its desktop-app requirement.

If your invitation is for a timed coding test, you are in the proctoring family described above. If it is for an interview link with a scheduled time or an AI interviewer, expect audio.

How to verify before the timer starts

• Read the setup screen. Browser modes list every permission; a microphone request would appear there.
• Check the OS. macOS shows an orange indicator when any app uses the microphone, and Privacy & Security lists which apps have access. Windows shows a microphone icon in the taskbar and lists access under Settings, Privacy, Microphone.
• For the desktop app, review the permissions it requests on first launch and decline anything the documentation does not explain, then ask the recruiter.

For a cross-platform comparison, which coding assessments record audio covers CodeSignal, which does document audio capture, alongside HackerRank. For the full list of what each HackerRank mode collects, see what HackerRank proctoring detects and records.

What this means for candidates

For a HackerRank test, the documented capture is your screen, your webcam as still images, and your editor activity. Your microphone is not on that list. The webcam question has its own rules by mode, covered in when HackerRank uses your camera.

Treat the consent screen as the authority for your specific test. If a permission appears that the rules do not explain, ask the recruiter in writing before you start rather than guessing what it is for.