Microsoft Teams interviews carry a risk the other platforms mostly don’t, and it has almost nothing to do with Teams. It’s the laptop.
Teams interviews skew corporate, and corporate means the call frequently happens on hardware someone else administers. That flips the question. On Zoom or Google Meet the interesting problem is whether an assistant appears in a screen share. On Teams it’s often whether the machine you’re sitting at is reporting on itself, and no window setting touches that.
Teams itself can’t see your other software
Starting with the narrow question, because it does have a clean answer. Teams cannot detect applications running on your computer. When you share content in a Teams meeting, Teams requests a capture stream for the screen, window, or tab you picked. It receives frames. It does not enumerate processes or scan installed software.
And both desktop operating systems let an application ask to be left out of those frames. Windows exposes SetWindowDisplayAffinity with the WDA_EXCLUDEFROMCAPTURE flag, which is Microsoft’s own API doing the excluding. macOS exposes NSWindow.sharingType. Electron apps reach both through setContentProtection(true), which is the call Craqly makes on its assistant window.
There’s a small irony in Windows shipping the API that makes a window invisible to Teams. It exists for legitimate reasons, mostly DRM and applications handling sensitive data that shouldn’t leak into a recording, but the mechanism doesn’t care about your motive.
The managed device is the actual exposure
Here’s what changes on Teams. If you’re taking an interview on a work laptop, or on a machine issued by the company interviewing you, that device likely runs mobile device management. Microsoft Intune is the common one in Teams-heavy organizations, usually paired with Defender.
Software at that layer operates well below the capture stream. It can inventory installed applications, see running processes, and report to an administrator. Window exclusion is irrelevant to it, because it isn’t looking at pixels.
So the practical advice for a Teams interview is unusually blunt: don’t take it on a managed machine. Not because of what Teams does, but because of what the management stack does. If you’re interviewing while employed, using your current employer’s laptop to do it creates exposure that has nothing to do with AI assistants and existed before they did.
Compliance recording and transcription
Teams has a second characteristic worth knowing. Enterprise tenants can enable compliance recording, which captures calls automatically under an administrator policy rather than someone pressing record. Teams also does live transcription.
Neither of these sees more than a normal recording would. A compliance recording contains the same capture stream everyone else received, so a window excluded from capture is absent from it too. What changes is permanence and reviewability. On a compliance-recorded call, everything visible is archived by policy and can be pulled up months later by someone who wasn’t in the room.
Transcription matters for a different reason. It produces a searchable text record of what you said. If your spoken answers are noticeably more polished than your follow-up reasoning, that contrast is now in writing.
Where the platforms differ
| Google Meet | Zoom | Microsoft Teams | |
|---|---|---|---|
| Runs as | Browser tab | Native client | Native client |
| Can detect local software | No | No | No |
| Main risk | Assistant inside the shared Chrome window | OS capture permissions changing | Managed device reporting on itself |
| Automatic recording by policy | Uncommon | Uncommon | Common in enterprise tenants |
The part software doesn’t solve
Teams interviews are often panel format, which makes the human tell worse rather than better. More cameras, more people whose only job for the next ten minutes is watching your face.
Reading an answer produces a recognizable pattern. A pause, a lateral eye movement, then delivery that’s more fluent than the thinking that preceded it. On a panel, several people see it independently and compare notes afterward. It surfaces in the debrief as “seemed rehearsed” or “fell apart on follow-ups”, and that impression forms regardless of whether anything appeared on a screen.
The probe is what breaks it. A clean answer invites a specific question underneath, and if you read the answer four seconds ago there’s nothing underneath. That gets recorded as a competence problem, which is a considerably worse outcome than being caught with a tool.
Testing on Teams
- Start a Teams meeting with only yourself. A meet-now call works.
- Join a second time from your phone.
- Open the assistant so it’s clearly on your display.
- Share your whole screen rather than one window.
- Look at the phone.
If it’s visible there, capture exclusion isn’t working on your machine and no setting will change that today. Repeat after Windows or macOS updates, because that’s when it breaks without warning. If you’re on a managed device, this test tells you nothing useful, since the exposure there isn’t the capture stream.
Where Craqly fits
Craqly is a native Windows and macOS app, so it can make the exclusion call described above, and it does. It captures the interviewer’s audio through the system loopback path, so it hears the Teams call without joining it. Nothing appears in the participant list because nothing connected to the meeting.
What it can’t do is help you on a managed device. If your machine runs Intune or a similar agent, installing anything is visible to whoever administers it, and that’s true of any application. I’d rather say that than let the stealth claim imply more coverage than it has.
Stealth is included on every plan, the free Starter tier included, which gives 20 credits a month at one credit per minute of live session. That’s deliberate, so you can run the test above on your own hardware first. And most employers prohibit undisclosed AI use in interviews, with a 2025 SHRM survey finding a majority of hiring managers would disqualify a candidate over it. Not being in a capture stream is a technical property, not consent.
Test it on a personal machine, not a work one. The free Starter plan gives you 20 credits a month with stealth enabled, one credit per minute of live session, enough to run a solo Teams call and see exactly what a second device sees.
Frequently asked questions
Can Microsoft Teams detect an AI assistant on my computer?
No. Teams receives only the capture stream for the screen, window, or tab you chose to share. It cannot enumerate running processes or inspect installed applications. The real exposure on Teams is usually the managed device rather than Teams itself.
Can my employer see what I install if I interview on a work laptop?
Very likely yes. Managed devices running Microsoft Intune or similar endpoint management can inventory installed applications and running processes and report them to an administrator. This operates independently of Teams and is unaffected by window capture exclusion.
Does Teams compliance recording capture more than a normal recording?
It captures the same stream, but automatically under administrator policy rather than by someone pressing record. A window excluded from capture is absent from a compliance recording too. What changes is that the recording is archived by policy and reviewable later.
Does Teams live transcription reveal AI assistance?
Not directly, since it only transcribes spoken audio. It does create a searchable written record, so a gap between polished answers and weak follow-up reasoning becomes easier to notice after the fact.
Is a Teams panel interview riskier than a one-on-one?
In practice yes, though not for technical reasons. More interviewers means more people watching your face, and they compare impressions in the debrief afterward. The visual tells of reading an answer are noticed independently by several people rather than one.