The AI Interview Ended on a Tab Switch. Next Step

A recruiter forwarded me a screenshot last month. The candidate’s screen said Interview Terminated. The resume was one of the stronger ones in that role. The recruiter’s question was whether to throw the person out. The AI interview ended over a tab switch, and the team had no shared next step, so every person in the thread invented one.

I am writing the next step down so you can stop inventing. A HireQwik call that stops this way is a cutoff with a reason attached. It is not a verdict. Your job in the next half hour is to decide which of three things you are holding: a conversation too short to judge, a conversation long enough to read, or a conversation that looks like someone was reading from somewhere else. Then you act. Silence, which is what most teams do, is how a good candidate decides you are careless and a bad process decides it caught a cheat.

The overlay and the counter are explained in what Tab Switch Detected does on the call. This page starts after the room is already gone.

Key takeaways

• Interview Terminated is an end screen, not a score.
• A very short recording is filed as incomplete, not as a finished screen.
• A longer cutoff can still be read against the answers already given.
• Listen around the hides before you rebook or refuse.
• Reply to the candidate. The end screen asked them to write in.
• Do not let a local rule (“one warning and you are out”) replace the product.

When the AI interview ends, read the length first

Open the person from your review home and look at how much speaking happened. Do this before you open the complaint email, or the complaint will pick the pile for you.

A very short recording is filed as incomplete. If they barely got a handful of turns in, the scorer is told to leave the gaps blank instead of dropping in a polite middle number, and to say the conversation stopped early. A neat figure on a two-minute cutoff is a reason to read the note, not a reason to trust the figure.

A cutoff at minute four is usually pile one: unfinished. A cutoff after a long stretch of real answers is pile two: reviewable. I will not give you a magic minute that splits them, because a fast talker and a slow talker do not reach “enough” at the same clock time. Six speaking turns is the line the scorer uses. If you are under it, you do not have a screen. If you are over it, you might.

The end reason matters only to confirm you are in the right story. The stored reason for this stop is a tab switch. A camera stop uses different wording on the candidate’s screen, about repeated camera shutoffs, and a different stored reason. If the candidate’s screenshot says tabs and your record says camera, believe the record and ask for the screenshot again. People paraphrase.

Three piles after an AI interview ends on a tab switch

Use the same three piles every time so the team stops relitigating.

Unfinished. Almost no answers. Default action: offer another time, except when the little you have is already disqualifying for a reason that has nothing to do with the page, such as a knockout answer that was clearly no. When you rebook, send the one-paragraph rule again. Do not rebook into the same broken lab hour if the first failure was a room full of pop-ups. Say what should be different: quiet, charger, one window, phone on silent. The wording for that note is in the invite paragraph for candidates.

Reviewable. Most of the screen happened, then a hard stop. Read the answers. Listen to the minute before the stop. Keep them in the normal review queue if the work is specific and the hide looks singular. Send them to a short human conversation if you are unsure. Do not convert “unsure” into a reject to save the slot. A human conversation is cheaper than a wrong no, and it is the same remedy we use when other assist flags fire. Those flags, and the habit of listening rather than auto-closing, are covered in ChatGPT-style help on an AI interview.

Pattern. Hides sitting just before answers, speech that suddenly sounds written, little self-correction. You still do not have a picture of the second window. You have a pattern worth a person’s time. Bring them to a live round, or decide the sample is not one you will hire from and say so. What you should not do is let the pattern silently lower a score that the product refused to lower. The count is not a penalty. If you want that argument in full, it is in the reason the points stay put.

Write the pile on the record in whatever note field you already use. “Terminated, rebook” and “Terminated, review answers” and “Terminated, live follow-up” are enough. Future you will not remember the Slack thread.

Listening for a search versus an interruption

The counter has no motive. You add the motive by listening, or you admit you do not have one.

Play the stretch around the hide. An interruption often sounds like life: a door, a “hello?” half-caught, a flustered return, an answer that picks up the same clumsy thread as before. A search often sounds like a clean join: silence, then a paragraph with a shape nobody uses when they are rattled. One of those is not proof. Three of them in one call are a reason to stop trusting the transcript as the candidate’s own words.

Also check the camera side only as context. If they were also killing video, you have a second story, and it is a pause story rather than a tab story. Do not add the two counts into a homemade total and compare it to four. Each line is separate. A person with two hides and two camera cuts finished under the rule. You may still dislike what you heard. Dislike is allowed. Arithmetic you invented is not.

