Is an AI Interview Assistant Detectable?

By Aaron Cao · Updated 2026-05-25

The honest answer is: it depends on architecture. A native desktop AI assistant like SubcueAI is not visible to Zoom, Google Meet, or Microsoft Teams when you are on camera only — the overlay renders locally and never enters the conferencing app's process space. It IS detectable under explicit anti-AI proctoring (LiveHire, certain Mercer Mettl modes, the proctored Bar exam infrastructure) — those systems are designed to catch exactly this kind of tool. Detection is not a single yes/no; it is a function of architecture, platform, and proctor configuration.

What "detectable" actually means — three different layers

People search "is an AI interview assistant detectable" wanting a one-word answer. The honest answer is three different questions stacked together:

In the live meeting — can the interviewer see, in real time, that you are using an AI assistant?
On the recording — if the call is recorded, will someone reviewing it later spot it?
By a proctor — if a proctoring system (HackerRank Proctor, Mercer Mettl, LiveHire, anti-cheat browsers) is running, will it detect the assistant?

Each layer has a different answer, and conflating them is how candidates end up surprised. The rest of this article walks each layer separately, with no marketing — including the cases where SubcueAI is absolutely visible.

What Zoom, Google Meet, and Microsoft Teams can see

None of the mainstream video conferencing platforms — Zoom, Google Meet, Microsoft Teams, WebEx — can see a properly designed native desktop AI assistant in a normal call:

SubcueAI is a native desktop app, not a meeting bot. It does not join the call as a participant, does not request OAuth into your Zoom or Google account, and does not appear in the participant list.
It does not install a browser extension and does not modify your video feed. From the interviewer's side, the call looks identical whether or not the assistant is running.
The floating overlay where suggestions appear is rendered by macOS or Windows directly, on a layer outside the conferencing app's window. The conferencing app is not aware the overlay exists.

Bot-based interview assistants (the ones that join the meeting as a third participant to transcribe) are a different category entirely — those do appear in the participant list with their own name. SubcueAI is not in that category. See do AI interview assistants show in participant lists for the full breakdown.

What screen sharing does and does not capture

Screen sharing is where the honest answer changes. There are two screen-share modes on every major platform:

Full-screen share — everything visible on your display is shared, including any floating overlay positioned on top. If you full-screen-share and have the AI overlay open, the interviewer sees it. Do not full-screen-share with the assistant open.
Single-window share — only the selected window's contents are shared. The AI overlay, being a separate top-level window outside the shared app's window, is not in the shared stream. Single-window share is the safer mode if you must share anything during a coding interview or system-design walkthrough.

This is a platform behavior, not a SubcueAI feature — Zoom, Google Meet, Microsoft Teams, and WebEx all share the same window-vs-screen distinction. See can interviewers see AI tools during screen share for platform-by-platform configuration.

What recordings capture

Recordings split the same way:

Audio is always recorded if the call is recorded. The interviewer hears the same audio they heard live; SubcueAI does not change what they hear.
Video recording captures whatever the screen-share captured. If you only shared your webcam (no screen share), the recording is the call's video grid — the AI overlay never enters the recording.
Pacing review — a human reviewing a recording later can sometimes notice unnaturally even pacing, perfectly structured answers, or pauses that look like reading. This is a soft signal, not a hard detection. Practicing with the overlay before a real call (so you sound natural, not robotic) is the only mitigation.

Where SubcueAI IS detectable — and we say so

There are interview contexts where no real-time desktop AI assistant is safe, and we are direct about them in the responsible use policy:

Explicitly anti-AI proctored interviews — LiveHire, certain Mercer Mettl modes, the proctored Bar exam infrastructure, and similar systems. These are designed to detect exactly the kind of audio capture and overlay rendering SubcueAI does. Do not use it there.
Locked-down coding platforms — CoderPad's strict mode, HackerRank Proctor, Coderbyte proctor, and Codility under invigilation typically monitor processes, focus changes, and full-screen activity. Treat these like a proctored exam.
Company-managed devices — laptops owned and configured by the employer can run endpoint security agents that flag third-party apps. Do not install on a work-issued device.
Certifications and regulated assessments — anything that explicitly forbids outside help (Bar, Medical Board, CFA, GMAT, GRE proctored, etc). Using SubcueAI in those contexts violates the assessment terms.

