Invite Candidates
An invitation ties one candidate to one assessment and produces one attempt.
Sending an invitation
From the assessment, choose Invite. Add a name and an email address. You can add candidates one at a time, paste a list, or upload a CSV with name and email columns.
Each candidate gets their own link. Links are personal — they identify the attempt and cannot be shared or reused by someone else.
Set an expiry
Give the invitation a window rather than leaving it open indefinitely. Two weeks is generous for most processes. An expired link can be reissued in one click.
The expiry is a deadline for starting, not for finishing. Once a candidate starts, they have the full time limit.
What the candidate sees
- Your organization name and logo, and the role
- The time limit, and what the task will involve
- What the workspace provides — editor, terminal, tests, AI agent
- A device check that must pass before anything begins
- A Ready to Start screen they control
The task itself is not readable until they click Start. Nobody gets a preview.
What you must tell them
Before the assessment, candidates must know that the session is recorded and scored with AI assistance. Link the Candidate Privacy Notice in your invitation or job posting. Depending on where you hire, you may also owe candidates a formal notice or a bias-audit disclosure — that obligation is yours, not ours.
Also send them Taking a Ducker Assessment. A candidate who knows how the agent behaves spends their time on engineering instead of on the interface.
Bulk sends
For a large batch, stagger sends across a couple of days rather than all at once. Support requests arrive in the first hour after an invitation lands.