AI Interview Assistant for Microsoft Teams Calls (Windows): What Works, What Shows

Most corporate interviews in India now land in Microsoft Teams: Infosys, Accenture, Capgemini, the big banks and most captives run their tenant on Microsoft 365, and the recruiter's calendar invite carries a Teams link by default. Teams behaves differently from Google Meet in two ways that matter for an AI interview assistant: there is a real desktop client, and its sharing options split "screen" from "window" with an explicit sound toggle.

This page walks through what Teams sends when you share, what Microsoft's own documentation says participants can see, how the MockMate Windows companion behaves alongside the Teams desktop client, how to set it up, and where it stops. It also says plainly when you should not use it.

How a Microsoft Teams interview works

You receive a meeting link. On Windows it opens either in the Teams desktop client (if installed and signed in) or in the browser as a guest. Both routes join the same meeting. From the candidate's side a typical round has:

• Lobby and admission. Guests often wait in a lobby until the interviewer admits them. Nothing about a helper matters at this stage; use it to confirm your audio device.
• Audio from the interviewer playing through your Windows default output device, whether laptop speakers, a wired headset or Bluetooth earbuds.
• Sharing. Either the interviewer shares a problem statement or a PowerPoint, or you are asked to share your project, a document or your editor.
• Recording or transcription. Corporate tenants sometimes record interview rounds. If Teams tells you the meeting is being recorded or transcribed, treat it as a signal to check what the organisation allows.

Teams sharing options and what the interviewer can see

Microsoft's "Share content in Microsoft Teams meetings" page describes the options. The two that matter for a candidate are Screen (your entire desktop) and Window (one application). There are also PowerPoint Live, Excel Live and Whiteboard, which share a file rather than pixels from your display.

Two details from Microsoft's share-sound page are useful in practice. First, if you do turn on sound while sharing your desktop, "all audio from your computer, including notifications, will be heard by participants," so mute other apps before you present. Second, a Windows-specific quirk: when you join a Teams meeting, Windows reduces the volume of other sounds from your device, and the same setting also quiets any audio you are trying to share. The fix Microsoft gives is in the Sound Control Panel under Communications, set to "Do nothing." This quirk affects what Teams participants hear from you; it does not affect what your computer plays from the interviewer, which is what a transcription tool listens to.

The practical rule for a candidate:

• Prefer Window. Share your IDE, your PDF or your browser window. Other windows are not sent.
• Use PowerPoint Live for slides. Teams renders the file; your desktop is never on screen.
• Treat Screen as "everything is visible." If an interviewer insists on a full-screen share, hide any helper window before you click Share. Do not rely on capture resistance.

How the MockMate Windows companion behaves with Teams

MockMate's companion is a native Windows 10/11 app. It does not install into Teams, does not read Teams' data, and does not depend on which client you joined from. During an authorised Live session:

• It hears the interviewer through system audio and you through the microphone, transcribing both with low latency. Input health is visible: microphone, system audio, transcription and reconnect states have their own indicators, so a wrong output device shows up before the first question.
• It stays a compact tool window, always-on-top, movable, with a one-key hide. Privacy Mode and capture resistance exist on supported Windows display paths. This is platform-dependent. Different Teams builds, GPU drivers, virtual desktops and remote-desktop setups behave differently, and MockMate does not promise invisibility.
• Answers are grounded in the session snapshot you attached before the call: resume, job description, notes or instructions. Each answer carries a source label (transcript, manual text, screen text or screenshot).
• Screen context is manual. When the interviewer shares a coding problem or a case, you capture a screenshot or the visible text yourself, review it in a queue, and can remove it before sending.
• You choose the model and the depth, fast or deeper reasoning, and there is an on-device "Local" option for some answers.
• Mixed-language rounds work. Set your spoken language and transcription plus answers handle Hinglish naturally, which matters in HR and managerial rounds that switch between Hindi and English.

The companion sends nothing into Teams. If you share a window, that window is what goes out. If you share the screen, the screen goes out, and the companion's window goes with it unless hidden.

Setup steps before a Teams interview

1. Register at mock-mate.com/register and attach your resume plus the job description. This context feeds both Practice and Live.
2. Run a browser Practice session first. It is adaptive, with interviewer personas and follow-up pressure, and it ends in a report. You learn how to glance at a suggestion without breaking eye contact with the camera.
3. Install the companion from the download page (sign-in required) and sign in inside the app.
4. Check the Teams audio device. In Teams, open device settings and confirm the speaker matches the Windows default output. Microsoft's share-sound page notes that Teams and your computer need to be set to the same speaker for sharing to work; the same alignment is what lets the companion hear the interviewer.
5. Do a ten-minute test. Start a Teams meeting with a friend, use one of your three free Live starts, speak, listen, and watch the transcript. Try the one-key hide while the Teams window has focus. Try sharing a window and confirm what your friend sees.
6. Set Do Not Disturb. Microsoft notes that notifications show during a screen share unless Do Not Disturb is on. That is good advice with or without a helper.
7. Decide on the mode. Use Live assistance only where the organisation, interviewer or applicable rules permit assistance and disclosure. Use Practice when permission is unclear.

Known limits on Microsoft Teams

• Corporate tenants can restrict sharing. If the host disables attendee sharing, you may not be able to present at all. This is a Teams admin setting, not something any helper changes.
• Audio device mismatches are the main failure. A headset paired after joining, or a Teams speaker setting that differs from the Windows default, means the companion hears silence. Check the indicators.
• Latency. Transcription is quick; a full answer takes longer. Treat suggestions as direction, not a script to read.
• Proctored assessments are separate. If the interview also uses an assessment platform with its own monitoring, that platform's rules apply, and the companion's Windows capture resistance says nothing about it.
• Windows only. No Mac, iOS or Android companion. Practice runs in any modern browser.
• Free allowance is capped. Three Live starts and three Practice starts, ten minutes each, tracked server-side. After that credits apply; as of September 2026 the packs are Starter ₹2,000 for 2 credits, Growth ₹5,000 for 5, Pro ₹10,000 for 12, one credit being roughly sixty minutes billed in thirty-minute blocks with a ten-minute grace window. Details on the pricing page.

Ethics on Teams interviews

Many Teams interviews are corporate, recorded, and governed by the employer's candidate policy. Some employers explicitly ask whether you used AI assistance. Answer honestly. A helper is legitimate in a mock round with a mentor, a calibration call, a meeting where you want your notes and the JD beside you, or any interview where the interviewer has agreed. It is not legitimate where assistance is prohibited, and MockMate's Acceptable Use and AI Safety and Usage policies say it does not authorise unauthorised interview use.

If the interview matters and permission is unclear, the strongest move is still Practice: run the Teams-style round in the browser the day before, read the report, and walk into the real call without needing anything on top.

Teams vs Google Meet vs Zoom for a candidate

For the Meet-specific behaviour see Google Meet interview AI helper; for Zoom see Zoom interview AI assistant. For a plain-language explanation of what recruiters can actually see, read Can Zoom, Google Meet or Teams detect an AI overlay?.