What Tab Switch Detected Means on a HireQwik Call

Tab switch detected on an AI interview is a strike counter, not a guess about cheating. On a staging call in August 2026 I left the HireQwik interview tab to read a log line. When I came back, the overlay said Tab Switch Detected, warning 1 of 3. I did it three more times on purpose. The fourth time, the room disconnected and the screen said Interview Terminated.

That is the whole rule. I am writing it down because the sentence on the overlay is easy to misread, and because a recruiter who only hears “the interview ended” cannot tell a search for answers from a student who alt-tabbed to silence a notification. This post is the mechanism. Later pieces cover the invite line for candidates, a call that has already been cut off, and why the same count does not move the score.

Key takeaways

• The browser reports the page as hidden. HireQwik counts that. It does not read the other screen.
• Warnings 1, 2 and 3 show an overlay. The call stays live.
• The fourth hide ends the interview immediately.
• The overlay closes itself after five seconds, even if the candidate is still away.
• Camera-off uses a separate counter. Mixing the two does not add up to an end.
• Ending the call is not a verdict. The score, if one is produced, is a later step.

What Tab Switch Detected shows the candidate

The overlay title is Tab Switch Detected! The body says the candidate switched away from this tab, that this is warning N of 3, and that after 3 warnings the interview will be ended immediately. A button says I Understand.

That copy is doing two jobs at once, and they fight each other if you only skim it. “Warning N of 3” sounds like the third warning is the last event. “After 3 warnings” sounds like something else happens later. Both are true, and the second one is the one that matches the code. The third warning is still a warning. The interview ends on the next hide after that, not on the click of I Understand.

Before the candidate even joins, a notice on the join screen is titled Proctored Video Interview. It says the camera must stay on, and that switching tabs or turning the camera off will trigger warnings and may lead to automatic termination. “May” is the honest word on that screen. The first three hides do not terminate anything. The fourth does, every time, with no extra judgement in between.

I have watched people treat the overlay like a pop-up ad. They click through and keep working in another window. The click does not reset the counter. It only hides the box. The next hide is strike two, or three, or the end.

How HireQwik counts a tab switch

The listener is the browser’s Page Visibility event. When the interview page becomes hidden, the counter goes up by one. Mozilla’s documentation of visibilityState describes hidden as the page not being visible at all: a background tab, a minimized window, or a locked screen. The Page Visibility spec is the standard behind that report. HireQwik does not add a second detector on top of it.

A few consequences follow, and they surprise people who picture a “tab” as only the strip of tabs in Chrome.

Leaving for another browser tab counts. Switching to another app usually counts, because the interview page is no longer the visible page. Locking the laptop counts. Minimizing the window counts. The product does not know which of those the candidate did. It knows the page was hidden, and it knows how many times that happened after they had joined.

It does not count before they join, and it does not count after the call has already ended. A candidate who opens the link, reads the notice, and flips to their email before pressing Join is not burning strikes. The counter starts once they are in the call.

It also does not see what they looked at. There is no screen recording of the other tab, no list of sites, and no gaze tracking. A hide is a hide. Searching the job description and checking a calendar invite look the same to this counter. That is a limit, not a bug in the count. If you need a picture of what the person did, you will not get it from this signal. You get a number, and you get the recording of the call itself.

One more limit, and I would rather write it here than have a recruiter discover it in a complaint. The warning auto-dismisses after five seconds. That timer runs even while the candidate is still on the other tab. We logged this in August 2026. The interview page was left as it was, so the warning can vanish before they look at it. Enforcement did not change: three hides are tolerated, and the fourth ends the call. A candidate can therefore burn a strike they never read. The pre-join notice and the invite are the places that sentence has to live, which is why the candidate briefing is its own page and not a footnote.

Why the fourth hide ends the HireQwik interview

On the fourth hide the client tells the server the meeting is over, marks the reason as a tab switch, disconnects the room, and replaces the call with an end screen.

The end screen title is Interview Terminated. The message says the interview ended because of a proctoring violation, that switching tabs or windows during the interview is not permitted, and that the candidate should contact the recruiter if they believe this was an error. The usual “thank you, we will review the conversation” screen is not what they see. The short feedback form that follows a normal ending is not offered either. We do not ask someone to rate an interview we just cut off.

The room disconnect is immediate. There is no fourth overlay and no ten-second countdown. If they were mid-sentence, that sentence stops. The transcript holds whatever was said before the disconnect. It does not hold a tidy closing question.

I chose a hard stop on purpose, and I still think the alternative is worse. A soft warning that never ends the call teaches people the warning is theatre. We already had that failure mode on camera-off, before April 2026: a short toast, then the interview carried on with the camera disabled. Candidates learned to flip the camera and keep talking. The tab-switch rule was already a three-then-stop rule by then, and it was the pattern we copied when we made camera-off match it. A warning with no consequence is a suggestion. A warning with a published stop is a rule.

The stop is still crude. It cannot tell a cheat from a mistake. It can only make the fourth hide expensive enough that casual searching has a cost, and loud enough that your team can see it happened. What you do with that fact is a hiring decision. The software does not turn it into a No Go by itself. I will come back to that, because it is the mistake I most want to prevent.

The five-second timer on the tab-switch warning

The overlay has two ways to close. The candidate can press I Understand. Or five seconds can pass.

Five seconds is long enough to read the title if you are looking at the page. It is not long enough if you are in another app, which is exactly when the warning appears. So the person who most needs the text is the person least likely to be there for it.