There is a specific lie of omission I want you to expect. That box clears on its own after a five-second wait, including while they are still away. A candidate can say they never saw the later boxes. That can be true and they can still be on strike three. Ask what the final screen said. If it said Interview Terminated and mentioned tabs or windows, the stop fired. If the call simply dropped and the screen was the normal thank-you, you are in a different incident, network or browser, and you should not scold them for a rule that did not end the call.

The normal thank-you screen is a useful contrast. It thanks them and says the team will review the conversation. It also asks for feedback. The terminated screen does not ask them to rate you. If they are describing a feedback form, they did not get the tab-switch ending. Believe the screen they can describe in detail.

What to write back to the candidate

The end screen already asked them to write to you if the stop felt wrong. Some will. Reply the same day. A next-day reply is fine. A silence is how they write a post about you.

For an unfinished call you are rebooking:

The session stopped because the interview window went away too often. Another tab, another app, or a locked screen can do that. There is not enough conversation here to review, so I am sending a fresh time. Please keep that window in front of you for the whole slot, and silence your phone.

For an unfinished call you are not rebooking, say the real reason. If the reason is “we only had a fragment and the drive is closed,” say the drive is closed. Do not say the AI found cheating.

For a reviewable call:

The call stopped early because the page was hidden past the warning limit. We are reviewing what was said before that. There is no need to forward a list of sites. We will come back to you with the next step.

Do not ask for a confession. Do not ask for a screenshot of their browser history. You will not read it consistently, and asking for it teaches candidates that the process is a negotiation.

If a placement cell is in the middle, send the cell the pile counts, not the gossip. How many rebooks, how many reviews. The campus version of that evening’s work is in tab switch warnings on a campus drive.

What your team should stop doing

Stop sorting the terminated rows into the reject filter as a morning ritual. You will bury incomplete interviews under a decision they never received. The product did not put them there.

Stop telling hiring managers “the AI caught them cheating.” You do not have that finding. You have a hide count and a recording. Managers repeat the sharper sentence in debriefs, and then you cannot walk it back when the recording is just a phone call from a parent.

Stop rebooking forever. One new slot is a fair response to a thin transcript. A third slot because the same person keeps leaving the page is you refusing to decide. Two attempts is plenty. After that, the pattern is the decision.

Stop debugging the candidate’s laptop in chat. “Try a different browser” is a reasonable line before a rebook. It is not a diagnosis of the stop you already have on file. The stop fired because the page was hidden four times after they had joined. A different browser will do the same thing if they leave the page four times. Say the behaviour you need, not a technical fable.

And stop promising that a human will “ignore the termination” as a favour. Either the answers are usable or they are not. A favour system is how one recruiter’s friend gets a fourth slot and a stranger does not. Write the pile rule where the team can see it.

What to say in the hiring-manager meeting

You will get five minutes, if you are lucky, and someone will ask “so did they cheat?”

Answer with the pile, not with a theory. “The call stopped because the interview page was hidden four times. We have under a minute of answers, so I am rebooking.” Or: “We have a nearly full conversation. I am scoring the answers and I listened to the pause just ahead of the cutoff. I will not call that cheating.” Or: “The pattern is a hide before each answer and speech that sounds read. I want a live round before we proceed.”

Those three sentences map to the three piles. They do not require the manager to understand the browser. They do require you to have listened. If you have not listened, say you have not, and take the recording into the meeting. Guessing in front of a manager is how “terminated” becomes “rejected” on a slide you will see again at the offer stage.

If the manager wants a numeric penalty anyway, do not invent one in the meeting to look prepared. Tell them the score does not move for this, and that a live follow-up is the penalty you can defend. Then stop talking. Filling the silence with a made-up deduction is the failure mode.

A cutoff is still information

I do not want the kindness of a rebook to blur the original point. Leaving the interview page during a live screen is a bad idea, and the product makes the fourth leave expensive so that people feel it. When the expense lands on someone who was hunting for a script, good. When it lands on someone who locked their phone, a second slot repairs it. Both can be true in the same week.

Your speed matters more than your tone. The candidate is sitting on Interview Terminated wondering if the last year of applications just died in one click. You can resolve that with a short note and, when the transcript is thin, a new time. The review of a longer transcript can take the usual path your team already uses for a finished screen. None of this requires a new policy document. It requires the half hour after the slot, spent on the length of the call and the sound of the minutes around the hides.

If you want to see a terminated record next to a finished one and decide your pile names before a live drive, Set up a walkthrough. We will end a test call on a tab switch and walk the record together.