Does the Amazon HackerRank assessment use your camera?

You want a straight answer before you click start, and the honest one carries a condition. This section explains who controls the camera setting and how to find out what your own test does. It comes down to a per-assessment configuration plus a browser permission you can observe directly.

HackerRank is assessment software that Amazon, like many employers, sends candidates through. Proctoring options such as webcam image capture live in the test configuration, and the hiring team turns them on or off for a given assessment. Two candidates at the same company in the same week can see different behavior because they were sent different tests for different roles.

So the useful question is not what Amazon does in general. It is what your specific invitation is set to do, and that is knowable before the timer starts.

Browsers do not let a page open your camera silently. Access requires an explicit permission prompt, and you can inspect or revoke it in site settings. That makes the permission model a reliable signal rather than something you have to guess at.

• No camera prompt, no capture. If the instructions screen and system check never ask for the camera, webcam proctoring is not enabled for that assessment.
• A prompt plus a preview. If HackerRank shows your webcam feed during the system check, image proctoring is on and snapshots will reach the report a reviewer reads.
• The invitation email. Assessment invitations state the requirements, including whether a working webcam is needed.
• Site permissions. Your browser's address bar shows which permissions the page currently holds while the test runs.

Denying the camera on a test that requires it will usually stop you from starting, so treat the prompt as information rather than a switch to flip. If you plan to test the flow, do it on a practice problem rather than on the timed assessment.

Camera off does not mean nothing is measured. Code similarity scoring compares your submission against other submissions and public sources regardless of proctoring settings, and the test page can log its own focus changes and paste events. Amazon assessments for engineering roles also frequently pair the coding portion with non-coding sections such as a work styles questionnaire and a work simulation, which are scored on consistency rather than watched.

Consider a new-grad candidate scheduled for an Amazon assessment for a software engineering role. They spend the evening before worrying about the webcam and skip rehearsing how they would explain a solution out loud. The camera never turns on, and the follow-up interviews with people are where the decision actually gets made. Running a few timed rounds on the mock interview page would have been the better use of that evening.

A proctored assessment is not a place for a live assistant, and SubcueAI is not designed for one. When a test can capture your screen and your webcam under terms you accepted at the start, no tool can honestly claim to belong there. Aaron Cao, founder of SubcueAI, has kept live assist scoped to conversation for that reason: the product targets interviews you talk through, not exams you are monitored during.

The live interview case works differently. On macOS and Windows the desktop app captures system audio together with your microphone and shows suggestions in a floating local overlay. The browser extension's Side Panel does live assist from the meeting tab's audio only, so it hears the interviewer and never your microphone. In both cases no bot joins the call and nothing is injected into the meeting page. The boundaries, including screen share, recording, and company-managed devices, are worked through across the detectability topic hub.