Supported Platforms
Zoom, Google Meet, Tencent Meeting, browser interview rooms, HackerRank, and CoderPad setup guidance
Supported Platforms
This page answers the most practical question: how to use the product with
Zoom, Google Meet, Tencent Meeting, browser interview rooms,
HackerRank, CoderPad, and similar platforms, and what to verify before a
real interview.
Bottom line first
We prioritize common meeting platforms, browser interview rooms, and online coding platforms. What determines the real result is not the platform name alone, but whether you completed the correct sharing setup, self-check, and one full rehearsal on the exact target platform.
Which platform types matter most
Meeting platforms
Zoom, Google Meet, and Tencent Meeting mainly depend on share mode,
window filtering, and what the remote side actually sees.
Browser interview rooms
These are common in live interviews, remote assessments, and collaborative editor flows. The focus is on focus behavior, tab switching, shortcuts, and the share path.
Coding and assessment platforms
HackerRank, CoderPad, LeetCode, and similar online IDE or assessment
platforms mainly depend on natural operation, screenshot Q&A timing, and
minimizing tab switching.
Screenshot-restricted and controlled-sharing platforms
The Desktop client currently supports use on some platforms that apply screenshot limits, window checks, tab-switch detection, or controlled sharing. You can still use Screenshot Ask, Voice Ask, shortcuts, and the stealth assistance window; judge readiness from a rehearsal on the exact target platform.
Know the boundary
The platform's own screenshot, recording, tab-switch, and proctoring rules still apply. We do not promise to bypass platform rules. Run self-check tools and a rehearsal room on the exact platform first, then use a second device to confirm what the remote or monitoring side actually sees.
How to tell whether a platform is ready before the interview
Run self-check tools first
Use self-check tools to confirm that capture, voice, shortcuts, focus behavior, and the share path are working.
Rehearse once on the exact target platform
Do not rely on the fact that another platform worked. Zoom, Google Meet, Tencent Meeting, and browser interview rooms can behave differently.
Use a second device to inspect the remote view
The real result is what the interviewer sees, not only what looks correct on your own screen.
Trigger the full core workflow once
At minimum, verify Cmd/Ctrl + B, capture, voice, view switching, and the
exact share mode you plan to use in the real interview.
How to handle common platforms
| Platform / Scenario | Type | What to do first | Continue reading |
|---|---|---|---|
Zoom | Meeting platform | Use the current advanced capture/window filtering option when available, then verify the remote result once | Zoom setup |
Google Meet | Meeting / browser share | Follow the browser-share path first, then verify once in a rehearsal meeting | Common Platform Issues |
| Tencent Meeting | Meeting platform | Use the current standard sharing mode, then confirm the remote view from a second device | Tencent Meeting setup |
| Browser interview room | Live interview page | Focus on focus behavior, shortcuts, tab switching, and the share path | Stealth Mode |
HackerRank / CoderPad / LeetCode | Coding / assessment platform | Keep switching minimal and rehearse the complete Screenshot Ask and shortcut workflow | Core Features |
| Windows browser compatibility concern | Default desktop-client path | Finish self-check and a real rehearsal room verification first; current client releases include a built-in keyboard-protection path | Stealth Mode |
What matters most on Zoom, Google Meet, and Tencent Meeting
The share mode must match the real interview
Sharing the entire screen and sharing a single window are not the same path. Your rehearsal must match the real interview setup exactly.
Re-test after updates
OS updates, meeting-app updates, and fresh app builds are the most common times when window and share behavior changes.
The remote view matters more than your local view
If the local machine looks fine but the remote feed is wrong, the result is still wrong. Always judge from the remote side.
What if your platform is not listed here
If you are using a newer platform, an in-house interview room, or a less common browser collaboration page, this order is usually the fastest:
- run self-check tools
- open a rehearsal meeting or test room
- verify
Cmd/Ctrl + B, capture, voice, and view switching - confirm the remote feed from a second device
- if it still feels off, review Common Platform Issues and Stealth Mode
If you came here because of a platform name search
The two real questions are usually simple: can this platform work, and what exactly should you verify before going live. That is why this page focuses on platform names, core actions, and the next troubleshooting entry points.
Continue reading
Stealth Mode
Review sharing boundaries, system-level behavior, and pre-interview verification.
Common Platform Issues
Start here when the problem is tied to sharing, display behavior, multiple monitors, or meeting apps.
Core Features
See how Screenshot Ask, Voice Ask, and Interview Materials work across different platforms.
Something missing or unclear?
Tell us which page or step needs work.
AI Reading Assistant
Send to your preferred AI
Smart Summary
Deep Analysis
Key Topics
Insights