How to Use an Interview Copilot on Zoom, Google Meet & Microsoft Teams (2026)

Last updated: May 2026

TL;DR

Using an AI interview copilot on Zoom, Google Meet, and Microsoft Teams is the same workflow with three platform-specific gotchas: Zoom’s “Original Sound” toggle, Google Meet’s noise cancellation interfering with mic-route configurations, and Teams’s screen-share defaults that can expose more than you intended. This guide walks through setup on each platform, the dual-monitor positioning trick that preserves eye contact, and the 30-second rehearsal that prevents the most common mistake: looking at your second screen the instant a question lands. The fastest way to get this right: use OphyAI’s real-time interview copilot which is purpose-built for these three platforms.

Who This Guide Is For

You have a live video interview coming up. It’s on Zoom, Google Meet, or Microsoft Teams. You want to use an AI interview copilot to surface tailored answer suggestions in real time, without your interviewer noticing.

You’ve probably already read our guide on whether interviewers can detect AI copilots — short answer: well-used copilots are very hard to detect. The detection question depends almost entirely on technique, not technology. This guide is the technique.

The 60-Second Mental Model

An interview copilot needs three things to work during a Zoom, Meet, or Teams interview:

It must hear the interviewer. This is the audio routing problem. The copilot captures the audio of the meeting (your interviewer’s voice) so it can transcribe what’s being asked.
It must display answers somewhere you can see them. Without being visible to the interviewer.
It must not be visible in your screen share, if you screen-share. Most candidates don’t screen-share, but technical candidates do — for live coding, for portfolio walkthroughs.

If all three are set up correctly, the copilot is functionally invisible to the interviewer.

Universal Setup (Before You Pick a Platform)

Regardless of whether your interview is on Zoom, Meet, or Teams, do these four things 30 minutes before the interview:

1. Use a dual-monitor setup if possible

The single biggest determinant of how natural you look is whether your copilot is on the same screen as the interviewer’s video feed or on a different screen.

Best: Two monitors, with the interviewer’s video on the same monitor and roughly the same height as your webcam (eye contact preserved), and the copilot on the second monitor positioned just below the webcam (so your eyes drop a tiny amount but don’t swing sideways).
Acceptable: Single monitor with copilot in a window positioned just below the meeting window, ideally underneath where the webcam is.
Worst: Copilot off to the side. Your eyes will visibly track to the side every time you read a suggestion.

For a deeper guide on positioning, see how to prepare for video interviews.

2. Test audio routing

The copilot captures the meeting audio. Different copilots do this differently:

OphyAI’s Interview Copilot: Browser-based audio capture. Just launch the session in your browser and grant tab-audio permission.
Desktop overlay tools (Cluely, some others): Capture system audio via a virtual audio device. May require granting screen-recording permissions on macOS.

Run a test 30 minutes before the real interview. Open a YouTube video at your normal speaker volume and check that the copilot transcribes correctly. If it doesn’t, you’ll know now, not when your interviewer is asking “tell me about a time you led a team.”

3. Use headphones — but consider which kind

Headphones eliminate echo (your interviewer hearing themselves through your speakers). For audio-capture copilots, two configurations work:

Closed-back over-ear headphones with a separate microphone (USB or boom): Cleanest setup. The copilot captures the meeting audio at the source (browser tab) before it goes to headphones.
AirPods or Bluetooth earbuds: Work fine for most copilots that capture audio at the OS or browser level rather than the speaker level. Test in advance.

Wired earbuds with an inline mic also work but compress audio quality.

4. Close everything else

Quit Slack, Discord, email notifications. Mute system sound alerts. A notification popping up mid-interview is the kind of unforced error that costs offers.

Zoom-Specific Setup

Zoom is the most common interview platform and the easiest to configure correctly.

Step 1: Join the meeting in your browser, not the Zoom app

This sounds counterintuitive — most users default to the Zoom desktop app. For interview copilots, joining in a browser (Chrome or Edge) gives the copilot direct tab-audio access without requiring system-level audio capture permissions.

