Take-Home Assignment

A take-home assignment is a work-sample test you complete on your own time: a small project, analysis, or design brief that shows how you actually work. Fair ones are scoped to a few hours; unfair ones are free labor wearing an interview badge.

What Is a Take-Home Assignment?

Key Takeaways

  • A take-home assignment is a scoped work sample done on your own time: a coding task, an analysis, a design brief, a writing piece.
  • Fair scope is commonly 2 to 4 hours; anything past a day of work deserves scrutiny, payment, or a polite no.
  • Submissions are judged on the working result, your communication, and the decisions you documented, not on gold-plating.
  • Some 'assessments' are disguised free labor, and there are reliable tells for spotting them before you donate a weekend.

A take-home assignment is a project-based assessment you complete outside the interview room: build a small feature, analyze a dataset, draft a campaign, critique a design. Employers use it because it looks more like the actual job than any live round does; you get your own tools, your own schedule, and no one watching you type. For candidates who freeze in a live technical interview, that's genuinely good news. The catch is scope. A fair take-home is a bounded sample, commonly 2 to 4 hours of effort. An unfair one is a real deliverable with your evenings as the budget, and part of handling take-homes well is telling the two apart before you start.

2-4 hrWidely accepted fair scope for an unpaid take-home
3-7 daysTypical window employers give for submission
1Short README that lifts almost every submission
0Company-specific deliverables you should hand over unpaid

What Fair Scope Looks Like (and Scope Creep)

Fair assignments share a shape: an explicit time expectation stated up front, a generic or synthetic problem, clear evaluation criteria, and a deliverable small enough to discuss in a follow-up conversation. The 2 to 4 hour range is the widely accepted norm for unpaid work; some companies go longer and compensate candidates for it, which is a strong signal they respect your time. Scope creep announces itself differently. No stated time limit paired with 'spend as long as you need.' Requirements that keep growing after you ask questions. A rubric that rewards production polish: tests, deployment, documentation, edge cases, for what was pitched as a sketch. When the assignment quietly wants a finished product, the scope is telling you what the interview process won't.

When an Assessment Is Really Unpaid Work

Most employers run take-homes honestly. The exceptions have tells:

  • The problem is their actual product, not a generic exercise: their real backlog item, their live campaign, their current client's problem.
  • You're given real company or customer data instead of a synthetic set, which no assessment needs and no careful company hands out.
  • The deliverable would be usable as-is: a shippable feature, a publishable article, a client-ready strategy deck with their branding on it.
  • There's no stated rubric and no promised feedback, because the point was the output, not the evaluation.
  • The ask arrives before any human conversation, at a scale of days rather than hours, sometimes to a large pool of candidates at once.

How Take-Home Submissions Are Judged

Reviewers typically score three layers, and candidates consistently over-invest in the first.

The working result

Does it run, hold up, answer the brief? Reviewers check the happy path and a couple of edge cases. A modest solution that works beats an ambitious one that almost does, every single time.

Communication

A short README or summary note: what you built, how to run it, what you'd do with more time. Reviewers read this first, and many form their opinion there. It's the highest-return hour in the whole assignment.

Documented decisions

Why this approach, what you traded away, what you deliberately skipped. Naming your own cut corners reads as senior; hoping nobody notices them reads as the opposite. SHRM's 2025 research found 51% of organizations use AI in recruiting, yet take-home review remains a mostly human round, and humans reward candidates who make the review easy.

Negotiating Scope, or Declining Gracefully

Scope is more negotiable than most candidates assume, because reasonable employers would rather adjust than lose good people silently. If the ask is oversized, name it plainly: you're enthusiastic, you have limited hours alongside your current job, and you'd like to either time-box your submission to four hours, swap in a portfolio piece from your career portfolio, or do a paid version at a day rate. Every response tells you something. A company that accepts a time-box respects boundaries; one that bristles at the question just showed you the job. And declining is a legitimate move, not a failure: a polite 'the scope doesn't work for my situation, but I'd welcome a live session instead' keeps the door open while keeping your weekend.

Frequently  Asked  Questions

How long should a take-home assignment take?

The widely accepted norm for unpaid take-homes is 2 to 4 hours of focused work, with a submission window of several days so you can fit it around life. Anything specced at a full day or more should either come with payment or come with your polite pushback. Companies serious about candidate experience state the expected hours up front.

Should I spend extra time to beat other candidates?

Mostly no. Reviewers score against the brief, and a gold-plated submission signals you can't scope work, which is its own red flag for the job. Spend any surplus on the README and your decision notes rather than extra features; that's where reviewers actually form their impressions.

Can I ask questions during a take-home?

Yes, and you usually should. A clarifying email about requirements, expected polish, or evaluation criteria mirrors how real work starts, and thoughtful questions are often quietly scored. If the answers keep expanding the scope instead of bounding it, treat that as data about the company, not just the assignment.

How do I know if a take-home is disguised free work?

Check three things: is the problem generic or their actual live work, would the deliverable be usable as-is, and is there a stated rubric with promised feedback? A synthetic problem with clear criteria is an assessment. Their real backlog item, client-ready, with no feedback loop, is labor. Decline or ask to be paid.

Will declining a take-home cost me the job?

Sometimes, and that can be acceptable. If you decline a fair 3-hour exercise, expect to exit the process. If you push back on a 20-hour unpaid project and the employer walks, they filtered themselves out. Offering an alternative, a time-boxed version, a portfolio piece, a live session, keeps most reasonable processes alive.

What happens after I submit?

Good processes review within about a week and bring you into a follow-up conversation to walk through your decisions, often the most enjoyable round in the loop because you're discussing your own work. If you hear nothing at all, follow up once; persistent silence after submitted work, like any hiring ghosting, tells you what working there might feel like.

From the team that builds interview software

Hyring builds the AI interview software (video, phone, and coding rounds) that runs skills assessments for 5,000+ HR teams, so this definition of what a fair one looks like comes from inside the interview machine.

See how the AI Video Interviewer works

Sources

Adithyan RKWritten by Adithyan RK
Surya N
Fact-checked by Surya N
Published on: 11 Apr 2026Last updated: 14 Jul 2026
Share: