Kendor vs traditional take-home assignments
Facts last reviewed: August 3, 2026
Kendor keeps what take-home assignments get right — realistic, job-shaped project work — and fixes what they cannot deliver: proof. Candidates work in a provisioned VS Code-based workspace in the browser, the screen starts automatically when they apply, and every submission is scored by a verified re-run on Kendor’s infrastructure. You get take-home realism with an unforgeable result and a timeline of how the work actually happened.
A classic take-home is an email, a zip file, and trust. In 2026 — when a polished solution can be generated in minutes — that trust gap is the whole problem. The fix is not surveillance; it is evidence.
| Kendor | Traditional take-home | |
|---|---|---|
| What candidates doThe format of the screen itself | Real project challenges (Node/TS, Laravel, Python, Go, SQL), scoped and timeboxed | An open project on the candidate’s machine, usually unbounded |
| EnvironmentWhere the candidate writes code | Full VS Code-based IDE in the browser: terminal, live preview, debugger — zero setup | Their own machine and IDE — setup cost is theirs |
| Hiring flowGetting applicants into a screen | Hosted careers page + Google-for-Jobs postings; applying can start the screen automatically | Manual email logistics: instructions out, zip files back |
| Trusting the resultHow the final score is produced | Verified re-run: a clean, version-pinned re-execution on Kendor infra — the score cannot be forged | Trust — nothing verifies whose code it is or that it runs |
| Integrity signalsWhat you learn about how the work happened | Timestamped facts: tab switches, pastes, typing timeline, per-save snapshots | None — you see only the final zip |
| AI policyWhether candidates may use AI | Each org decides per assessment; allowed AI use is visible in the work timeline | Unknown — you cannot tell either way |
| Live interviewsPairing with the candidate in real time | Interview mode: pair live inside the candidate’s actual workspace — code, terminal, running app | None — a separate call, if any |
| Candidate chatTalking to candidates during the process | Built-in chat with candidates on the assessment — no email ping-pong | Email threads |
| Team reviewHow the hiring team decides | Weighted rubrics with pass marks, multi-reviewer consensus, live collaborative review | Ad-hoc — whoever reads the zip decides |
| Agent tabAI assistance inside the sandbox | Coming soonOrg-provisioned AI agent inside the workspace, its use logged as evidence | Whatever the candidate uses, invisibly |
| Observer appScreening in the candidate’s own environment | Coming soonCandidates work in their own IDE on their own machine; the work is logged as reviewable evidence | It is their own environment — but nothing is observed or verifiable |
| Desktop kioskPrevention for high-stakes finals | Coming soonLocked-down desktop app: process allowlist, network sealing, multi-monitor block | None |
| PricingWhat drives the bill | Per reviewer seat, unlimited candidates — $49/reviewer/mo after beta, free tier included | Free — paid for in your team’s review time and candidate drop-off |
| Data protectionWhere candidate data lives | EU-hosted (Frankfurt), GDPR-first: signable DPA, export and erasure, no trackers | Depends entirely on how you handle emailed submissions |
What take-homes get right
Take-homes are popular for good reasons: candidates work on realistic problems, in relative calm, without an interviewer watching them type. Kendor is built on the same belief — real work over puzzle performance — and keeps that shape: project challenges with a real codebase, a terminal, and a running app.
What a take-home cannot tell you
Whose code is it? How long did it really take? Does it even run outside the candidate’s machine? A traditional take-home answers none of these. Kendor answers all three: the workspace records a timestamped activity timeline, the environment is identical for every candidate, and the grade comes from a clean, version-pinned re-execution — "works on my machine" is not a factor, and neither is a ghost-written zip.
Logistics: from manual email to automatic
Take-homes run on manual effort: emailing instructions, chasing submissions, cloning repos, installing dependencies, and writing feedback from scratch. On Kendor, applying to a role can start the screen automatically, submissions land in a review queue with the run results already graded, and your team reviews the actual workspace together — no setup on either side.
Respecting the candidate’s time
Unbounded take-homes quietly cost candidates evenings and weekends, and the best candidates decline them. Kendor challenges are scoped and timeboxed, need zero local setup, and let candidates work in a familiar IDE in the browser. Respecting candidate time is not just kindness — it protects your funnel.
When a classic take-home is still right
If you are hiring a very senior engineer for open-ended design work, an unconstrained take-home (or better, paid trial work) on their own machine may tell you more than any platform — and some candidates will rightly prefer it. Kendor’s upcoming Observer mode splits the difference: candidates work in their own IDE with their own tools while the work produces reviewable evidence.
Frequently asked questions
Are take-home assignments still worth it now that AI can solve them?
The format is worth keeping; the blind trust is not. A realistic project is still the best predictor of job performance, but an emailed zip can no longer prove who — or what — produced it. A verified re-run plus a timestamped work timeline keeps the realism while making the result and the process visible.
How do you know a take-home was not written by AI or a friend?
On Kendor you see how the work happened, not just the final file: a typing and activity timeline, paste events, and per-save snapshots, with the final grade computed by re-running the code in a clean environment. Organizations that allow AI see that use in context; organizations that do not can weigh the timeline evidence.
How long should a take-home assignment be?
Aim for 2–4 hours of focused work, scoped so a strong candidate can finish. Kendor challenges are timeboxed by design, and because the environment is pre-provisioned, none of that budget is spent on setup.
Do candidates need to install anything to do a Kendor screen?
No. The workspace — a VS Code-based IDE with a terminal, dependencies, a live preview, and a database when needed — runs entirely in the browser. Candidates open a link and start.
More comparisons
Kendor vs HackerRank · Kendor vs CodeSignal · Kendor vs CoderPad · Kendor vs Coderbyte
See it on the Kendor homepage, browse live roles hiring through Kendor, or read the engineering-hiring blog.