Before you start
- If you don’t see these controls, contact your dedicated CS Manager or support@heymilo.ai (or in-app chat).
- Candidates to use a current browser; allow camera and microphone when prompted (needed for video-based signals).
Browsers (keep updated): Chrome (best tested), Edge, Firefox, Safari (macOS/iOS). Other Chromium-based browsers (Brave, Opera, Arc, etc.) usually work. Internet Explorer is not supported.
1) Workspace default (usual starting point)
Path: Sidebar → Interviewers → Tools → Interview Integrity
Use this when you want one default across interviews.
Settings
- Enable Cheat Detection: Workspace-wide on/off for interviews that use these defaults.
- Detection Threshold (0–100): How strict flagging is. Lower = fewer flags; higher = more. A practical starting point is ~70.
- Detection Types: Which signals to monitor (see below). Use Select All / Deselect All.
Click Save Settings.
2) Per interviewer (override)
Path: Create or Edit Interviewer → Voice/Video (web interview) workflow step → Settings (cheat detection section)
Same controls as the workspace page: enable, threshold, detection types. These apply only to that interviewer and override workspace defaults for that flow.
Detection types (what they mean)
Signals are observational—they indicate something looked unusual, not intent.
| Type | What it’s looking for |
|---|
| Facial Behaviour | Sustained or repeated looking away from the screen (e.g. notes or another display). |
| Multiple People | More than one person visible in frame during the interview. |
| Phone Detection | A mobile device appears in view. |
| AI/Scripted Answer | Answer patterns that resemble scripted or AI-like structure/timing (heuristic, not proof). |
| Unusual Delays | Long or inconsistent pauses that may suggest off-screen help or lookup. |
| Tab Switching | Candidate leaves the interview tab/window during a response. |
Reviewing results
Path: Interviewers → [candidate] → Diagnostics & Analysis
Open Cheat Detection Overview (or equivalent). You’ll typically see:
- Events grouped by type
- Timestamps
- Confidence / strength per event (stronger signal ≠ automatic guilt)
- A synced player or jump-to-moment behavior to review video + context
How to read confidence
- Treat high confidence as “worth a careful look,” not “confirmed cheating.”
- Moderate: check context (question difficulty, nerves, environment).
- Low: often lighting, angle, movement, or one-off glitches.
Patterns beat single blips: repeated signals, several types together, or spikes on hard questions matter more than one low-confidence event.
What cheat detection does not do
- Does not auto-fail or auto-advance candidates
- Does not raise or lower the interview score
- Does not replace recruiter judgment
- Does not use biometrics for “identity” decisions in the sense of facial recognition hiring outcomes—think behavioral / environmental signals for review
Flags are informational. Always pair them with transcript, answers, and video context before conclusions.
Best practices
- Start near threshold 70, then tune if you’re flooded with noise or missing what you care about.
- Only enable detection types you’ll actually review.
- Give candidates clear setup (quiet room, stable camera, good light, supported browser).
- Align as a team on how you interpret flags so decisions stay consistent.
Troubleshooting
| Issue | What to check |
|---|
| No cheat detection data | Feature disabled; interview very short; camera/mic denied; unsupported browser. |
| Too many flags | Lower threshold slightly; improve candidate instructions and environment. |
| Weird inconsistency | Browser updates; lighting; camera placement; connection quality. |
Next steps
Help: support@heymilo.ai or in-app chat.
