How to Use an AI Assistant During a Zoom Interview

Zoom is still the default room for technical interviews at most US tech companies, even five years after everyone said the pandemic norms would fade. The reasons are unglamorous: the client is stable, the audio is good enough, and most candidates already have it installed. But Zoom interviews are not just in-person interviews piped through a webcam. The medium changes what the interviewer can see, what they can't, and where you have room to bring your own tools — including an AI assistant — without it being weird or unethical.

This piece is about the practical mechanics: how Zoom's screen sharing actually works, where a coaching layer like Acedly can sit, and the etiquette that separates a candidate who looks composed from one who looks like they're reading off cue cards.

Zoom-specific etiquette before the call starts

Most of the bad first impressions in a Zoom interview happen in the first 30 seconds, and almost all of them are avoidable. Treat the pre-call as part of the interview.

• Join from the desktop client, not the browser. Browser Zoom drops audio quality and limits screen-share controls — you do not want to debug that mid-question.
• Update Zoom in the morning. The client occasionally forces an update right when you click the link, which is a five-minute panic you don't need.
• Pin yourself off-screen mentally and pin the interviewer in Speaker view. You'll talk to a face, not to a tile of yourself.
• Set your display name to your real first and last name, no emojis, no pronouns inside the name field. Zoom truncates aggressively in gallery view.
• Disable every notification on your machine — Slack, Mail, Calendar, Messages, system updates. Each banner that pops during a screen share is one more thing the interviewer remembers about you.
• Test your camera in the Zoom client itself, not Photo Booth. Zoom applies its own filters and exposure curve, and the preview is the only one that matters.

How screen sharing actually works in Zoom

This is the part most candidates get wrong, and it's the part that determines whether you can use any second-screen tool at all. Zoom's screen-share model is window-scoped or display-scoped, and the distinction matters.

• Share Screen → Desktop 1: the interviewer sees everything on that physical monitor, including notifications, dock activity, and any window in front.
• Share Screen → a specific window: the interviewer sees only that window. Anything else on your screen — a second browser, a notes app, a coaching overlay — is invisible to them.
• Share Screen → Portion of Screen: a green rectangle the interviewer sees, and only what's inside it.
• macOS adds an extra wrinkle: windows that use hardware-accelerated rendering or floating overlays may not show up to the remote viewer even on full-display share, depending on Zoom's capture mode.

The practical takeaway: when an interviewer asks you to share your screen, share the specific window — usually your editor or browser tab — not your entire display. It's better hygiene anyway, because you don't accidentally leak a second monitor or a Slack DM. And it leaves room on your other screen for whatever workflow you've built for yourself.

Where an AI interview assistant fits

An AI assistant during a live interview is most useful as a coaching layer, not a ghostwriter. The candidates who get value from tools like Acedly use them in three specific ways, and basically none of those ways involve reading answers verbatim off a screen.

1. Real-time question parsing. The assistant transcribes what the interviewer asked, surfaces the underlying competency (ownership, conflict, ambiguity, technical depth), and reminds you which of your prepared stories maps to it.
2. Structural prompts during your answer. A discreet 'you've been on Situation for 40 seconds — move to Action' is the kind of nudge that turns a rambling answer into a tight one.
3. Reference for technical specifics you genuinely know but might blank on. The exact name of an algorithm, a syntax detail, the order of arguments to a function you use weekly.

What it should not do: generate answers you don't actually understand, replace your preparation, or push you into bluffing through topics that need follow-up depth. An interviewer's second question is almost always sharper than the first, and an answer you didn't author falls apart there.

Mechanically: keep the assistant on a second monitor, or on a window that you do not share. Glance, do not stare. Your eyes drifting off-camera every six seconds is more visible than candidates think.

Coding interviews on Zoom

Most Zoom-based coding rounds use a separate web tool — CoderPad, HackerRank, Coderbyte, or a shared Google Doc for the truly old-school. The interviewer sends the link in chat, you open it in a browser, you both watch the same page. Zoom is just the audio and video channel.

This is good news, because it means screen sharing usually isn't required. The interviewer sees your code by virtue of the shared editor, not your display. You have full control over the rest of your screen.

• Open the coding pad in its own browser window, sized to fill one monitor. That keeps your eye line consistent and reduces the temptation to alt-tab visibly.
• Keep a scratch space — Notes, a text file, a side tab — for the brute-force outline before you start typing in the shared pad. Interviewers see your final keystrokes; they don't need to watch you reformat a paragraph.
• If the interviewer asks 'can you share your screen so I can see your terminal' — that is the moment to switch to single-window share and choose only the terminal. Not the full display.
• If the round explicitly forbids external tooling (some senior loops at large tech companies do), respect it. That's an integrity question, not a technical one.

Three failure modes to avoid

Assume the interviewer has done dozens of these calls this quarter. They notice the things you think they don't.

1. The off-camera glance. Reading too long off a second source makes your answers stilted and your eyes wander. If you're going to reference notes, do it during pauses, not mid-sentence.
2. The audio lag. Bluetooth headphones often add 100–200ms of latency, which makes you talk over the interviewer constantly. Wired earbuds or a USB headset are worth the small inconvenience.
3. The tab-switch noise. Cmd-Tab, browser tab clicks, and trackpad scroll are all picked up by built-in mics if your gain is high. A real microphone (or even a phone mic on a stand) cleans that up entirely.

“

The interviewer will forgive a wrong answer faster than they'll forgive a candidate who clearly isn't present in the conversation. Tools should make you more present, not less.

What to do this week

1. Update Zoom and run a 5-minute solo meeting. Confirm your camera, audio, and the share-window flow.
2. Decide which monitor or window will hold any second-screen reference. Lock that arrangement in.
3. Disable every system notification permanently for interview hours — most OSes have a Focus mode for exactly this.
4. Run two mock interviews end-to-end on Zoom, including screen sharing a coding pad, before the real loop.
5. Practice glancing, not reading. If you can't get the value of a coaching prompt in one second, treat it as noise and ignore it during the call.

The candidates who do well on Zoom interviews aren't the ones with the most exotic setup. They're the ones who treat the medium as part of the interview — quiet room, locked-down screen, predictable workflow — and let any AI assistance disappear into the background of an answer they were going to give anyway.