Guides
These guides answer the questions hiring teams ask when they design a technical interview: how to run a live coding session, how to build a take-home that feels like the real job, and how to review the work fairly. Each one starts with advice that holds whatever tool you use, then shows how to do it in Kendor.
How to run a live coding interviewPrepare one realistic problem, let the candidate drive while you observe, keep time loosely, and write your verdict alone before the panel talks.How to build a take-home assignment with a real databaseGive candidates a real PostgreSQL or Valkey instance, seed it with a small SQL file, and write tests that hit it. No mocks, no local setup.Should you allow Claude Code in technical interviews?Allow AI agents when the job uses them, set the task and token budget to match, tell candidates upfront, and review the transcript alongside the code.How to build a take-home from your company repositoryCut a small, runnable slice of your real codebase, strip secrets and history, make it start with one config file, and size the task to the time limit.How to review take-home assignments fairlyAgree on criteria before you open a submission, read and run the code, treat replays and signals as context, and record each verdict before the panel discusses.