What is an invisible AI interview assistant, and is it really invisible?

The phrase comes from how the first generation of interview tools worked: a bot joined the call, sat in the participant list, and transcribed everyone. An invisible assistant is the opposite design. It runs on your own machine, hears the call through the audio your computer is already playing, and draws its suggestions in a window that only exists on your screen.

Three concrete properties are what the word actually promises.

• No participant. Nothing joins the Zoom, Google Meet, or Microsoft Teams call. The participant list, the roster the interviewer sees, is unchanged.
• Nothing injected. Nothing is added to the meeting web page or the meeting app. The interviewer's client, the recording, and the transcript see the same call they would without the tool.
• Off the shared window. When you share a single window, the overlay is not part of it. It is a separate window on your desktop.

SubcueAI uses the word in exactly this sense for its native macOS and Windows desktop app, which captures system audio and your microphone and shows prompts in a floating local overlay, and for its browser extension Side Panel on Chrome and Edge, which captures the meeting tab's audio only and never transcribes you. The how it works topic explains the audio path in detail.

It is reasonable to assume the interviewer's software might detect an overlay, so it helps to be precise about what each surface observes. This section lists what Zoom, Google Meet, and Microsoft Teams receive from your machine, and the short version is: your audio, your video, what you share, and what you type into the meeting itself.

• Audio and video. The meeting client sends your microphone and camera. An overlay produces neither.
• Shared content. A single-window share sends that window's pixels. A whole-screen share sends everything on the screen, overlay included; that is the one way an invisible assistant becomes visible through the meeting itself.
• Meeting chat and reactions. Anything you type or click in the meeting is visible to all participants and lives in the meeting record.
• Not your applications. Standard meeting clients do not enumerate the programs running on your computer or report them to the host. Detecting running applications is what proctoring software does, and it has to be installed on your machine, usually as a condition of a proctored assessment.

A hiring manager watching a Google Meet call sees your tile, hears your voice, and sees whatever window you share; the invisible property is a description of that view, nothing more.

Four situations are outside what any overlay can promise, and an honest vendor says so on the page rather than in the fine print.

• Whole-screen sharing. Share your entire desktop and the overlay is on the shared feed and in the recording. The fix is procedural: share one window.
• Recording on your side. Employer software that records your screen, or a recorded assessment session, captures the overlay like any other window.
• Proctoring. Proctored assessments install software that can list running processes, watch the webcam, and log tab switches. An overlay is a running process.
• Company-managed devices. A laptop administered by an employer can report installed and running software regardless of what a meeting client sees.

A data analyst interviewing for a role at a bank was asked mid-call to share her screen to walk through a dashboard. Because she had rehearsed sharing a single window in a mock session, she shared the browser window with the dashboard and the overlay stayed off the feed. Someone who had only read that the tool was invisible would have shared the desktop. The detectability topic has the platform-by-platform version of this list.

As a description of the design, not a guarantee. Aaron Cao, founder of SubcueAI, chose a local overlay over a meeting bot for the reason above: a bot is a participant, and a participant is visible by definition. The overlay is deliberately a plain window so that it behaves predictably with screen sharing, and the product pages state the four exceptions plainly rather than claiming immunity from them.

In practice that means the desktop app and the browser extension Side Panel keep the participant list and the meeting page untouched, and the responsibility for the exceptions stays with you: share a single window, do not use it in recorded or proctored sessions, and do not run it on a company-managed device. Setup for both surfaces, including how to test what a screen share shows before an interview, is on the tutorial page; what the app captures and stores is described on the security page.