Skip to content

Coding screens · async take-homes

Take-homes in a real IDE. Reviewed by people, not a score.

Candidates get VS Code, a terminal, a running preview of their app and language servers, all in the browser. They run your project's tests from the Tests tab as they work, and your reviewers judge the code, the diff and how it was built.

A reviewed session

A real screen, then its review.

From repository to decision in a minute: Maya builds the screen with Claude, Ada works with AI and checks her work, then Maya replays it and decides.

01

Three question types, one time limit.

Combine full projects, single-file exercises and written questions in one screen. The time limit covers the whole screen, and candidates move between questions freely.

02

Candidates run your tests as they work.

Put test files in the project like in any repository. Candidates run them from the Tests tab or the terminal as often as they like, and see what passes before they submit.

  • The same pinned versions and dependencies for every candidate.
  • Passing tests don't decide anything: a reviewer reads the code.

03

Integrity signals, shown as evidence.

With proctoring on, tab switches, external pastes and fullscreen exits are logged with timestamps, and the Timeline tab plays the code back as it was written. Kendor doesn't turn them into a score. A reviewer reads them and decides what they mean.

04

Check they understood what they shipped.

With an AI agent, anyone can produce passing code. So after each coding challenge, candidates answer three questions about their own changes, four minutes each, with no editor and no AI. Each answer is checked against the code and marked for your reviewer, with the line it refers to.

  • Questions are written from the candidate's own diff, so they can't be prepared in advance.
  • Nothing rejects anyone: the answers are evidence for your reviewer.

05

Attach a screen to a job posting.

Applicants get the screen the moment they apply, as a link on the confirmation page and an invitation email, so nobody sends invites by hand. Choose No screen and applications wait for manual review instead.

06

Every reviewer gives their own verdict.

Reviewers read the code, the diff and the activity, then each records a recommendation from Strong no to Strong yes, with a note the others can read. Then someone on the team advances or rejects the candidate.

How it works

From repository to decision in three steps.

  1. Build the screen

    Import a repository or start from a single file, add tests like in any repo, and set the time limit.

  2. Send it, or attach it to a role

    Invite candidates directly, or let applicants receive it when they apply.

  3. Review and decide

    Each reviewer reads the work and records a recommendation, and you advance or reject.

Questions

Can candidates see the tests?

Yes. Tests are ordinary files in the project, like in any repository, and candidates run them from the Tests tab or the terminal as often as they like. Passing tests doesn't decide anything on its own: a reviewer reads the code and decides.

Does Kendor reject candidates automatically?

No. The code, the transcripts and the integrity signals are inputs for reviewers. A person advances or rejects every candidate.

Do candidates need to install anything?

No. They open the link from their invitation in a browser and land in the IDE with the project's dependencies, terminal and preview ready. No webcam, no browser extension, no desktop app.

How do I know the candidate understood their code?

Turn on the explain-your-code check for the screen. After each coding challenge, the candidate answers three timed questions about their own changes, with no editor or AI and pasting blocked. Each answer is checked against the code and shown to your reviewers with the lines it refers to. It uses your organization's AI key.

Read the docs

More of Kendor

All features

Run your next screen on Kendor. Read what the code says.

Create your workspace, import a repository or start from a template, and send your first screen today.

Hiring at scale? Talk to us