No. Meet hands the host no focus-tracking signal at all: there is no tab-switch counter in the host controls, no blur event log, and no such column in the attendance report. The browser does know when the Meet tab drops into the background, but that event belongs to the page that lost focus, and Meet keeps it rather than publishing it. What can still give a switch away is far more ordinary, and it is worth naming exactly: the share mode you picked, the preview of that share, Chrome's automatic picture-in-picture window, and where your eyes go on camera.
The mechanism, and why an assessment platform is different
A web page can observe one thing about focus: whether it is visible. The browser fires a visibility change event at a tab when that tab goes to the background, and a blur event at the window when the window stops being frontmost. Both are scoped to the page receiving them. A page cannot enumerate your other tabs, read their titles, see that you alt-tabbed to a desktop app, or notice a second monitor. The only fact available is that it is no longer on screen.
That single fact is enough for a proctored assessment, because of who owns the page. HackerRank, Codility and CodeSignal render the code editor you are typing in. Their script is running inside the thing you are working on, so it can timestamp every visibility change, count them, and write the total into a candidate report a recruiter opens later. The detection itself is unremarkable. The plumbing that carries it to a human is the whole product.
Google Meet has the same browser event available and nowhere to send it. Meet is a meeting product. There is no candidate report, no proctoring dashboard, no host panel listing per-participant attention, and no post-call artefact with a focus field in it. The attendance report some Workspace editions generate for larger meetings records participant names, join and leave times, and total duration. It is a register, not a monitor. Nobody receives a banner, a chat line or a badge when you move to another tab, and your camera and microphone carry on transmitting exactly as before, so from the other side of the call nothing changes.
Two honest caveats. First, this describes Meet itself. A managed Chrome profile, an admin-installed extension holding tab permissions, or corporate device management on a company laptop are separate systems that genuinely can log browser activity, and none of that is Meet reporting on you. Second, Google ships changes to Meet regularly. The absence of a focus surface has held for a long time, but if a future release adds one it will show up in the host controls, so check rather than assume.
Where a tab switch becomes visible anyway
Detection is not the interesting question. Visibility is. Every row below describes what the other participants actually receive when you leave the Meet tab, not what your own monitor shows.
| Your situation | What a tab switch looks like to them |
|---|---|
| Not sharing anything | Nothing at all in the stream. Your camera tile keeps rendering as normal. The only cue is your face and your eyes. |
| Presenting one Chrome tab | Nothing. The share is bound to the tab you selected, not the tab you are looking at, so it keeps streaming while you read elsewhere. Watch Chrome's sharing bar, which carries a button offering to share the tab you are currently viewing instead. One stray click swaps your presentation. |
| Presenting a browser window | Fully visible. A window share includes the tab strip, so every tab title is legible and the highlight moving between tabs is obvious. |
| Presenting your entire screen | Fully visible, immediately. They are watching that display live, so the new page simply appears. This mode also carries notification toasts, the taskbar and any window you open. |
| Your own share preview | A private mirror rather than a leak. Meet shows you a thumbnail of what you are presenting so you can confirm it. On an entire-screen share that preview sits inside the captured display and produces the receding tunnel effect. |
| Automatic picture-in-picture | Invisible on its own, but it appears the instant you leave the Meet tab, so during an entire-screen share the audience sees a small floating video window pop into a corner. The timing is the tell, not the window. |
| An overlay excluded from capture at OS level | Absent from the stream in every mode above, because the compositor strips it before the frame ever reaches Meet. |
Automatic picture-in-picture, the row people miss
Chrome can open a small always-on-top video window by itself when you navigate away from a tab running a call, so participants stay on screen while you work in front of them. It is a convenience feature aimed at you, and it reports nothing to the host. It still deserves its own section, for two reasons.
- Its arrival is synchronised with your switch. If you are sharing your entire screen, that floating window materialises in the corner of the captured display at the exact moment you leave Meet. An observer does not need a focus log when the software announces the change on your behalf.
- It can start a second mirror loop. The picture-in-picture window contains the meeting, the meeting contains your presentation, and your presentation contains the picture-in-picture window. On an entire-screen share this stacks on top of the tunnel the main preview already causes.
Behaviour here varies by Chrome version and by whether the feature has been permitted for the site, so treat the specifics as generally true and confirm on your own build. The fix is the same either way: present a tab rather than a display, or move Meet to a second monitor.
Prove it on your own machine in five minutes
Do this once and you will never have to take a page's word for it again, including this one.
Start a solo meeting and join it twice
Open Meet on your laptop, then join the same code from your phone with the microphone muted and the speaker off. The phone is now an honest audience of one.
Switch tabs while sharing nothing
Move to another tab for ten seconds and watch the phone. Your camera tile keeps updating, no indicator changes, no message arrives. That is your baseline.
Present a single tab, then switch away
The phone keeps showing the tab you chose, because it is still live. Now find Chrome's sharing bar on your laptop and read the button offering to share the current tab instead. That button, not Meet, is the actual risk in this mode.
Present your entire screen, then switch away
The phone shows the new page the moment you arrive on it, and usually a picture-in-picture window sliding into a corner a beat later. Time that delay. It is shorter than you expect.
Check the host side afterwards
End the call and look at everything Meet gives you: the chat log, any attendance report your account generates, the Calendar event. Names, join and leave times, duration. No focus data anywhere in it.
What an interviewer can genuinely infer from your camera
This is where the real signal lives, and it is inference rather than detection. A webcam gives an interviewer direction and rhythm, never content.
- Reading looks different from thinking. Reading is a repeating pattern: a run of short left to right movements, then a longer sweep back to start the next line, at a fairly steady cadence. Thinking is a loose gaze that drifts off, settles nowhere in particular and comes back. Several seconds of the first pattern while you are silent is the most legible cue there is.
- Gaze angle is stable and comparable. If your eyes go to the same off-axis point every time a hard question lands, and somewhere else entirely when you are talking freely, that consistency registers in a way any single glance does not.
- Light changes on your face. A bright surface off to one side alters the colour and level on that cheek. If the content you are presenting has not changed but the light on your face has, something else on your desk did.
- Timing. A long pause, then a fluent and unusually complete answer, then another long pause on the follow-up, reads as a rhythm rather than as a conversation.
- What they cannot tell. Whether you looked at a spec, a second monitor, handwritten notes, an IDE, a person, or a window. The camera reports where your head went and nothing about what was there.
Keep this in proportion. Everyone looks away to think, glances at a second display and pauses before answering, and interviewers know it because they do the same thing. It becomes a problem when it hardens into a repeated pattern, not when it happens once. The practical lesson is about eye lines rather than about software: whatever you need to read should sit as close to the camera axis as you can get it, which is why an on-screen overlay near the video tile behaves better on camera than a phone in your lap or a monitor off to your right. That constraint is the one OfferPilot AI is built around, and it is also why a browser-based coding round is easier to handle from an overlay beside the editor than from anything you have to physically turn towards, which is the job Code Copilot does.
Where this stops being useful
An overlay excluded from screen capture at the operating system level is absent from Meet, Zoom, Teams, OBS and plain screenshots, because Windows strips that window out of the frame before the capturing application ever receives it. That is a real property, and it is on every plan including the free tier, so the phone test above can confirm it at no cost. It is also narrow, and the boundary matters more than the feature does.
- It does nothing about a webcam. Capture exclusion hides pixels from a screen share. It cannot change where your eyes go, and this page has just spent a section explaining that your eyes are the actual signal in a Meet call.
- It does nothing inside a lockdown browser, against a proctor watching you in person or over video, against eye tracking, or against a phone propped up as a second camera. If your round is a proctored assessment rather than a conversation, this is the wrong tool and the honest answer is to prepare instead.
- Windows 10 and 11 only. No macOS, no Linux, no mobile, no browser extension. If you interview from a Mac, none of the above applies to you.
- Meet can change. Everything here describes Chrome on Windows in 2026. If your picker, your sharing bar or your host controls disagree with this page, trust what is in front of you.
The short version: Meet is not watching your tabs, and it has no channel to tell anyone if it were. Pick your share mode deliberately, present a tab rather than a display when the work lives in the browser, and put anything you need to read where your face does not have to move to reach it.