Candidates code in their own IDE, in a private repo you own.
Candidates connect GitHub from their portal link; no Kit account. The reviewers named on the stage get read access when the candidate submits, and a Slack DM that it's their turn.
The candidate gets a private repo cut from your template, with a deadline on it. When they submit, reviewers get read access and review the code in GitHub.
The setup should take less time than the review.
Every assignment brings repo setup, access permissions, reminders, and a handoff to reviewers.
Repeat the assignment, without repeating the setup.
Creating repos, inviting collaborators, sending reminders, and adding reviewers means repeating the same steps for each candidate.
Candidates need the instructions in one place.
Candidates need clear instructions, a repo link, a deadline, and a way to submit. Missing details turn into emails before they can start.
Give candidates a task that resembles the job.
Your template can include the framework, tests, and build setup your team uses. Review how candidates work with code relevant to the role.
Choose how candidates will submit their work.
Compare the assessment environment, deadline controls, and reviewer access. Check each provider's current plan for details.
| Capability | Kit | CoderPad | HackerRank | Manual / ZIP |
|---|---|---|---|---|
| Coding environment | Real GitHub repos | Browser coding environment | Browser coding environment | Manual repo or ZIP |
| Candidate experience | Their own IDE + GitHub | Provider's editor | Provider's editor | Instructions by email |
| Deadline enforcement | Auto-submit + grace period | Time-boxed sessions | Time-boxed sessions | Your team tracks it |
| 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 | Your team archives it |
| Cost | Included in every seat | Separate subscription | Separate subscription | No software fee |
Code assignments come with hiring. No per-candidate fee, no per-assignment fee. 30-day free trial, card required.
Get started freeFrom template repo to reviewer access.
Follow the assignment from stage setup to submission and review.
Pick a template and set the deadline
Select a template repo from your GitHub org. Set the duration (1-30 days), estimated hours, and grace period. Add markdown instructions.
Candidate receives the invitation
The candidate gets an email with instructions and a link to connect their GitHub account. The clock doesn't start until they accept.
Private repo from your template
A private repo is created in your org from the template. The candidate is added as a collaborator with push access.
Candidate codes in their own IDE
The deadline timer runs. A 24-hour reminder goes out automatically. The candidate can request a one-time 72-hour extension if enabled.
Submit and notify reviewers
The candidate submits, or the hard deadline submits for them. The submission time is recorded and reviewers are notified.
Reviewers access the code
Your reviewers are added as read-only collaborators. They review in GitHub with the tools they know. Feedback goes back to Kit.
Connect your GitHub
Connect a GitHub account to receive repo access.
Connect GitHubThe instructions, deadline, and submit button in one place.
Candidates open the assignment from their portal link, read the instructions, and connect GitHub.
- Live updates without refreshing the page
- Connect GitHub from the portal
- Live deadline countdown with time remaining
- Self-serve 72-hour extension (if enabled)
- Clear submission confirmation with timestamp
Included in every seat. No per-candidate fee.
Set the template and deadline for each role.
Each job posting's code assignment stage has its own template, deadline, and settings. Change them anytime without affecting in-progress assignments.
- Choose a different template for frontend, backend, fullstack, or DevOps roles
- Configurable deadline from 1 to 30 days
- Grace period (0-72 hours) before the automatic submit
- Turn candidate extensions on or off
- Markdown instructions with full formatting
- Paid assignment tracking with amount and currency
Handle access, reminders, and submission automatically.
The repo and deadline run themselves. Your engineers judge the submission.
Template Library
Keep starter repos for the roles you hire for. Choose the relevant template on each job posting. There is no template limit.
Connect from the candidate portal
Candidates connect GitHub from their portal. That account gets access to the assignment repo.
Auto-Submit on Deadline
When the deadline and grace period (0–72 hours) have passed, the work is submitted automatically and the time is recorded.
Automated Reviewer Access
Reviewers get read access when the candidate submits. They review in GitHub and record feedback in Kit.
Deadline Reminders
The candidate gets an email reminder 24 hours before the deadline.
Archive on Complete
The assignment repo is archived when the stage completes.
Set up a code assignment.
If your starter repos already live in your GitHub org, step two is done.
Install the GitHub App
Install the GitHub App from Kit and authorize your organization.
Create template repos
Prepare a template in your GitHub organization with the starter code and files the candidate needs.
Configure the stage
Add a Code Assignment stage to a job posting. Choose a template, set the deadline and grace period.
Invite candidates at the right stage
When a candidate reaches the stage and connects GitHub, their repo is created and they get an invitation. The deadline starts when they accept.
The assignment stays in the hiring pipeline.
Candidates use the same portal link for their assignment, interview instructions, and scheduling. The hiring team keeps the record in one pipeline.
Before you add the stage.
How does Kit compare to CoderPad and HackerRank for take-home coding tests?
Each candidate gets a private GitHub repo from your template and works in their own IDE. Access, deadlines, submission, and archiving run inside your hiring pipeline. Your engineers review the code; nothing is graded automatically.
Do code assignments cost extra?
No. Code assignments are part of hiring, included in every seat. There is no per-candidate fee, per-assignment fee, or cap on assignments.
Does the candidate need a GitHub account?
Yes. Candidates connect a GitHub account from the portal before they get access to their repo.
Are assignment repos private?
Yes. Assignment repos are private within your GitHub organization. The candidate gets push access, and reviewers get read access after submission. Repos archive when the stage completes. Your organization's GitHub permissions also apply.
Can I use different templates for different roles?
Yes. Each job posting's Code Assignment stage selects its own template from your GitHub organization. Use a different starter repo for each role.
What happens when the deadline passes?
The soft deadline starts a grace period of 0 to 72 hours, with 24 hours as the default. At the hard deadline the work is submitted automatically, the submission time is recorded, and reviewers are notified. The repo is archived when the stage is complete.
Can candidates request extensions?
Yes, if enabled for the stage. Candidates can request one 72-hour extension from the portal, and it is approved automatically.
How do reviewers access the code?
On submission, the reviewers named on the stage are added as read-only collaborators. They review the code and leave comments in GitHub, then record their assessment in Kit.
Can I compensate candidates for their time?
Yes. Set the amount and currency on the code assignment stage. Candidates see the fee in their portal and submit payment details after completing the work. Required tax forms go to an admin for review before finance receives the payment request. Your team sends the money.
Add a Code Assignment stage to a job posting you already have open.
Get started freeReview code in a repo you own.
Connect your GitHub organization, choose a template repo, and add a Code Assignment stage. Candidates open it through their portal link.