Technical challenges & interviews
Watch candidates build. Ask better questions. Bring your recruiting team’s ratings, notes, and recommendations into one hiring record.
A checkout retry creates two orders. Find the cause and stop the duplicate.
The candidate traced the retry path and added a check for an existing order.
How it works
Use a coding task for a technical challenge, or a question template for an interview.
Add recruiters or a team, or share one recruiter link. Only signed-in recruiters in your organization can join.
Each recruiter records their own ratings, notes, and Go or No go. Follow every stage in the candidate’s journey.
For candidates
Candidates work in a browser workspace with the task, codebase, tests, and an AI agent. The timer and token budget remain visible throughout the attempt.
Check whether the retry path can reach order creation twice.
For hiring teams
Technical sessions preserve code and test evidence. Interviews preserve each recruiter’s response ratings and notes. A candidate journey brings the stages together.
Illustrative review recordInspect the final files and the candidate's changes without leaving the attempt.
const existing = await findOrder(key)+ if (existing) return existingRead the prompt history in order. Check which model they used and how many tokens the attempt consumed.
Check whether the retry path can reach order creation twice.
See which hidden tests passed or failed and inspect how the final score was calculated.
Get started