What integrity signals does Kendor record?
Este artículo aún no está traducido, así que se muestra en inglés.
With proctoring on, Kendor logs tab switches, outside pastes and fullscreen exits, with times. It never decides anything from them on its own.
When you turn on Proctoring for a screen, Kendor logs each time the candidate leaves the page, pastes text from outside the editor, or leaves fullscreen, with the time of each. Reviewers see the log in the Activity tab. Kendor never rejects, fails or scores anyone because of it: the signals are there for a person to read.
Turn proctoring on
Open the screen and turn on Proctoring under Options. Its description reads "Track tab switches, external pastes and fullscreen exits during the attempt." It's off by default, and it applies to every challenge in the screen. See Screen settings.
With proctoring off, none of these signals are collected.
What candidates see
Candidates know before they start. On a proctored screen, the start page asks them to stay on the tab.
While they work:
- The editor asks them to go fullscreen, with an Enter fullscreen button. If they leave fullscreen, the editor covers up again until they go back in, and it tells them how many times leaving has been logged. Their work saves the whole time.
- When they leave the tab or paste from outside, a warning appears at the top of the editor saying it has been logged, and how many times.
- The editor's preview only opens their own app, not outside websites.
What Kendor records
With proctoring on
| Signal | When it's counted |
|---|---|
| Tab switch | The page is hidden (another tab, a minimized window) or the browser window loses focus (switching to another app). One leave is counted per absence, and the time away is recorded when they come back. |
| External paste | Text is pasted into the code editor that wasn't copied inside the editor. Kendor keeps the pasted text so you can read it. |
| Fullscreen exit | The candidate leaves fullscreen. |
Clicking into the preview or the terminal inside the editor doesn't count as leaving. Moving code around inside the editor with copy and paste doesn't count as an external paste.
For a written-answer challenge, tab switches and outside pastes are recorded the same way. The fullscreen requirement applies to code challenges.
On every coding screen
Some things are captured whether or not proctoring is on, because they're part of reviewing the work:
- Edit replay. Changes in the code editor are recorded so reviewers can replay them in the Timeline tab.
- Live files. While the candidate works, your team can see their files. The start page tells candidates this.
- Terminal and AI assistant. When the terminal is recorded, the start page says so, and reviewers can replay it in the Terminal tab. If AI assistants are on too, the conversation with the assistant is saved and shown under AI agents.
Kendor doesn't use the candidate's camera or microphone, and it doesn't record their screen.
Where reviewers see the signals
The Activity tab
On the review page, each challenge has an Activity tab. It shows:
- a Proctored or Not proctored badge, so you know whether signals were collected at all
- counts for Tab switches, External pastes and Fullscreen exits, with the total time away
- a timeline, line by line, such as "Away from the screen for 2m 10s", "Pasted 412 characters from outside" or "Left fullscreen", with the pasted text underneath, ending with Submitted
The timing is what makes the counts useful. A two-second glance away reads very differently from twenty minutes out of the tab.
Flags and alerts
When a challenge has recorded signals, a small flag with a count appears on that screen in the candidate's row on Candidates and on their profile. When the candidate submits a challenge with signals, every member also gets an in-app notification, and members who keep Integrity flags on under Settings → Notifications get an email.
Read signals with care
Kendor reports what the candidate's browser saw. It can't see why.
- Leaving isn't cheating. Candidates switch tabs to read documentation, check a message, or look something up, which is often allowed. Agree as a team on what you expect, and say so in the screen's description.
- Developer tools count as leaving. When focus moves to the browser's developer tools, the browser can't tell that apart from switching apps, so it's counted.
- Read pastes, not just the count. A pasted error message or a snippet from the challenge's own instructions is different from a pasted solution.
- Look at the code too. The Timeline replay shows how the solution came together, which says more than a counter.
What Kendor never does
- It never changes a rating, recommendation or decision because of a signal. Those are always set by a person on your team.
- It never emails the candidate about a signal.
- It never ends an attempt because of a signal. The timer keeps running and the work keeps saving.
For a review process that treats every candidate the same way, see Review take-homes fairly.