How do you know the candidate is who they say they are?
Take-homes and challenges are unproctored by design. There is no webcam, no screen recording and no lockdown browser — the candidate works on their own machine, in their own time.
What you get instead: the invite link can be single-use, so it stops working once it has been opened and completed; paste and tab-switch activity is logged while they work and shown to the reviewer on a timeline beside the code; and the live interview round is where identity is actually established, because you are in the call watching the person type.
Anything else would be a claim about a machine we do not control. What the activity timeline gives you is the thing to ask about in the live round.
What do you record while a candidate works?
Snapshots of the code as they type, so nothing is lost if their laptop dies; each submission and its results; and paste and tab-switch events.
Candidates are told all of it before they start and have to accept it to begin. Nothing is recorded silently.
Do candidates need an account?
No. They open the link you send, write code in the browser and submit. No signup, no install, nothing to download.
Which languages can candidates use?
JavaScript, TypeScript and Python. Code runs in the candidate's browser, so there is no environment to set up and no server to wait for.
What does it cost?
$20 a month, flat, however many people you invite — we do not charge by the head. Unlimited sessions, unlimited questions, unlimited teammates.
Every account starts with a 14-day free trial and no credit card. The sandbox is free forever and needs no account at all.
Do you support SSO, or a security review?
Not today. SSO, SAML and a signed DPA are not part of the first version, and the honest thing is to say so before you buy rather than after.
If any of that is on your checklist, talk to us and we will tell you plainly where things stand.