What Happens When a Candidate Turns the Camera Off

Camera turned off during a HireQwik interview is a pause, not a guess. On a staging call I clicked the camera control to see whether the agent would keep taking answers from a dark frame. It did not. The microphone dropped, a box titled Camera Turned Off covered the screen, and the text said this was warning 1 of 3 and that the interview was paused until the camera came back.

I am writing the rule down because teams hear “the candidate went quiet” and invent three different causes. Sometimes the person is thinking. Sometimes the line died. Sometimes they flipped the video control and the product did exactly what it says on the box. This page is that box. A campus lab has its own mess in how a drive handles a camera that will not stay on. The sentence for the invite is in the invite wording for the camera. What the pause means for the score, and what HR should do when a candidate writes in, are both further down this page.

Key takeaways

• The pause starts when the candidate uses the in-call camera control, after they have joined.
• The mic mutes. The box remains until they choose Turn On Camera.
• The first three pauses leave the room open. Only the fourth shutoff closes it.
• This box does not vanish on a timer.
• Join itself is refused until a camera is allowed.
• A thumb over the lens is not this pause. The product counts the toggle, not the picture.
• The pause is not a score change, and it is not a rejection.
• What HR should do depends on which screen the candidate is looking at.

What the Camera Turned Off box tells the candidate

The title is Camera Turned Off. The body tells them the camera has to stay on, names which pause this is, out of three, and says the session is held until video returns. It also says that going past those three pauses ends the session. The only button is Turn On Camera.

People squash the two halves. The number on the box is how many pauses they have used. The ending is a later event. Pause number three is still a hold they can leave. The room drops the next time they switch video off, not when the third box appears.

This box waits. It does not clear itself while they look away. A different warning on the same product can disappear on its own. This one cannot. If you need that other warning, it lives in the page-hide rule on a live call. Here, the screen stays covered until video is enabled again. There is no “I’ll deal with it in a minute” that still leaves them audible. They are not audible.

Before they ever reach that box, the lobby carries a short notice that the session is recorded on video and that the camera stays on for the whole conversation. Hiding the browser tab, or switching video off, can lead to warnings and a stop. The first three camera toggles hold the room. They do not close it.

Why the microphone goes quiet when the camera is off

The pause is mechanical. Turning the camera off from the in-call control mutes the microphone in the same step and marks the candidate as not listening. The agent cannot take a new answer from them, because there is no live mic to take it from.

The reason for that design, and it came from a failure we already shipped once. Early on, a camera that dropped produced a short notice and then the call continued with video disabled. People learned the trick in a single attempt: drop video, stay audible, and glance at notes the webcam could not catch. Advice that leaves the mic open is easy to ignore. A hold that closes the mic is not.

The pause is not a punishment measured in seconds. We do not add a mark for how long they take to find the button. We count the shutoff. A candidate who needs twenty seconds to click Turn On Camera has used one pause, not twenty. A candidate who flips the camera off, on, off, on, is spending the count, even if each dark stretch is brief.

I will not claim the on-screen clock freezes. The thing that stops is the answer. If your team tells candidates “the timer pauses too,” you are adding a promise the overlay does not make. Tell them the true promise: speech stays blocked until video returns, and the box will not leave on its own.

How Turn On Camera puts the interview back

Turn On Camera does three things together. It enables the camera. It unmutes the microphone. It clears the box. The call underneath is the same call. They have not been sent to a new link, and they have not been scored for the pause.

There is a second way back. If the camera control itself is used to switch video on while the box is showing, the mic unmutes and the box clears as well. Either path is a resume, not a restart. The count does not reset to zero. The next shutoff is warning 2, or 3, or the end.

Candidates miss this and message a recruiter mid-pause: “It froze, send a new link.” A new link is the wrong fix while the box is still up. The fix is the button on the box. Say that in the reply, in one line, and tell them not to keep typing on their phone if the interview is on the laptop. The phone is a distraction. The button is the resume.

If the button fails because the browser has dropped permission, they are no longer in a pause they can click through. They are in a device problem. The page before join already knows that case: Retry Camera Access. Mid-call, if the device is gone, they may not get a clean resume. That is a reason for your team to offer another slot later, which is a hiring decision, not something the box does by itself. The steps for that decision are further down.

Why the fourth camera shutoff ends the call

On the fourth shutoff, HireQwik marks the meeting finished, stores the reason as the camera, drops the room, and shows an end screen.

The heading says the interview is over. The paragraph underneath is about the camera specifically: video was required, it was switched off too many times, and the copy invites them to email the hiring team if the cutoff felt mistaken. It is not the paragraph used when someone hides the page. If their screenshot talks about tabs and the record says the camera, trust the record.

There is no extra box and no grace period. The session has already closed. We skip the feedback form. A call we cut off is a bad moment for a survey.

The fourth shutoff is blunt because the earlier, softer behaviour taught the wrong lesson. Three recoverable holds, then a real stop, is something a coordinator can say out loud. It is still a blunt instrument. It cannot see the motive. A dead webcam and a deliberate black frame spend the same count. You add the motive later, from whatever speech exists before the stop, or you say you do not know and offer another time.

The stop does not assign a verdict. A tiny conversation is filed as unfinished. Sparse replies stay sparse: the evaluator is told not to invent a comfortable midpoint. A long conversation that dies on that fourth shutoff can still be read. Neither outcome is an automatic rejection.

You cannot start the HireQwik interview with the camera refused

The pause is an in-call event. The join screen is stricter. People mix the two up.

