When HearQA Fits: AI Copilot Risk by Platform

Before deciding whether HearQA fits a scenario, it helps to know what the other side is actually watching. Modern remote-exam and interview platforms aren't one thing — they're a stack of monitoring signals, most of which focus on the computer you're taking the exam or interview on. Understanding each signal is the difference between "this is fine" and "this is a career-ending risk."

Webcam monitoring is continuous video of your face during the session. Platforms like Proctorio, Respondus Monitor, Honorlock, AWS OnVUE, and Kryterion use face detection (to confirm it's still you), gaze tracking (to flag when your eyes repeatedly drift off-screen), and multi-face detection (to catch someone helping in the room). The AI does the first pass; a human reviewer watches flagged sessions after the exam.

Audio monitoring is continuous microphone capture. It flags whispering, lip movement, a second voice, or noticeable background sounds. Most certification proctoring platforms enable it by default. Some academic ones only enable it for high-stakes finals.

Screen monitoring typically runs through a lock-down browser (Respondus LockDown Browser, Proctorio's browser extension, AWS OnVUE's secure browser). These block other apps from opening, prevent tab switches, disable copy/paste, and record screen output. Some can detect external monitors.

Pre-exam checks — ID verification, a 360° room scan with the webcam, a clear-desk check — happen before the timer starts. Once the exam begins, only what's inside the webcam frame is actively monitored. That's the key insight: the room-scan constraint ends when the exam starts.

Behavioral flags are AI-detected anomalies: long pauses before answering, eye-movement patterns, unusual response speeds. A single flag isn't disqualifying; a cluster of them triggers human review. The review happens after you've finished — which means consequences can land days or weeks later.

Desktop is the right call when you want to pull audio from a meeting tab (Zoom, Meet, Teams — Chromium desktop only), capture a screenshot from a browser tab (an unproctored coding challenge running in another window), or upload files from your computer. The trade-off is screen-share risk: if the interviewer or client asks you to share your screen mid-call, HearQA's window is visible.

Phone is the right call when the other side is watching you on camera. A phone kept flat below or behind the laptop is the lowest-detection setup — eye-gaze drift is the primary tell trained recruiters look for. The trade-offs: nothing in the room is private from the in-room camera (don't prop the phone where it's visible), and reflective glasses can show the phone screen on a high-resolution webcam.

For Interview and Conversation the phone is the recommended device — both are camera-on scenarios with screen-share risk. For Exam, Certification, Practice, and Presentation either device works equally well; pick whichever has the screen you'll be reading. The session-creation page surfaces this same recommendation when you start a session.

The product is designed for three kinds of moments: scenarios with no one watching your camera or screen, live conversations where a second device off-camera is unremarkable, and preparation.

Unproctored online courses (Coursera, edX, LinkedIn Learning, HubSpot Academy, Salesforce Trailhead, most Microsoft Learn paths, internal company training) have no webcam, no screen lock-down, and often no timer. The "honor code" is the only barrier, and most of these platforms now explicitly allow or even integrate AI assistance. HearQA is just a better study-and-reference tool here.

Video calls on Zoom, Meet, and Teams (the standard business-meeting flow, not a locked-down interview platform) have one or a few human observers watching a small webcam tile. They aren't running AI analysis on your eyes. A phone tucked below the camera frame is about as detectable as a notepad on your desk — possible to spot if they're looking for it, unremarkable otherwise.

Take-home tests, Canvas/Moodle/Blackboard quizzes without lock-down, internal company compliance training, and practice/mock exams (Whizlabs, Tutorials Dojo, ExamTopics) have no active monitoring. Any device works, any workflow works.

Practice mode itself — the scenario in HearQA's session picker — is the responsible path for preparing for anything high-stakes. Unlimited rehearsals, full AI coaching, upload all your study materials, no one watching because there's no exam. If you're considering HearQA for an exam we tell you to avoid, we mean Practice instead.

Certification exams delivered through AWS OnVUE, Pearson VUE's home edition, PSI, Kryterion, or Certiport use the full monitoring stack — webcam, screen lock-down, pre-exam 360° room scan, AI gaze tracking, and human review of flagged sessions. These aren't gentle systems. A phone becomes detectable as soon as your eyes repeatedly drift the same direction. Even if the phone itself is outside the webcam frame, the gaze pattern is visible.

Consequences are serious: score cancellation, retake fees, multi-year bans from the certification body (AWS, PMI, CompTIA, ISC², CFA Institute have all documented bans), and — in regulated fields like finance, healthcare, or law — professional disciplinary action. A 90-minute AWS exam is $150; the actual cost of getting caught is the years of career impact.

Proctorio, Respondus Monitor, Honorlock, and ProctorU protect university finals and online-degree programs. Consequences here include course failure, academic probation, and expulsion. University integrity offices generally believe their proctors over student appeals. Standardized tests like GRE at Home, TOEFL iBT Home Edition, and IELTS Online use the same technology with even stricter policies — and disqualification often means a multi-year hold on retakes that affects grad-school and visa timelines.

For any of these, our recommendation is unambiguous: switch to the Practice scenario before the exam. Upload your study materials there, run mock sessions, ask the AI every hard question you can think of. The preparation is the help. The live exam isn't the moment to try to hide HearQA from a system specifically designed to catch that.

Standard video interviews — a recruiter, hiring manager, or panel on Zoom, Meet, or Teams — are the lowest-risk HearQA use case after unproctored courses. The interviewer watches a small video tile of your face. They aren't running gaze-tracking AI. A phone propped below the camera, angled so you can glance at it without moving your eyes far from the screen, is genuinely unremarkable.

Behavioral rounds, initial screens, system-design discussions, and most take-home-style technical discussions work well. The challenge is when the interviewer switches modes mid-call: asks you to share your screen for a live coding challenge, opens a whiteboard, or moves you into a proctored coding platform like CodeSignal or HackerRank with proctoring enabled.

CodeSignal's Interview/Screen products and HackerRank's proctored assessment mode use the same monitoring stack as certification exams: webcam, screen, sometimes mic, AI gaze tracking, sometimes code-paste detection. HireVue and similar AI-analyzed one-way video platforms run sentiment and behavioral AI on your recorded responses. Detection risk in all of these is real.

If your interview round is purely conversational — yes, HearQA fits. If you're routed to a proctored coding platform, switch to Practice beforehand instead. For mixed-format interviews (conversation plus a separate proctored coding test), HearQA helps with the conversational portion only.

Business calls — sales, client meetings, negotiations, consultations — are another HearQA-friendly context. The camera is usually on and the audio is captured (for your own transcription, via the tab-audio feature or a second mic), but nothing on the other side is trying to detect AI help. The only wrinkle is when a client asks to share your screen mid-call for a demo or walkthrough. A phone kept off-camera sidesteps that cleanly.

Presentations — internal talks, thesis defenses, conference panels, pitches — aren't stealth situations. You're running the room. The concern here is accidental: a projector or video call connected to your computer can display whatever's on your screen, including HearQA's window. A phone at your side during audience Q&A keeps AI answers to your eyes only.

Practice is the catch-all recommendation for anything high-stakes. Upload your study materials, job description, past exam papers, textbook chapters, interview notes, company battlecards, whatever you're preparing for. Run sessions in the same scenario type (Interview, Exam, Certification, Conversation, Presentation) you're preparing for; the AI adjusts its coaching style. There's no timer, no limit, and no one watching because there's no exam.

The most valuable pattern we see: users take 3–5 practice runs in the same scenario before the real one. By the third run, the AI has learned what trips them up, they've heard the same question three times in three different ways, and the real session becomes a confidence exercise instead of a first-time stumble. This is what HearQA is built for.

Practice has six sub-types. Mock Interview drills behavioral and technical questions matched to a job description. Exam Questions generates multiple-choice / short-answer / essay items from study materials. Coding Challenge poses LeetCode-style problems and grades correctness, complexity, code quality, and edge cases. Presentation Q&A simulates a skeptical audience reading your slides. Sales Roleplay has the AI play a client raising real objections about price, timeline, or competition. Free Study is open-ended Q&A with no scoring — best for last-minute review.

After each practice session the score and per-answer evaluation appears on the Practice progress page (`/portal/practice/`). Trend across sessions, weakest dimensions, and a streak counter — useful for catching whether you're actually improving or just feeling more comfortable. The page only shows up after your first practice session, so the dashboard stays focused for users who only do live sessions.

Interview — phone position matters. Lay the phone flat just below or behind your laptop screen, never holding it up. The eye-line indicator in the session-creation card shows the geometry: your eyes stay roughly level with the laptop screen, the phone catches your downward glance as a natural blink-and-look-back rather than a sustained off-screen stare. Sustained gaze drift is the #1 tell trained recruiters look for, ahead even of audio anomalies.

Interview — use your own words. Read the AI's answer, then say it the way you'd actually speak. Verbatim reading sounds generated and fluency-flatlines (the same cadence on every answer) are the second-biggest red flag after gaze drift. Treat the AI output as a structure to riff on, not a script to recite.

Interview — some platforms are out of scope. Switch to Practice if your interview is on HireVue async (Unilever, Hilton, JPM-style screening), Karat managed (Citi, Roblox, Indeed, Wayfair), or includes a full-screen-share coding round (rising at Google, Meta, parts of Goldman tech). Those watch your gaze, voice timing, or your whole screen — the phone-stealth thesis breaks the moment your whole monitor is shared.

Sales / Presentation — set displays to Extend, not Mirror. If a projector or external display is plugged in, configure your operating system to extend (macOS: System Settings → Displays; Windows: Win+P → Extend). Otherwise the projector mirrors whatever's on your laptop screen — including HearQA's answers. The session-creation card detects external displays via the Window Management API and surfaces this warning on the Presentation template (Chromium only — Safari and Firefox don't expose the API).

Conversation — phone for camera-on calls. Same logic as Interview: the client may ask to share your screen mid-call for a demo or walkthrough. A phone kept off-camera sidesteps that cleanly. Tab-audio capture (desktop Chromium only) is useful when you're on the same laptop as the meeting and want to capture the client's side of the call; on phone, your microphone still hears both sides if the phone is near your speakers.

Exam / Certification — confirm unproctored before starting. The session-creation form requires an attestation: "I confirm this is unproctored — no webcam monitoring, no lockdown browser, no live human watcher." If any of those apply, the session-creation card surfaces a red "This looks proctored" warning when the topic mentions a known proctored platform (Proctorio, OnVUE, etc.) and recommends switching to Practice. The platform fit matrix above is the authoritative source for which platforms qualify.

The 2024–2025 explosion of AI interview-assistance tools forced a structural reaction. Per Fabric's "State of Cheating in Interviews 2026" report, ~35% of candidates showed AI-cheating signs in late 2025 — more than double the H1 2025 rate — and over half of candidates use AI on coding challenges. Gartner: 72.4% of recruiting leaders are now running more in-person interviews specifically as an AI-cheat countermeasure (Computerworld).

Concrete moves: Google piloted in-person SWE rounds at Bay Area, Seattle, NYC, Poland, and Bangalore through 2025 and is rolling out a "2 virtual + 3–4 in-person" loop for all software-engineering roles. McKinsey brought back in-person final rounds for consulting hires. Cisco, Anthropic, OpenAI, and several large banks (Goldman, JPM tech) made similar moves. For finance superdays in NYC and London the on-site coding test on a company laptop is increasingly the norm again.

Detection tooling launched in 2025 that you should be aware of. Truely (built by Columbia students, July 2025) is an open-source tool that asks candidates to install a background app for real-time detection — visible and opt-in, but spreading at smaller orgs. Fabric claims an 85% Cluely detection rate via timing-flatline + gaze-pattern analysis and is being adopted as a post-interview review tool. HireVue's 2025 product literature explicitly markets gaze + voice + timing as fraud signals. HackerRank shipped Proctor Mode in July 2025 claiming 85–93% precision on ChatGPT-assisted code submissions. Codility expanded its behavioral-events detection with snapshot capture and typing-rhythm analysis.

What this means for HearQA users: live-assistance during the interview is getting harder; preparation is getting more valuable. If your target company is FAANG, a top consultancy, or top-bracket finance, assume the interview will be at least partly in-person, and shift your prep weight from "live copilot" to "Practice mode rehearsals." This is the structural argument for Practice as the long-term core use case.

Specific platforms to steer away from to Practice rather than fight: HireVue async (Unilever, Hilton, JPM-style screening — gaze + voice + timing analysis), Karat managed (Citi, Roblox, Indeed, Wayfair — a trained Interview Engineer is watching live, this is the hardest human-watcher in the industry), and any round where the interviewer asks you to share your full screen for a coding challenge (rising at Google, Meta, parts of Goldman tech). The phone-stealth thesis breaks the moment your whole monitor is shared.

The platform-by-platform verdicts above are the strategic answer — does this scenario fit the product or not. Once you've decided HearQA fits the moment you're facing, the deciding factor stops being "which platform" and starts being "how prepared are you." That's a different problem.

For interviews and conversations, the single highest-leverage preparation is uploading the source material into HearQA's document library — job description, resume, company research, customer-account notes, product battlecard, whatever frames the moment. Once those documents are in, every AI response during the live session is grounded in YOUR context, not generic web content. A behavioral question gets answered with your actual past projects; a technical question pulls from the system you actually built; a sales objection gets handled with the pricing your prospect actually quoted.

For exams and certifications you've confirmed are unproctored, the same logic applies: upload the syllabus, the textbook chapters that map to it, your own notes, any practice-test PDFs you've worked through. The Practice scenario then runs you through generated mock questions with full coaching, and the live exam (when the time comes) has your full prep context to draw on if you reference it.

For anything we've flagged as proctored or otherwise off-limits for live use, Practice is the entire answer. Most users we see hitting Practice take 3–5 rehearsal runs in the same scenario before the real one. By the third run, the AI has learned what trips them up, they've heard each likely question multiple ways, and the real session becomes a confidence exercise instead of a first-time stumble.

If you're an active subscriber and wondering about the operational details — phone placement, audio configuration, mid-session controls, pre-flight setup — those tactics live in the portal under Live Session Tips, alongside the rest of the active-user reference material. We keep them inside the authenticated experience because the responsible default is "prepare well, not hide better."