Can TestGorilla detect cheating? Reading the Reddit reports
By Aaron Cao · Updated
Yes, within limits, and the disagreement on Reddit has a simple cause: TestGorilla's anti-cheating features are settings each employer turns on or off. Two candidates describing the same platform can honestly report different experiences.
Why do the Reddit threads contradict each other?
You have probably read one thread saying the test took webcam photos throughout and another saying nothing happened at all. Both can be accurate. This section explains the mechanism behind that, because it changes how much weight any single report deserves.
TestGorilla sells an assessment product to employers, and the monitoring is configurable on the employer's side. A recruiter builds an assessment and chooses which controls to switch on. One company enables snapshots and full-screen enforcement; another sends the same skills test with neither. The candidates then write up their experiences, and the accounts do not match.
The practical consequence: read community threads as reports about specific configurations, not as documentation of the platform. The only configuration that matters to you is the one in your invitation.
What can TestGorilla actually record?
The controls that turn up consistently across accounts are worth knowing on their own terms:
- Webcam snapshots. Still images captured at intervals during the test, not continuous video. This is the one candidates notice, because the browser has to ask permission.
- Full-screen enforcement. Leaving full screen is detected and recorded, sometimes with a visible warning.
- IP address logging. Recorded with the submission, which is how one person taking two tests becomes visible.
- One attempt per invitation. Retakes are blocked unless a recruiter reissues the link.
- Randomized questions. Items drawn from a larger pool, so two candidates rarely see the same set.
What is not on that list matters too. There is no reliable authorship detector for a written answer, and no screen recording of your whole machine. Comparable breakdowns for other assessment vendors sit on the detectability topic hub.
How do you tell which settings your test uses?
Check before the timer, not after. The invitation email and the page in front of the Start button describe the controls in plain language, and any camera requirement forces a browser permission prompt you cannot miss.
A customer support candidate applying to a mid-size SaaS company read a thread predicting constant webcam recording, then opened the assessment and found a short skills test with no camera request at all. The hour spent worrying was the real cost. Two minutes on the pre-test screen would have answered it.
Randomized question pools also mean the question lists shared in community threads are of limited use. Practising the underlying skill transfers; memorising a leaked item does not.
Where SubcueAI fits, and where it does not
SubcueAI assists live spoken interviews. The native macOS and Windows app captures system audio plus your microphone and shows suggestions in a floating local overlay; the browser extension's Side Panel does live assist for a meeting tab on Chromium browsers, capturing that tab's audio only. No meeting bot joins the call, and nothing is injected into the meeting page.
A TestGorilla assessment is a timed solo test, so none of that applies, and a snapshot-monitored round is out of scope by design. The rounds it is built for come after: the recruiter call, the hiring manager conversation, and the panel interviews. What SubcueAI captures and stores in those rounds is documented on the security page.
If the assessment stage is where you keep stalling, timed rehearsal is the direct fix, and it runs on the mock interview page.