When the meeting page loads, it asks the browser for a camera and shows a preview. The request is a normal browser prompt. Mozilla’s notes on getUserMedia describe the three outcomes that matter here: allowed, denied, or no device. HireQwik maps those into plain lines.

If the person blocks the prompt, the page says camera access was denied and that they must allow it in the browser settings to proceed. On Chrome, that Block choice is changed in site settings for the camera, which Chrome’s camera and microphone help walks through, including the case where a school administrator has locked the setting. If the machine has no camera, the page reports that it found none and asks them to plug one in. A button labelled Retry Camera Access runs the check again. Until it succeeds, and until the slot time has arrived, Join stays grey and the label reads Camera Required to Join.

So there is no “I’ll do this one on voice only.” The audio-only path was the hole we closed. A candidate who cannot produce a picture does not enter the call, which means they also do not burn a pause count. The count starts after Join. A denied prompt on the lobby screen is a locked door, not warning 1 of 3.

Tell them that before the slot, next to the rest of how candidates should prepare. A student who hits Camera Required to Join in a lab with the webcam unplugged will call the link broken. It is not broken. The preview failed. The cell’s job, the day before, is to say the link will ask for a camera and will not open without one. That briefing is the campus page. The sentence itself is short enough to paste, and the paste lives in the candidate note linked above.

A covered lens is not Camera Turned Off

This limit will annoy anyone who wanted the box to mean “we saw you cheating.” The box does not mean that.

The counter moves when the camera control is switched off. It does not inspect the pixels. The Media Capture and Streams specification describes a disabled camera track as one that stops delivering real pictures. HireQwik does not grade those pictures. It counts the control. A thumb on the lens, a sticker, a book in front of the webcam, a virtual background that hides the room: if the track is still enabled, this pause does not fire. We do not run gaze tracking, and we do not claim to. A dark picture with the camera still “on” is a recording your reviewer can watch. It is not an automatic pause.

The other direction matters too. A candidate can switch the camera off for a boring reason: the preview looked wrong, they were hunting a blur setting, the laptop asked which device to use and they clicked the control by reflex. All three count as a pause if they used the toggle. Nothing in the product calls that an accident. You will, after you listen, or you will admit you do not know.

Because the camera count and the page-hide count are separate, a couple of camera pauses plus a couple of page hides do not end the room. Each counter reaches its own end on its own fourth event. Keep the two counts in separate columns. A homemade sum was never the rule we shipped.

Does turning the camera off change the interview score?

No. The pause stops the answer. It does not subtract points. The interview score and the verdict come from what the candidate said, and a camera stop never triggers an automatic reject. A fourth shutoff closes the call, but closing a call is not a rejection: a very short conversation is filed as unfinished, and a long one can still be read.

We could have docked points every time the count rose. That would have looked decisive in a demo and been the wrong instrument: a hidden penalty on a toggle that a nervous candidate or a lab PC hits by accident. The hold already stops the dark-frame trick while it is happening, so the score can keep meaning one thing, which is what they said.

The saved record keeps how many times video was switched off, how often the browser tab went away, and the reason if this rule ended the call. A later save cannot shrink a count the server already kept, and reloading the page does not zero it.

The count shows up in one more place: the AI-assist flag, a separate 0 to 100 signal computed after the call from answer timing, how the speech sounds, and the proctoring counts. Camera-off is its lightest input. It fires only when video went off at least twice, and it adds 5 points however many times it happened. The flag reads elevated from 35 and high from 65, so camera stops alone can never raise it. A 5 matters only next to louder signals, such as long pauses before every answer or delivery that sounds recited, which we cover in spotting chatbot help on the call.

So keep it out of your spreadsheet too. A reviewer who types “-1 camera” next to a 7.4 has started a second grading system that nobody can explain at offer stage. If the pattern worries you, the defensible consequence is a live round with a person, not an edited number.

What HR should do when a candidate writes in

The words on their screen pick the remedy. Ask them to read the largest heading before you reply, then sort the ticket into one of three lines.

1. Camera Turned Off, with a Turn On Camera button. They joined, video is off, and the room is still open. Send one message and stop typing: “This interview is still open. Video is off, so the microphone is silent. Use Turn On Camera and stay on this window. Do not open a second link.” More chat bubbles pull them onto their phone and away from the interview.
2. Camera Required to Join, sometimes with Retry Camera Access. They never started, and nothing was counted. Send the camera permission steps for their browser, or ask them to plug in a webcam. If the slot has passed, book the new time first and explain later.
3. The interview is over, and the message mentions the camera. The fourth shutoff fired, and you are now a reviewer, not a helpdesk. Open the record in the HR dashboard and check how much was said before you read anything else.

For closed calls, write a lane on the record so the next recruiter does not reopen the argument:

• Restore. Little or no speech: a lobby lock or a stop in the opening minutes. Offer one more slot and resend the camera paragraph from the invite note for the camera.
• Read. Most of the conversation exists. Listen around the stops. One early pause followed by a normal conversation stays in the normal queue. A pause before every answer, with video back only for a polished stretch, is a reason for a live round with a person.
• Unsure. Say unsure, and take the live round. Do not upgrade it to “caught” because a manager is waiting.

Two attempts, then a decision. Do not grant a private audio-only exception: the moment it is forwarded, it is the policy. And answer the same day, live pauses first. A candidate who sits in a silent pause for twenty minutes remembers the silence, not the rule.

If you want this pause, the join lock, and the end screen shown on a role you actually hire for, book a demo. We will disable video, bring it back, and read the record together.