We close the SubcueAI account of any user we learn is using it in these contexts. This is not because we cannot serve those use cases — it is because we will not.

How SubcueAI's architecture handles detection

The architectural choices that make SubcueAI invisible in normal calls — and why we chose them:

Native desktop, not browser — runs as a macOS or Windows app, not a Chrome extension. Browser extensions are visible in the toolbar and in some cases enumerable by sites; native apps are not.
ScreenCaptureKit (macOS) and WASAPI (Windows) for system audio — these are the OS-blessed audio capture APIs, not screen-recording APIs. They do not trigger the system "your screen is being recorded" indicator on macOS.
Floating window outside the conferencing app — the overlay is rendered by the OS window manager as its own top-level window. The conferencing app cannot enumerate or read it.
No meeting bot, no OAuth, no calendar integration — SubcueAI never touches your Zoom, Google, or Microsoft account. There is no API surface a platform could use to discover it.

This architecture is documented in the founder letter and in the detectability cluster — the four non-negotiables (privacy-first, native apps, sub-400ms latency, preparation not deception) drive every choice.

If you're still nervous, run a dry-run with a friend

The fastest way to verify what SubcueAI looks like from the other side is to start a Zoom/Google Meet/Teams call with a friend, share your camera only, and have them watch while you use the overlay. They will see your video; they will not see the overlay or any indication you are using one. The five minutes of testing is worth more than any article.

Setup steps for the dry run are in the setup tutorial. The same article covers permissions, audio device selection, and hotkey configuration so the overlay can be hidden instantly if the interviewer asks you to share your screen.

FAQ

Can Zoom detect SubcueAI?

No — not in a normal video call. SubcueAI is a native desktop app, not a Zoom bot or browser extension; it never enters Zoom's process space. Zoom can only see the camera, microphone, and screen-share streams you explicitly give it. The exception is full-screen sharing — anything visible on your monitor, including the overlay, is in the shared stream.

Does the overlay appear on screen sharing?

Only if you share your full screen. SubcueAI's floating overlay is a separate top-level window; if you share a single window (your IDE, your browser, etc), the overlay is not in that share. This applies on Zoom, Google Meet, Microsoft Teams, and WebEx.

Will the interviewer see I'm using an AI tool?

In a camera-only call, no — the call looks identical from their side. Pacing is the soft signal to watch: if your answers are unnaturally perfectly structured or you have long silent pauses while reading, a perceptive interviewer may notice. Practicing with the overlay before the real call so your delivery sounds natural is the mitigation.

Is using SubcueAI against Zoom / Google Meet / Microsoft Teams terms of service?

SubcueAI does not modify, automate, or interfere with the conferencing app, so it is not a violation of the platforms' ToS in the way that meeting bots or unauthorized integrations are. However, the interview itself may have separate rules — many employers explicitly prohibit outside assistance during interviews, and using SubcueAI in those contexts would violate the candidate's agreement with the employer, regardless of platform ToS. Check the rules of your specific interview before deciding how to use any tool.

Are there interview formats where SubcueAI should NOT be used?

Yes, and we say so directly. Explicit anti-AI proctored interviews (LiveHire, certain Mercer Mettl modes, the proctored Bar exam infrastructure), certifications that forbid outside help (Bar, Medical Board, CFA, GMAT/GRE under proctoring), locked-down coding platforms (HackerRank Proctor, Coderbyte proctor), and company-managed devices are all contexts where SubcueAI is detectable, prohibited, or both. The full list is in the responsible use policy.

What about pacing — can a recording reveal AI usage even if the overlay isn't visible?

Pacing review is the only post-hoc detection avenue when no screen share or proctor is involved. Reviewers can sometimes notice unnaturally even cadence, perfectly structured STAR answers, or short silent pauses that look like reading. This is not deterministic detection — it is a human judgment from someone watching the recording. Practicing with the overlay enough that your delivery feels natural is the only real mitigation; the architecture cannot help here.

Does SubcueAI trigger the macOS 'your screen is being recorded' indicator?

No. SubcueAI uses ScreenCaptureKit's audio-capture path, not its screen-recording path. The orange dot indicator that macOS shows for screen recording does not appear for system audio capture. Microphone capture lights up the green dot indicator on macOS — that is normal and expected for any app that uses your mic.