Live pair coding
One link for the candidate. One sandbox for everyone.
Send a link; the candidate doesn't need an account. They wait in a lobby until you let them in, then everyone works in the same editor, terminal and running app, with a whiteboard and a video call built in.
{
"allowed": true,
"remaining": 4,
"window": "60s"
}01
No account. A lobby, then you let them in.
The candidate opens the link, enters their name and email and checks their camera. There's nothing to install and nothing to sign up for. They wait in the lobby until a host admits them, so the session starts when you're ready.
- Start a session right away, or schedule it and send the invitation
- Any host can admit or deny, and remove someone from the session
02
Draw it, then build it, in the same room.
The whiteboard sits next to the code, so a system-design question can turn into code without switching tools. When a host moves the room between the board and the code, everyone moves along. Talk it through on the built-in video call.
- Live cursors, and follow anyone's view on the board or in the editor
- Screen sharing in the call, and a host can mute or remove anyone
03
AI agents on or off, per session.
To see how someone works with Claude Code or Codex, turn agents on for that session. To see them without, leave them off. The agents run in the sandbox terminal on your organization's API keys. A host can flip the switch during the session, and everyone in the room sees which way it's set.
04
The code stays. Every interviewer records a verdict.
When the session ends, Kendor keeps the final code and the whiteboard for review. Each interviewer records their own recommendation and note while it's fresh, and the team makes the Advance or Reject call from what's written down.
- Attendance shows who was in the room, when, and how much each person typed
- MCMaya Chen · just nowTalked through the failure modes before writing any code.Strong yes
- JWJonas Wirth · just nowGood instincts on the sliding window; slower on the tests.Lean yes
How it works
Set up in a minute, run for an hour.
Create a pair coding
Import a repo, or start blank or from a template. Add the interviewers and choose whether AI agents are on.
Send one link
Start now or schedule it. The candidate joins the lobby and a host lets them in.
Pair, then write it down
Work together in the sandbox. Afterwards each interviewer records a verdict next to the final code.
Questions
Does the candidate need an account?
No. They open the link, enter their name and email, and wait in the lobby until a host admits them.
Which languages can we pair in?
Any runtime Kendor offers — Node/TypeScript, Python, Go, Java, Rust, C++ and PHP — as a single file or a full project with a running preview.
Is the call recorded?
No. Kendor doesn't record audio, video or shared screens. After the session it keeps the final code, the whiteboard and each interviewer's verdict.
Who joins as an interviewer?
The interviewers you add to a pair coding join the panel of every session, alongside whoever starts it. Each of them sees live cursors and can follow anyone in the room, the candidate included.
More of Kendor
All features- Coding screensAsync take-homes in a real browser IDE, graded on a clean re-run.Read more
- InterviewsSelf-booking, invites that update in place, live review.Read more
- AI agentsClaude Code and Codex in the candidate's terminal, on your keys.Read more
- Real environmentsSeven pinned languages, PostgreSQL and Valkey, one kendor.yaml.Read more
- Repo importCloud or self-hosted Git, private repos too, one fixed snapshot.Read more
- EnterpriseAshby integrationAshby stages send the screen; results come back as fields.Read more
Run your next screen on Kendor. Read what the code says.
Kendor works with engineering teams in the EU, the UK and the US. Tell us what you're hiring for and we'll set up your organization with you.