Somewhere between the phone screen and the final round, many hiring processes hand candidates a project: build a small app, analyze a dataset, draft a marketing plan. The logic seems sound. Watching someone do the work beats asking them to talk about it.
But take-home assignments have a completion problem. Strong candidates, the ones with multiple offers in motion, are the most likely to walk away when an assignment feels bloated or disrespectful of their time. If your take-home is quietly filtering out your best applicants, it is working against you.
Here is how to design one that candidates finish, and that gives you signal worth reading.
Scope Creep Is the Silent Killer
Most bad take-homes did not start bad. They started as a two-hour exercise, then someone on the panel added a testing requirement, someone else asked for documentation, and a third person wanted bonus points for deployment.
Each addition felt small. Together they turned a screening exercise into a week of unpaid work. Before you send an assignment, have someone on your team complete it cold and time them. If it takes your own engineer four hours, expect a candidate juggling a job and other interviews to need six.
Keep It Under Three Hours, and Say So
Set an explicit time cap and put it in writing: "We expect this to take two to three hours. Please stop there, even if it is unfinished."
Then honor it in evaluation. If a candidate submits something rough but scoped honestly to three hours, that is a better signal than a polished submission that clearly took a weekend. Rewarding overwork just tells candidates the cap is fake, and word spreads. Candidates talk to each other on Glassdoor, Blind, and Reddit more than most hiring teams realize.
Test the Job, Not a Puzzle
The best assignments look like a small slice of the actual role. If your engineers spend their days working in a large existing codebase, a greenfield build-an-app-from-scratch exercise tells you little. Consider a code review exercise or a small change to a sample repository instead.
The same applies outside engineering. For a content role, ask for an outline and one section, not three finished articles. For an analyst, share a messy dataset and ask what they would investigate first. You are testing judgment, not stamina.
Pay for Anything Longer
If the work genuinely requires more than three hours, pay for it. A modest honorarium changes the relationship: the candidate is doing contract work, not auditioning for free. It also forces discipline on your side, because suddenly a bloated assignment has a real cost attached.
If paying candidates is not possible at your company, treat that as a constraint on assignment length, not something to apologize for in the email.
Share the Rubric Before They Start
Candidates should know what you are grading. If clean code matters more than feature completeness, say so. If you care about the written explanation more than the solution itself, say that too.
Hiding the rubric does not make the assessment more rigorous. It makes it a guessing game, and it rewards candidates who happen to guess your preferences rather than the ones best suited for the job. Publishing evaluation criteria also keeps your own reviewers honest and consistent between candidates.
Always Close the Loop
Nothing sours a candidate on your company faster than spending three hours on an assignment and receiving a form rejection, or worse, silence. If someone completes your take-home, they have earned two things: a decision within a week, and at least a paragraph of specific feedback.
This is rare enough that it becomes a differentiator. Rejected candidates who feel respected refer their friends, reapply later, and sometimes become customers. Ghosted candidates write reviews.
When to Skip the Take-Home Entirely
Take-homes are not the only way to see real work. A structured, collaborative working session of 60 to 90 minutes can surface the same signal with less burden, and it gives you something a take-home never can: a view of how the person thinks out loud and responds to feedback.
Senior candidates with public track records may not need either. If someone has shipped products, published work, or maintains an open portfolio, review that instead and use interview time to go deep on it.
A Quick Checklist
Before your next requisition goes live, run your assignment through these questions. Can a busy person finish it in under three hours? Has someone internal completed it recently and confirmed the timing? Does it resemble the actual job? Do candidates see the evaluation criteria upfront? Does every submission get a decision and feedback within a week?
If the answer to any of these is no, fix that before you lose another strong candidate to a company that respects their time. The assignment is not just a filter you apply to candidates. It is a preview of what working with you will be like, and candidates are grading it too.