What they often see instead is the aftermath. They return to a call that is still going, with no box on screen, and they do not know a strike was used. Or they return to Interview Terminated and the only explanation is the end-screen paragraph. Both are bad moments. The first one burns trust in the warning. The second one burns trust in the process, especially if nobody told them the rule before the link arrived.

If you are writing the candidate email, do not rely on the overlay as the teacher. Say the rule in the email in one plain sentence: remain on that page, three warnings, one more departure ends the call. Point them at the join-screen notice so the email and the product say the same thing. We put a fuller version of that note in the briefing post, including what “leaving the page” covers on a phone.

For your own team, the practical read is this. A candidate who says “I only saw one warning and then it died” can be telling the truth. Strikes two and three may have fired and cleared while they were away. That story is not proof they were honest, and it is not proof they were cheating. It is a reason to look at the count and the recording before you decide, which is the same habit we want on an interview that has already been cut off.

Tab switch and camera-off are separate counters

HireQwik runs two strike counters during the call. They do not share a total.

The tab-switch counter is the one this post is about. It does not mute the microphone. The agent can still be talking, and the candidate can still be heard, while the warning is up. If they wander off and come back within the three warnings, the conversation has continued underneath.

The camera-off counter is the other one. Turning the camera off mutes the mic and puts a blocking overlay on the screen until the candidate turns the camera back on. The interview is paused in a real sense: they cannot keep answering with the camera dark. That overlay does not use the five-second dismiss. It stays until they press Turn On Camera. Warnings are still 1, 2 and 3, and the fourth camera-off ends the call with different copy, about the camera being turned off repeatedly.

Because the counters are separate, two tab hides plus two camera-offs do not end the interview. Each side needs its own fourth strike. A candidate can be sloppy on both and still finish, as long as neither side reaches four. I would not call that a comfortable finish. I would call it the rule we actually shipped, and your team should know it so you do not invent a combined “five violations” policy in a Slack thread.

The stored record keeps them apart as well. When the call ends, the client sends a tab-switch count, a camera-off count, and, if the end was this rule, a reason string: tab switch or camera off. The server will not accept a lower count than it already stored for that meeting, so a refreshed page cannot wipe the number back to zero. Ending the meeting still succeeds even if the extra fields are junk. We learned that the hard way: a bad counter once blocked the end request entirely, and the meeting sat open. The end is the important part. The counters ride along.

What HireQwik stores, and what it refuses to decide

You will not get a screenshot of the other tab. You will get the counts, the end reason when the rule fired, the transcript of what was said before the cut, and the recording of the call.

That package is enough to ask a better question than “did they cheat?” The better question is “do we have a fair sample of this person, and do we owe them another slot?”

A call that dies in the first couple of minutes is not a completed interview. HireQwik will not mark a call completed when it is under two minutes or under three transcript turns. It is marked incomplete instead. If the candidate managed fewer than six speaking turns, the later scoring step is told the interview was incomplete: score zero where there is nothing to score, do not invent a middle score, and note that it ended early. A cutoff at minute twelve, after a full set of answers, is a different object. There is a conversation to read. The ending is ugly, and the answers may still be usable.

Neither case is an automatic reject. The tab-switch end does not write No Go. We talked about a “needs another interview” outcome and did not build it. So a terminated call can sit in your queue looking like a normal record with a short transcript, or like an incomplete one, and your team has to notice the reason. If you only sort by verdict, you will mis-file these people. Open the record. Look at the count. Listen.

The count also feeds a separate check that runs after the call, the AI-assist band. That check can light up when someone left the page, among other patterns. It is a flag for a person to verify. It does not edit the mark. I will leave the weights for the other page. The split between flag and points is laid out in the flag beside the score. Mixing the two is how a warning system turns into a silent punishment, which is the outcome we refused.

What a recruiter should do the day a call ends this way

Open the candidate on the HR dashboard. Read the length of the transcript before you read the complaint. A fragment is not a finished screen: book another slot or say plainly that you will not. A long conversation can be reviewed on the answers you have. Play the seconds just before the disconnect. A search tends to leave a gap and then a tidy paragraph. A trackpad accident does not.

The end screen already told them to contact you if they think it was an error. Answer. Silence is how a student decides the system failed them. The piles, the reply wording, and the mistakes teams make the morning after are in what to do once the AI interview has ended. Tell your own team the policy in one message so nobody invents a harsher one overnight: three warnings, one further departure stops the session, the score is a separate step, camera-off is a separate counter.

What this rule will not catch

A second phone on the desk, with the answers on it, never hides the interview page. The counter stays at zero. A second person in the room can talk and the counter stays at zero. We do not pretend otherwise. Client-side visibility is a deterrent for the common case, which is flipping to another tab on the same device. It is not a lock.

The other direction fails too. An honest candidate on a phone can hide the page without meaning to: an incoming call, a system sheet, a lock. The counter does not have a motive field. That is why the end screen tells them to contact the recruiter, and why your default for a thin transcript should be a second look rather than a closed door. Campus batches hit this more often than lateral hires, because the devices are worse and the rooms are louder. That setting has its own notes in how a campus drive should treat the warning.

If you want the rule to be fair, put it in the invite before you put it in the software. The software already has it. The invite is the part teams skip, and it is the part the candidate actually reads.

If you are about to run a drive and you want this behaviour walked through on your own roles, book a demo and we will show the warning, the end screen, and the record your team sees after.