When you click the Zoom meeting link, look for “Join from your browser” near the bottom of the page. (You may need to first try the desktop app and have it fail to launch — Zoom intentionally hides the browser join option.)

Step 2: Turn off Zoom’s “Original Sound” if it’s on

Zoom’s Original Sound feature applies aggressive audio processing that can muddy transcription. In your audio settings before the meeting:

Settings → Audio → Suppress background noise: set to Low (not Auto or High)
Settings → Audio → Advanced → Turn off “Echo cancellation”

If you’re joining in the browser, these settings are simpler — browser Zoom uses less aggressive processing.

Step 3: Position the windows

Drag the Zoom meeting window to the top of your screen, ideally with the gallery view positioned so the interviewer’s face is just below your webcam. Open your interview copilot in a separate browser window underneath.

Step 4: Disable Zoom annotations and reactions

In meeting controls → More → Settings → make sure annotations, whiteboard, and reactions are off. You don’t want a thumbs-up reaction to fire accidentally while your eyes are reading a suggestion.

Google Meet-Specific Setup

Google Meet is increasingly common, particularly for Google-hosted interviews and for startups using Google Workspace.

Step 1: Use Chrome, not Safari or Firefox

Google Meet works best in Chrome (or Chromium-based browsers like Edge, Brave). Safari has known audio-routing quirks that can interfere with browser-tab capture copilots. Firefox works but has occasional latency spikes.

Step 2: Watch out for Meet’s noise cancellation

Google Meet’s noise cancellation is aggressive and applied at the browser level. If your interviewer’s audio sounds robotic in your copilot transcription, the cancellation is the likely culprit.

In Meet → Settings (gear icon) → Audio → toggle off “Noise cancellation”. This means more background sound, but cleaner transcription.

Step 3: Use the side-panel layout

Google Meet’s default sidebar layout (with the people list visible) sometimes causes the video to be off-center on screen. Toggle to “Tiled” layout via the three-dot menu → Change layout → Tiled. This centers the interviewer’s face more reliably under your webcam.

Step 4: Disable chat and reactions

Click the three-dot menu → Host controls (or your own settings) → disable reactions if you can. Reactions can fire from accidental keyboard shortcuts.

Microsoft Teams-Specific Setup

Teams is common for enterprise interviews (finance, consulting, enterprise SaaS).

Step 1: Use Teams in your browser if you can

Like Zoom, Teams works in a browser, and the browser version gives interview copilots cleaner audio access. The web client (teams.microsoft.com) has near-feature-parity with the desktop app for most interview scenarios. If the interviewer sent a calendar invite with a Teams link, opening it should give you the option to “Use the web app instead.”

This is the biggest Teams gotcha. Teams’s default screen-share behavior on some setups is “Share entire desktop” rather than “Share window.” If you’re asked to screen-share for a coding round or portfolio walkthrough, always pick “Share window” and specifically the window you mean to share.

If you accidentally share your entire desktop, your copilot window may become visible. This is the single most common way candidates get caught.

Step 3: Turn off Teams’s “noise suppression”

Teams settings → Devices → Noise suppression → set to Low (not Auto or High).

Step 4: Beware Teams Live Captions

Teams has a Live Captions feature that the interviewer can enable. It doesn’t affect your copilot directly, but it can be on for the interviewer’s side. Don’t comment on it if you notice it in their UI — it’s their tool.

During the Interview: The Eye-Contact Technique

Setup is half the battle. The other half is what you do during the live interview.

The 3-Second Rule

When the interviewer asks a question, do not look at the copilot immediately. Look at the interviewer’s face for 2-3 seconds first — as if you’re processing the question (because you are). Then drop your gaze briefly to the copilot, absorb the structure of the suggestion, then bring your gaze back up to the interviewer before you start answering.

Reading directly off the screen is the most common detection signal. It produces:

