TL;DR
Codility tracks tab switching when proctoring is enabled, logging every time you leave the test tab, how long you were gone, and how many times you left. It also monitors screen recordings, webcam feeds, and paste events across every test. Codility's proctoring runs in the browser and cannot scan processes on your operating system. Browser extensions get caught because they exist inside the browser that Codility records. InterviewMan at $12 per month on annual billing runs as a desktop app outside the browser with over 20 stealth features including screen capture blocking, dock hiding, Activity Monitor evasion, and process name masking. It has 57,000 users with zero confirmed detections on Codility or any other proctored platform. The key to avoiding detection is typing code yourself with natural editing patterns, since the paste monitor flags code that appears without being typed and the plagiarism engine now includes AI output pattern matching. Test your setup with a practice recording before any real Codility assessment.
ok so i lost a $180k offer over a Chrome extension four months ago and i am still not over it. I was running this browser tool during a Codility test that i thought was just a normal timed assessment. Turns out the company had screen recording turned on and nobody told me. Got a one-line recruiter email the next week, "irregularities observed during the assessment review." I sat in my car after reading that email for probably ten minutes before i drove home.
That weekend i went to my coworker's place, he runs Codility hiring at his company, and i basically refused to leave until he showed me everything. He pulled up the hiring dashboard on his laptop and walked me through it while we ate pizza. The tab switching part freaked me out first, every time you leave the test tab when proctoring is on, Codility logs it. When you left, how long, how many times. He said the hiring team sees this timeline sitting right next to your code and most managers look at the flags before they read a single line. A couple quick switches probably wont kill you, he told me interviewers look at context, but if you leave for thirty seconds before each problem and come back with clean code that pattern jumps off the page.
Then he showed me the screen recording viewer and i felt dumb. When my test loaded it asked me to pick between sharing a tab, a window, or my whole desktop. I picked tab thinking that was the safe choice and it did not matter because my extension was IN the browser lol. My coworker said if you share your whole desktop with ChatGPT open in another window the recording just sees ChatGPT sitting right there. Tab-only sharing logs the switches but cannot see where you went, which is better but my extension was visible in the browser either way so it did not save me.
Then he brought up paste monitoring and honestly that was the scariest part. That runs on every Codility test, proctored or not. Code that appears without being typed gets flagged with a timestamp. My coworker said their plagiarism engine checks against past submissions, GitHub repos, Stack Overflow, and in 2025 they added AI output pattern matching too. Typing rhythm matters, if you sit there slow for twenty minutes then suddenly fifty clean lines appear in ninety seconds nobody reviewing that believes a human wrote it under pressure. That described Jake from my study group almost exactly, he had the same pattern on his CodeSignal and got thrown out.
The thing my coworker said that actually calmed me down though. Codility runs in the browser. The proctoring watches the assessment tab, webcam, and screen recording. Thats the wall. It cannot scan what processes are running on your machine. A desktop app that never touches the browser page, Codility has no mechanism to detect it. My Chrome extension got caught because it was inside the same browser Codility was recording. A reviewer saw it in a frame before any automated system even flagged anything.
After that disaster i switched to InterviewMan at twelve bucks a month annual. Desktop app, 20 plus stealth features baked into the base price. Used it on one proctored Codility and one unproctored since switching. Zero flags on either. I checked my own screen recording frame by frame after and the overlay was not there. Hides from screen capture, dock, Activity Monitor, process list. My typing looked normal because i read the hints and wrote code my own way with deletions and corrections and the normal mess you expect to see from a real person.
57,000 users, 4.8 stars from 257 reviews. I searched specifically for anyone getting caught on Codility with InterviewMan and could not find a single report. Twelve bucks with everything included, no seventy five dollar stealth addon like Cluely charges and no ninety minute session cap like LockedIn at fifty five.
Before your Codility figure out if proctoring is on. Some companies never tell you. Run your own screen recording during a practice session and watch the footage back. If you can see your tool the hiring team can see it too. I learned that the hard way and it cost me a hundred and eighty thousand dollars.
For a full ranking of tools by stealth, see our top 4 undetectable interview assistants for 2026.
Our stealth interview AI guide covers all three detection methods companies use.
For details on how other platforms handle detection, see does HackerRank detect AI tools and does CodeSignal detect cheating.
Ready to Ace Your Next Interview?
Join 57,000+ professionals using InterviewMan to get real-time AI assistance during their interviews.
