Teams and Google Meet Interviews: What to Test Before You Join

Different Platform, Different Failure Modes

If your interview is on Microsoft Teams or Google Meet rather than Zoom, most generic video-interview advice still applies — but the specific things that go wrong are different, and they go wrong in the first two minutes, which is exactly when you can least afford it.

Teams fails on identity: you sign in with the wrong account and cannot get into a meeting hosted by someone else's organisation. Meet fails on the browser: a forgotten tab is holding your camera, or the wrong Google account is active. Neither problem is hard to fix, and both are nearly impossible to fix calmly while five people wait.

This is the pre-join checklist for each.

Microsoft Teams

The account problem, which is the real one

Teams is built around organisational tenants, and an interview invitation almost always comes from the hiring company's tenant while you are signed in with your own personal or current-employer account. This produces the single most common Teams interview failure: the join link opens, and you are either stuck in a permission error or silently dropped into the wrong tenant's version of the app.

Fix it before the day:

1. Open the invitation link the day before. Not to join, just to see what it asks for. If it demands a sign-in you do not have, you have found the problem with a day to fix it.
2. Prefer "Continue on this browser" as a guest when you have no account in the host's tenant. Guest join is the reliable path and needs no sign-in. Check the invitation for a "Join on the web instead" option.
3. If you use Teams for your current job, expect a tenant switch. The desktop app can only be in one tenant at a time, and switching takes ten to thirty seconds of reload. Do it before the call, not at the join.
4. Set your display name properly if joining as a guest. Teams will show whatever you type, and "iPhone" or an old nickname is a bad first impression.

The pre-join screen is your friend

Teams shows a configuration screen before you actually enter. Use it rather than clicking straight through. Confirm the correct camera and microphone are selected, check the mic level meter moves when you speak, and set your background before anyone can see you. Once you join, changing devices takes several clicks in a menu while people watch.

Screen sharing in Teams

• The window list can take several seconds to populate on first use. Open the share picker once before the call so the list is warm.
• Guest join can restrict sharing depending on the host's policy. If you know you will need to share code, say so in advance so the host can enable it.
• Teams offers to include computer sound when sharing. Leave it off unless you are demonstrating something with audio; it can create echo.
• On macOS, Teams needs Screen Recording permission and must be restarted after you grant it.

Google Meet

The browser-holds-the-camera problem

Meet's most common failure is a black camera feed with everything apparently configured correctly. The cause is almost always another browser tab that already claimed the camera — a device test page, a previous Meet call you never closed, or another video site.

Only one tab can hold the camera at a time. Close every other tab that has ever asked for camera access, or restart the browser entirely. Restarting the browser is faster than finding the culprit.

The account problem, Meet's version

If you are signed into several Google accounts in the same browser, Meet will try to join with the default one, which may not be the account the invitation was sent to. Two reliable fixes: open the link in a private window and sign in with the correct account, or use the account switcher before clicking the link. Checking which account is active takes five seconds and prevents a "you need permission to join" wall.

Use the green room

Meet shows a preview screen before you join, with a self-view and device selectors. Use it exactly as you would the Teams pre-join screen: verify camera, verify microphone, and use "Check your audio and video" if it is offered — it records and plays back a short sample, which is far more informative than watching a level meter.

Screen sharing in Meet

• Tab sharing is unusually good here — it shares only that tab, and audio from the tab travels with it cleanly. Prefer it when showing a web page, a document, or a browser-based editor.
• "Your entire screen" is the right choice for anything involving a native application or switching between tools.
• Chrome will ask for its own screen-recording permission the first time, which on macOS means granting it to the browser rather than to Meet.
• The share dialog itself is a browser dialog, not a Meet one, so it looks different across browsers. Chrome gives the smoothest experience.

Side-by-Side Comparison

Concern	Microsoft Teams	Google Meet
Biggest risk	Signed into the wrong tenant	Another tab holding the camera
Best way to join	Desktop app, or browser as a guest	Chrome, correct account, private window if unsure
Pre-join check	Device settings on the pre-join screen	Green room preview and audio check
Best sharing mode	Window for one app, screen for coding	Tab for web content, screen for native apps
macOS permission	Granted to the Teams app; restart required	Granted to the browser
Sneaky delay	Tenant switch reload	Account switch and permission wall

What to Test the Day Before

Ten minutes, once, removes nearly all of this risk.

1. Open the actual invitation link. Do not just trust that it will work. See what it asks for.
2. Confirm which account you need, and get signed into it — or confirm that guest join is available.
3. Start a meeting with yourself on the same platform. Both Teams and Meet let you create a meeting and join it alone.
4. Grant macOS Screen Recording to the app or browser you will use, then restart it and verify sharing actually starts.
5. Test your microphone with playback, not with a level meter.
6. Practise the share you will need. If it is a portfolio, share that window. If it is code, share the screen and switch between editor and terminal as you would live.

During the Call

• Join two to three minutes early. Both platforms may hold you in a lobby; that is normal and not a reason to leave and rejoin.
• Do not rely on chat. Interviewers frequently do not watch the chat panel. If something is wrong, say it out loud.
• Mute only when there is real noise. Constant mute-unmute cycling produces clipped first words, which is worse than mild background noise.
• Watch for the sharing indicator, and stop sharing explicitly when you are finished. Leaving a share running while the conversation moves on is a common, avoidable mistake.

Frequently Asked Questions

Do I need a Microsoft account to join a Teams interview?

Usually not. Most interview invitations permit guest join through the browser, where you enter a display name and join without signing in. If the link insists on a sign-in and you have no account in that organisation, reply to the recruiter and ask for a guest-enabled link — this is a routine request.

Why is my camera black in Google Meet?

Almost always another browser tab holding the camera. Close other tabs or restart the browser. If that does not resolve it, check that the browser has camera permission at the operating-system level, and confirm no other application — a video app left running in the background is the usual suspect — has claimed the device.

Is the Teams browser version as good as the app?

For a standard interview, yes, and it avoids the tenant problem entirely. The app is better for heavy screen sharing and device switching. If you have no account in the host's tenant, the browser as a guest is the more reliable choice.

Can I use a phone if my laptop fails?

Yes, and both platforms have capable mobile apps — install them beforehand as a backup. Accept that framing and screen sharing will be worse. If the interview involves showing code or a portfolio, a phone is a fallback for continuing the conversation, not a substitute for the demonstration.

Which platform is the most reliable overall?

All three major platforms are reliable when configured correctly; what differs is what "correctly" means. Meet has the fewest install-related problems because it runs in a browser. Teams is the most robust once you are in the right tenant. The failure rate is driven far more by preparation than by the platform.