Do AI interview assistants show up in meeting participant lists?

AI interview assistants fall into two broad categories, and the participant-list question has a different answer for each.

The first category is the meeting bot. Tools like Otter, Fireflies, Read.ai, and many sales-call recorders work by sending a bot account into the Zoom, Google Meet, or Microsoft Teams call. That bot needs to be admitted to the meeting, and once inside it shows up in the participant list with a name like Otter.ai Notetaker or Fireflies Notetaker. The interviewer can see it, rename it, or remove it.

The second category is the local assistant. These run as a native application on your own laptop and capture audio directly from the operating system — your microphone plus the system output going to your speakers. Nothing connects to the meeting service, so nothing appears in the participant list. SubcueAI is built this way: a native macOS and Windows app with a floating local overlay and no meeting bot. You can read more about that design on the how it works overview.

You are worried about an unexpected name appearing next to yours mid-interview, and that worry is reasonable. This section gives you three quick checks you can run on any AI assistant before you trust it in a live call.

• Does it ask for the meeting link or calendar access? If yes, it is almost certainly a bot that will dial in and be listed.
• Does it install as a browser extension? Extensions often inject a bot or surface a banner inside the meeting UI that the other side can see when you share your screen.
• Is it a native desktop app that captures system audio? If yes — as with SubcueAI on macOS and Windows — there is no participant entry because the tool never joins the call.

A backend engineer interviewing for an L5 role at a public cloud vendor, for example, can open the SubcueAI overlay locally while the interviewer sees only the standard two participants in Zoom. The full install path is documented on the tutorial page.

Not appearing in the participant list is not the same as being invisible. A few honest limits apply to every local tool, including SubcueAI.

• Screen sharing. If you share your full screen or the wrong window, a floating overlay can be captured in what the interviewer sees.
• Local screen recording. Some companies record candidate screens during take-homes or live coding; anything visible on your display is in that recording.
• Proctored exams. Lockdown-style proctoring software actively inspects running processes and is designed to block third-party assistants.
• Company-managed devices. If the laptop is issued by an employer with MDM or monitoring agents, assume nothing on that device is private.

For a deeper breakdown of these boundaries, the detectability topic hub collects related questions in one place.

The architectural choice is deliberate. A bot in the meeting is easy to build but always shows up to the other side and routes interview audio through a third-party service. A local app is harder to build — it needs dual audio capture on two operating systems and a careful overlay — but it keeps the candidate in control of what is on screen and what is not on the call. You can read the broader product rationale on the about page, and pricing details are on the pricing page.