Eyes that visibly track left-to-right or up-and-down
A delivery cadence that sounds like reading aloud (slightly mechanical pacing, unnatural emphasis)
Long pauses while you process text mid-sentence

The Absorb-and-Speak Pattern

Don’t try to read every word the copilot generates. Use it as a structural scaffold:

Glance at the bullet points or sub-headers
Pull the framework into your head
Speak in your own words, with your own examples

Candidates who have practiced extensively with OphyAI’s Interview Coach before going live with the copilot do this naturally — they’ve internalized the STAR framework and behavioral patterns, and the copilot serves as a memory aid rather than a script.

When to Glance, When Not to

Glance at the copilot when:

The interviewer asks a complex behavioral question and you need a story prompt
A technical concept is in the question that you want to triangulate quickly
The interviewer asks for a structured answer (e.g., “give me three reasons why…”)

Don’t look at the copilot when:

The interviewer is mid-question (you’ll miss the rest)
You’re already mid-answer and confident
The question is a simple “yes/no/which” — overcomplicated answers signal copilot use

Common Failure Modes (And How to Avoid Them)

Failure 1: Audio not capturing

Cause: Browser permissions, headphone routing, system mute, or a copilot configured for the wrong audio source.

Prevention: 30-minute pre-interview test. Open a YouTube video, confirm the copilot transcribes.

Failure 2: Visible eye tracking

Cause: Copilot positioned too far from the webcam.

Prevention: Position the copilot window directly below the meeting window, ideally below the webcam. Use the 3-second rule above.

Failure 3: Latency mismatch

Cause: Slow internet, or the copilot model is slow on cold-start.

Prevention: Wired ethernet if possible. Open the copilot 5 minutes before the interview to warm up the connection.

Cause: Picking “Share entire desktop” instead of “Share window.”

Prevention: Practice the screen-share flow before the interview. Always pick a specific window.

Failure 5: Reading the suggestion verbatim

Cause: Not internalizing the suggestion, just reading it aloud.

Prevention: Practice with the Interview Coach first. Drill the frameworks until they’re muscle memory, and the copilot becomes a reminder, not a script.

Quick Setup Checklist (30 Minutes Before)

Frequently Asked Questions

Can I use an interview copilot on a Mac?

Yes. All major interview copilots work on macOS. Browser-based copilots like OphyAI’s Interview Copilot work without additional system-level permissions. Desktop overlay tools may require granting screen-recording permissions in System Preferences → Privacy & Security → Screen Recording.

Does an interview copilot work on Zoom mobile?

Mobile setups are not recommended. The screen size makes positioning the copilot difficult, and audio routing is unreliable. Use a laptop or desktop with a webcam.

Can the interviewer see my interview copilot on Zoom?

No — provided you don’t screen-share your entire desktop. The interviewer only sees what your webcam captures (your face) and what you explicitly share. Your second monitor or the second browser window is not visible.

Will my interview copilot work if the interviewer uses Live Captions on Teams?

Yes. Live Captions is a feature the interviewer sees in their UI — it doesn’t affect your copilot’s ability to capture audio. The copilot transcribes the interviewer’s audio independently.

What if my internet drops mid-interview?

If you lose internet, the copilot stops working. Have a backup plan: a single page of handwritten notes with your top STAR stories. Wired ethernet dramatically reduces the risk of mid-interview drops.

Is using an interview copilot allowed?

This is an ethics question rather than a technical one. For an in-depth answer, see our guide Is using an interview copilot ethical or cheating?. Using a copilot as a memory aid is widely considered acceptable; reciting verbatim scripts crosses into a gray zone.

Try OphyAI’s Interview Copilot Free

OphyAI’s real-time interview copilot is purpose-built for Zoom, Google Meet, and Microsoft Teams. Browser-based, no installs, no system-level permissions, no screen-recording prompts. Get 5 free credits to try a full session before your real interview — no credit card required.

Start practicing free → or see how OphyAI compares in our best interview copilot software 2026 guide.