Key takeaways
Do the assignment when a person has already spent real time on you, the hours are stated and modest, and the deliverable is an invented exercise with no use to the company. Renegotiate or decline when it arrives before any conversation, carries no time budget, or reads like a ticket off the team's backlog. Ashby's Recruiting Operations Benchmarks, published 7 May 2026, found around 13% of hires included a take-home component, and usage climbs as applications per hire climb. That correlation is the useful part, because it suggests the round is often sorting volume rather than measuring craft. Asking to change the scope costs an email.
Should you do an unpaid take-home assignment?
Usually yes, once three questions have honest answers. The resentment around this round is real and widely shared. Resume Genius, a resume-builder company, surveyed 1,000 active U.S. job seekers through Pollfish for its 2026 Job Seeker Insights Report, and 25% of them named being asked to complete unpaid assignments or tests as a top hiring frustration, sixth in a ranked list of nine. Getting no reply at all led that list, named by 55%.
Those two figures belong together. A candidate who has been ignored by twenty employers reads a request for six unpaid hours differently from one who has just had a good conversation with a hiring manager, and the difference is information rather than mood. The three questions below recover that context. Where in the process does the request arrive, how many hours does it actually cost, and is the output something the employer could use.
Four-Leaf's guide to handling a take-home assignment covers doing one well once you have accepted. The question here is whether to accept.
How common are take-home assignments, really?
Less common than their reputation suggests, and concentrated where applicant volume is highest. Ashby's Recruiting Operations Benchmarks, drawn from hiring on Ashby's own applicant-tracking platform and published 7 May 2026, reports that "take-homes are not universally used across hiring processes", with around 13% of hires including a take-home component. The same report finds that "roles with higher applications per hire are more likely to include a take-home stage", and that in business roles usage climbs steadily from roughly 8% at lower volumes to over 20% at the highest application ranges. Technical roles stay comparatively flat as volume rises.
Read that correlation as a description of what the round is doing. When a posting draws hundreds of applicants, an asynchronous exercise is a cheap way to thin the field, and the hours land on candidates rather than on the hiring team. Ashby states the same correlation and hedges it, writing that "this suggests that some teams (particularly in business hiring) lean on asynchronous evaluation as application volume increases and interview capacity becomes constrained".
One caveat on the Ashby figures. They describe employers using a single applicant-tracking system, weighted toward startup and growth-stage companies, so they indicate a direction and not a market census.
What does the stage of the request tell you?
The stage is the clearest signal available, because it shows how much the employer has already put in. An assignment that arrives with the automated application confirmation, before any person has spoken to you, is screening. One that arrives after a recruiter screen and a hiring manager conversation is evaluation.
Early-career pipelines are the exception worth naming, because volume is highest there and the take-home is usually standard for the whole pipeline rather than a judgment about one applicant. Netflix's new-grad careers page states that New Grad interviews at Netflix "typically include a take-home assessment followed by two rounds of interviews, with advancement based on the feedback at each stage". A published process is easier to plan around than one improvised per candidate.
Ask where the assignment sits in the full sequence before starting, and get that stage list in writing.
How many unpaid hours is too many?
The employer's own stated budget is the ceiling, and a prompt with no budget in it is the first thing to fix. A brief that names four hours is a commitment you can hold them to. Asking for that number when it is missing is a professional question, and the answer tells you whether the team has thought about the cost it is handing over.
Judge the hours in the context of the whole loop. One four-hour exercise inside a process with three interviews is a modest share of the total cost of applying. The same exercise as a fourth unpaid stage, bolted onto a loop that keeps growing, is a different proposition, and Four-Leaf's post on how many interview rounds is too many covers how to read that pattern and when withdrawing is correct.
One workable threshold is the loop itself. When the assignment would take longer than every interview in the process combined, the ratio has tipped, and saying so out loud is reasonable.
Is the assignment something the employer could ship?
This question separates an exercise from free labor, and it has a concrete test. Ask whether the deliverable could be used as it stands. An exercise runs on a synthetic dataset, a fictional company, or a problem with a known answer. Work means their real onboarding funnel, a campaign brief with their actual budget, a bug from the current sprint, or a design for a feature already on the roadmap.
Specificity about their business is the tell. An assignment that requires the employer's internal data, or that produces something they would otherwise pay a contractor for, deserves a direct question about compensation before you start. Ask it once and the answer is itself information. A company that asks for usable output and declines to pay for it has told you how it values your time.
Scope creep is the related pattern to watch. An exercise introduced as two hours that expands through follow-up emails is worth stopping and re-scoping in writing, politely and immediately.
How do you negotiate the scope of a take-home?
Four moves, from the cheapest to the largest ask.
Ask for a time budget when the prompt has none. "Roughly how many hours do you expect this to take?" is the entire message.
Propose a subset. Naming the part you will build and the parts you will describe instead is itself a scoping decision, which is the judgment the round claims to measure. "I will implement the ingestion path end to end and write up how I would approach the dashboard" beats a rushed version of everything.
Offer a live session instead. A paired exercise of ninety minutes costs the employer more and you less, and it settles the question of who actually wrote the submission.
Ask whether the assignment is paid, when the output is genuinely usable. Ask once, plainly, without apologizing for it.
Send any of these to the recruiter before starting, in a few lines, because a request made in advance reads as planning and the same request after a missed deadline reads as an excuse.
What is overrated
Refusing every unpaid assignment on principle. The rule feels clean and costs candidates real offers, especially in fields where a portfolio travels badly. A proportionate exercise late in a good process is one of the fairer stages in hiring, because it rewards work done over performance in a room.
Treating a paid assignment as automatically acceptable is the mirror mistake. Payment does not make eight hours available to someone holding down a full-time job, and a paid brief with vague requirements carries the same scope risk as an unpaid one.
Reading a take-home as a personal insult is the third. The volume pattern in Ashby's benchmarks suggests most of these are pipeline decisions made once, for every applicant, by someone who has never opened your file.
A playbook for an unpaid assignment request
- Confirm where the assignment sits in the sequence. Ask which stages remain after it, and who reads the submission.
- Get a stated time budget before you start. Where the prompt names one, hold to it and say so in your write-up.
- Run the shippability test. If the output could be used as it stands, ask about compensation before beginning.
- Propose a smaller version or a live session when the ask is out of proportion to the stage you have reached.
- Verify the company and the sender before running anything on your own machine. Four-Leaf covers the fake interviews that install malware, where the assignment stage is exactly where the attack lands.
- Ask whether a review conversation follows the submission, and rehearse narrating your choices if it does. Four-Leaf compares the tools for that in its roundup of mock interview platforms.
Where this is heading
The safest assumption now is that you will have to talk through a submission, because an unsupervised exercise cannot show who did the work. That helps candidates in one specific way. A shorter submission you can defend in detail beats a polished one you cannot, which lowers the number of hours the round rationally demands. Ask what happens after you hand the work in, and treat that conversation as the stage that decides the outcome.
The decision itself stays small. Three questions, asked before a weekend disappears. How much has this employer invested in me so far, how many hours are they actually asking for, and could they ship what I hand them. Asking those out loud costs one email, and it changes what the next two weeks look like.