EasyEnv
Cheating detection · built for real engineering interviews

Know when a candidate
is being fed the answer.

EasyEnv catches the signals that matter: pasted solutions, time spent off-screen, and answers that could only have come from somewhere else.

But the strongest defense is not surveillance. It is a task that cannot be Googled or copied. Our challenges are real broken systems, so a memorized answer or a pasted snippet simply does not work.

EasyEnvReplay
Replay timelinecandidate-7af3 · senior-sre
  1. 00:00Session startedClean
    Fresh Linux VM provisioned, recording on
  2. 01:12First commandNoted
    systemctl status nginx
  3. 02:48Paste detectedFlagged
    412 chars from clipboard into the editor
  4. 03:05Tab hiddenFlagged
    Left the interview tab for 41s
  5. 03:46Returned, pasted againNoted
    1 line, looks like a copied command
  6. 07:20Real debuggingClean
    Edited config, restarted, read logs, no paste
This is cheating

Hidden help that hides who actually did the work.

A pasted solution someone else wrote. A friend on a second screen. A leaked answer key. An impersonator sitting the test. These break the one thing an interview is for: finding out what this candidate can do.

This is not

Using AI well, when you let them.

If the role uses Claude or Copilot every day, banning it in the interview tests the wrong thing. EasyEnv lets you allow AI and score how well they use it. Cheating detection is about hidden help, not honest tools.

Three signals, one honest picture

What EasyEnv watches for.

No webcam spyware, no keystroke biometrics. Just the behavioral signals that tell you whether the work in front of you is really theirs, attached to the moment they happened.

Paste detection

We see every paste

When a candidate pastes into the editor or terminal, EasyEnv captures it: how many characters, from where, and at what point in the task. A 400-line solution pasted in one keystroke reads very differently from a developer who typed their way to it.

  • Paste size and frequency, timestamped
  • Editor and terminal both covered
  • Linked to the exact code change it produced
Focus and tab tracking

We know when they leave

The moment the interview tab loses focus or the window is hidden, the clock starts. You see how often a candidate left, for how long, and what happened right after they came back. A 40-second detour followed by a perfect paste is a story worth reading.

  • Tab-hidden and window-blur events
  • Time spent off-screen per excursion
  • Correlated with the next action in the session
Cheat-resistant by design

The answer is not on Google

Our challenges are real broken systems, not textbook puzzles with a known answer. The fix depends on the actual state of that VM, so there is nothing to search for, nothing to copy off Stack Overflow, and no leaked answer key to pass around. A model can help reason, but it cannot hand over the answer.

  • Intentionally broken, unique machine state
  • No memorizable or pasteable solution
  • Rewards diagnosis, not recall
The real defense

You cannot copy an answer that does not exist.

Most cheating works because the question has a known, shareable answer. Algorithm puzzles live on LeetCode. Trivia lives on Stack Overflow. The answer key gets passed around in a group chat before your candidate even logs in.

EasyEnv challenges are different. Each one is a real Linux machine put into a broken state on purpose. The fix depends on the actual condition of that specific box, so there is nothing generic to search, paste, or memorize. Candidates have to diagnose, reason, and act, which is exactly the skill you are hiring for.

  • Unique, intentionally broken machine state per challenge
  • No public answer key, no reusable copy-paste fix
  • Auto-graded on the real end state, not on matching a string
  • Works the same whether you allow AI or not
EasyEnvWhy copy-paste fails
Candidate searches
?nginx 502 after deploy fix
Returns 2.3M generic results. None of them know this VM has a stale upstream socket and a permissions drift introduced for this exact challenge.
Pastes a generic answer
$ sudo systemctl restart nginx
Still 502. The copied fix does not touch the real cause.
Real diagnosis wins
journalctl -u nginx → find stale socket → fix perms → reload
Only a candidate who understands the system gets here.

Every flag is backed by the recording.

EasyEnv never accuses anyone. It hands you the evidence and lets a human decide. The whole session is captured so a flag is always one click from the moment it happened.

Full session replay

Screen and terminal are recorded end-to-end. Scrub to any flagged moment and watch what the candidate actually did, in context.

Signals, not verdicts

A paste or a tab switch is information, not a conviction. There are honest reasons for both. You see the timeline and make the call.

Same task, fair compare

Every candidate runs the same broken box with the same rules. Integrity signals line up side by side, so review is consistent, not vibes.

Stop screening for who can copy fastest.

Run an interview where the answer cannot be Googled, the pastes are visible, and the recording settles every doubt. Set one up on EasyEnv in under 10 minutes.

Cheating Detection for Technical Interviews | EasyEnv