What is a take-home assignment in hiring?

Most teams place a take-home after an initial recruiter screen or first interview, once a candidate has shown baseline interest and fit, but before investing in a full interview loop. It acts as a practical filter: candidates who can talk about a skill in an interview don't always deliver when asked to produce work. Positioning it mid-process keeps the top of the funnel low-friction while giving you a concrete artifact to discuss in later rounds, which makes the final decision far less speculative.

A strong assignment mirrors real work the person would actually do, not a contrived puzzle or a trick question. Scope it tightly, give clear instructions and success criteria, and remove any ambiguity about what 'done' looks like. Avoid asking candidates to build something you could ship for free — that erodes trust. The best assignments are self-contained, respect the candidate's time, and produce output you can compare across applicants using the same rubric.

Keep it short — ideally under two to three hours of real effort. Long assignments disadvantage candidates who are employed, have caregiving responsibilities, or can't spare a weekend, which quietly narrows and biases your pool. State an explicit time cap in the brief and evaluate against that cap, so someone who stopped at the limit isn't penalized against a candidate who spent ten hours polishing. If you genuinely need more depth, pay for the time.

Paying for longer or more involved assignments is increasingly expected and signals that you value people's time. For short exercises under a couple of hours, most candidates accept an unpaid task as a normal step. For anything resembling a full project or a multi-day build, compensation is fair and improves completion rates and goodwill. Whatever you choose, be transparent about it up front so candidates can make an informed decision before starting.

Define the rubric before you see any submissions and score every candidate against the same criteria. Have at least two reviewers grade independently, then compare, to catch individual bias. Where possible, anonymize submissions by stripping names so the work is judged on its merits. Record scores in your applicant tracking system so the reasoning is visible to the whole hiring team and consistent from one candidate to the next.

The biggest risk is drop-off — strong candidates with multiple offers may decline a lengthy unpaid task, so you can lose good people to a slow, heavy process. There's also the fairness concern around time availability, and the effort of designing and grading assignments well. If the task is poorly scoped or feels like free labor, it damages your employer brand. Used sparingly and thoughtfully, though, the signal often outweighs these costs.

Choose a take-home when the work is reflective and benefits from focus — writing, analysis, design, or building something small — and when you want to see how someone works without interview pressure. Choose a live exercise, such as pair programming or a whiteboard walkthrough, when collaboration, communication, and real-time problem-solving are the actual job skills you're testing. Many teams combine both: a short take-home to filter, then a live discussion of that work to probe how the candidate thinks.