Candidates code in their own IDE, in a private repo you own.
Code assignments are one stage type in a Kit hiring pipeline. Kit clones your template repo, the candidate authorizes GitHub, work auto-submits at the deadline, and your reviewers get access. Candidates reach all of it from a magic link, with no Kit account and no seat.
Kit clones your template into a private repo, invites the candidate through a magic link, and auto-submits when the deadline hits.
Take-home assignments shouldn't require a project manager.
You're hiring engineers, not managing a logistics operation.
Create repo. Set permissions. Email the link. Chase the deadline. Repeat.
Every candidate means a new repo, new collaborator invite, a deadline email, a reminder email, and manual reviewer setup. Multiply by 20 candidates. That's your week.
Your best candidates drop off before writing a line of code.
Which repo? Which branch? What format? Where do I submit? Every unanswered question is another email to your recruiter, or a candidate who quietly stops.
Sandbox puzzles test memorization, not engineering.
Algorithm tests in proprietary IDEs tell you who practiced LeetCode. Real repos with real build systems tell you who can ship code.
CoderPad, HackerRank, a ZIP file, or a real repo.
Every engineering team runs one of these four. Only one is a stage in the pipeline you already run.
| Capability | Kit | CoderPad | HackerRank | Manual / ZIP |
|---|---|---|---|---|
| Coding environment | Real GitHub repos | Proprietary sandbox | Proprietary sandbox | Manual repo or ZIP |
| Candidate experience | Their own IDE + GitHub | Unfamiliar web editor | Unfamiliar web editor | Confusing email chains |
| Deadline enforcement | Auto-submit + grace period | Time-boxed sessions | Time-boxed sessions | Honor system |
| ATS integration | A stage in the pipeline | Third-party plugin | Third-party plugin | Copy-paste |
| Reviewer access | Auto-added on submission | Manual sharing | Manual sharing | Forward the ZIP |
| Repo cleanup | Auto-archived on completion | N/A | N/A | You'll forget |
| Cost | Included in Kit | $449/mo | $300-500/mo | Free (+ hours of your time) |
Code assignments come with hiring. No per-candidate fee, no per-assignment fee.
Start free trialFrom template repo to reviewer access.
Every code assignment follows the same 6-stage lifecycle. Kit handles every transition.
Pick a template and set the deadline
Select a template repo from your GitHub org. Set the duration (1-30 days), estimated hours, and toggle auto-submit. Add markdown instructions.
Candidate receives the invitation
Kit emails the candidate with instructions and a link to connect their GitHub account. The clock doesn't start until they accept.
Private repo from your template
Kit creates a private repo in your org, cloned from the template. The candidate is added as a collaborator with push access.
Candidate codes in their own IDE
The deadline timer runs. Kit sends a 24-hour reminder automatically. Candidate can request a one-time 72-hour extension if enabled.
Assignment submitted — repo locked
Candidate submits manually or the hard deadline triggers auto-submit. The repo is locked. Reviewers are notified.
Reviewers access the code
Kit adds your reviewers as read-only collaborators. They review in GitHub with the tools they know. Feedback goes back to Kit.
Connect your GitHub
One-click GitHub OAuth. No coordination with your team.
Connect GitHubOne link. Deadline, instructions, submit button.
The magic link opens the assignment. No Kit account, no seat, no password to set.
- Real-time updates via Turbo — no page refreshes
- GitHub OAuth in one click from the portal
- Live deadline countdown with time remaining
- Self-serve 72-hour extension (if enabled)
- Clear submission confirmation with timestamp
Part of the hiring module. No per-candidate fee.
Configure once. Run for every candidate.
Each job posting's code assignment stage has its own template, deadline, and settings. Change them anytime without affecting in-progress assignments.
- Different templates for each role — frontend, backend, fullstack, DevOps
- Configurable deadline from 1 to 30 days
- Grace period (0-72 hours) before auto-submit
- Toggle candidate extensions on or off
- Markdown instructions with full formatting
- Paid assignment tracking with amount and currency
Repo created, clock running, reviewers added, repo archived.
Six things Kit does between the stage opening and your reviewers reading the diff. Scoring is not one of them — your engineers still judge the code.
Template Library
Create template repos for frontend, backend, fullstack, DevOps — whatever you hire for. Each job posting picks its template. Unlimited templates, no extra cost.
Candidate GitHub OAuth
The candidate authorizes GitHub from the portal and Kit provisions repo access. Nobody emails a username to your recruiter.
Auto-Submit on Deadline
Soft deadline passes. Grace period starts. Hard deadline hits. The repo locks and the assignment is marked submitted. No more ghosted take-home tests.
Automated Reviewer Access
The moment a candidate submits, Kit adds your reviewers as read-only collaborators. They see the code in GitHub. Feedback goes back to Kit.
Deadline Reminders
Kit emails the candidate 24 hours before the deadline. Nobody on your team has to send the 'just checking in' note.
Archive on Complete
Kit archives the repo when the stage completes. Your org stops collecting dead hiring repos.
Four steps between your GitHub org and a candidate's repo.
If your starter repos already live in your GitHub org, step two is done.
Install the GitHub App
One-click install from Kit. Authorize your GitHub org. No API keys, no webhook configuration.
Create template repos
Set up starter repos in your GitHub org for each role type — frontend challenge, backend API task, system design scaffold.
Configure the stage
In any job posting, add a Code Assignment stage. Pick your template, set the deadline, toggle auto-submit.
Candidates auto-assigned
When a candidate reaches that stage, Kit creates their private repo, sends the invitation, and runs the clock through submission and reviewer access.
Code assignments are just one stage.
The same magic link that opens the repo also carries the candidate's interviews, reviews, and scheduling. One record, one pipeline, no second login.
Before you add the stage.
How does Kit compare to CoderPad and HackerRank for take-home coding tests?
CoderPad and HackerRank run the candidate inside a proprietary sandbox. Kit creates a private repo from your template, so the candidate works in their own IDE and you read the commit history afterwards. Kit also runs the deadline, auto-submits, adds your reviewers, and archives the repo. What Kit does not do is score the submission — your engineers read the diff.
Is Kit free for code assessments?
Code assignments are part of the hiring module. No per-candidate fee, no per-assignment fee, no cap on how many you run. Kit's VDP, Outreach, and Compensation modules bill separately — code assignments are not one of them.
Does the candidate need a GitHub account?
Yes. The candidate authorizes GitHub over OAuth from the portal and Kit provisions repo access from there. A candidate who will not connect a GitHub account cannot take this stage.
Are assignment repos private?
Yes. Every assignment repo is created as a private repository in your GitHub organization. Only the candidate (push access) and your reviewers (read-only, added after submission) can see the code. Repos are automatically archived when the stage completes.
Can I use different templates for different roles?
Yes. Each job posting's code assignment stage selects its own template repo. You can have a React frontend challenge, a Rails API task, a DevOps scaffold, and a system design starter — each one a template in your GitHub org.
What happens when the deadline passes?
Kit uses a two-phase deadline. The soft deadline passes and the candidate enters a configurable grace period (0-72 hours, default 24). When the hard deadline hits, Kit auto-submits the assignment, locks the repo, and notifies your reviewers the moment it locks.
Can candidates request extensions?
Yes, if you enable it. Candidates can request a one-time 72-hour extension directly from the portal — no emails, no awkward asks. Extensions are self-serve and auto-approved. You can disable this per stage if you prefer strict deadlines.
How do reviewers access the code?
Automatically. When a candidate submits, Kit adds your configured reviewers as read-only collaborators on the repo. They review code in GitHub using the tools they already know — PRs, inline comments, code navigation. Feedback is recorded in Kit.
Can I compensate candidates for their time?
Yes. Kit tracks payment amount and currency per code assignment stage. You configure compensation when setting up the stage, and the details are visible to the candidate in their portal.
Add a Code Assignment stage to a job posting you already have open.
Start free trialReal repos. Real skills.
Connect your GitHub org, pick a template repo, add the stage to a job posting. The candidate opens it from a magic link — no Kit account, no seat.