Why a Vettasy interview shows no live alerts
Verified Session shows nothing during the interview. Signals are logged and read after the session. Why that design is fairer than a live warning.
Vettasy shows no signals during the interview, on either screen. They are logged and go into a report after the session. A live warning would turn the interviewer into a detective, bias the conversation and punish honest candidates for harmless facts. Judging a signal is a task for after the interview, not during it.
During a Vettasy interview, nothing about Verified Session appears on either screen. No alert, no counter, no colour changing on a dashboard. The signals are logged and go into a report that is generated when the session ends. This is a deliberate design choice, and this is why it is the fairer one.
What happens instead
Verified Session runs in the background of the session and records facts about the machine: a window hidden from screen capture, a virtual camera, a second monitor. Each fact is logged. The interviewer sees the interview plan and their own tools, not signals. The candidate sees a clean call. When the session ends, both sides receive the same report, with each line and its harmless explanations.
Why not warn during the call
A live warning sounds useful and is not. Three problems follow from it.
First, it turns the interviewer into a detective. An alert mid-answer pulls attention away from what the candidate is saying and toward policing the session. That is a bad use of the interview and unfair to the candidate, who is being assessed on their answers, not on a popup.
Second, it biases the rest of the conversation. Once an interviewer has seen a flag, every later answer is read through it, including from candidates whose flag is completely harmless. The interview stops being the same for everyone.
Third, most signals are harmless, and a live alert cannot say so calmly. A virtual camera belongs to a streamer. A second monitor belongs to a developer. Shown live, in the moment, a signal reads as an accusation. Shown in a report afterwards, next to its ordinary explanation, it reads as what it is: a fact to weigh.
Judging is a task for afterwards
A signal is not proof of anything, and judging it well takes context: the recording at that moment, the answers around it, and the candidate's own account. None of that is available in the middle of a live call, and trying to judge there produces snap decisions. So the judgment happens after the session, when the report can be read against the recording, and the candidate can dispute any line within 14 days.
This is the same principle that keeps emotion and tone out of the product entirely. The tool answers a narrow question, "were the conditions for an honest interview met," and it answers it with facts after the fact, not with alarms during the conversation.
What the interviewer does
Because there are no live signals, the interviewer's job during the call is the interview: the plan, the questions, the follow-ups. Afterwards, they read the report, open the recording at any moment that raises a question, and record the decision with the evidence it rests on. The candidate reads the same report and can contest it. Nothing about the session is decided in the heat of it.
Sources
- Vettasy, Verified Session and how to read a session report.
Written by the Vettasy teamVettasy is a desktop application for job interviews. Employers run structured, recorded interviews in it with verified participants. It is free for candidates. Windows and macOS.
