For candidates

The interview tool that doesn’t make you hate the interview.

Solve real problems in your real editor. We respect your setup, your time, and your privacy. Here's what to expect.

Walkthrough

Three steps from zero to your first round.

Step 1

Install the extension

Search for Proctord in the VS Code marketplace and install. It's a single side-panel extension. No background daemon, no system permissions, no autostart.

Step 2

Sign in with your invite

Open the Proctord panel, paste the invite code from your email. The link binds to your account on first use, so nobody else can use it.

Step 3

Solve in your real editor

Visible test cases run on every save, hidden tests run on submit. You see verdicts in real time. Submit when you're ready. That's it.

Why it doesn't suck

Four specific decisions, in plain language.

Most coding-test products treat candidates as a threat surface. We don't.

Your shortcuts work

Vim mode, multi-cursor, your custom snippets, Copilot — whatever you have configured. The interview should feel like a normal day, not an exam booth.

Your theme works

Light or dark, your fonts, your color scheme. We don't override anything. If you've spent six months tuning your editor, that work isn't wasted at the worst possible moment.

No browser tab spying

We don't track which tabs you switch to or what you Google. We capture two specific signals — large pastes and editor focus loss — and we tell you exactly that, on this page.

Pastes detected, keystrokes ignored

We log the size and timing of paste events larger than 200 characters. We don't capture keystroke timing, mouse movement, or anything that would penalize people who type differently than the average.

FAQ

Specifically for candidates.

Privacy, fairness, and what to do if something goes wrong.

What data does Proctord collect during my interview?

Your code as you submit it, the timing and size of paste events larger than 200 characters, focus-gained and focus-lost events on the editor window, and verdicts from running your code. That's the complete list. No keystroke timing, no mouse movement, no webcam, no microphone, no screen capture, no browser tab tracking.

Does Proctord see my private repositories or other files?

No. The extension only reads files inside the assessment's working directory, which we create for you in a sandboxed location. Your other VS Code workspaces, your Git history, and your filesystem at large are off-limits.

What happens if my laptop crashes mid-interview?

Your work is saved locally on every meaningful edit, signed with a per-attempt key. When you reopen VS Code and unlock your assessment, you pick up exactly where you left off. The interview clock pauses if your machine goes offline.

Can I use Copilot or other AI tools?

It depends on what the company hiring you decided. The interviewer sees this option when they create the assessment. If they allowed AI tools, Copilot will work normally. If they didn't, you'll see a notice in the panel.

Can I get my data deleted afterwards?

Yes. Email privacy@proctord.dev from the address you used during the assessment, and we'll delete your submissions and telemetry within 30 days. We confirm by email when it's done.