A friend of mine was asked to produce a full market analysis, a marketing strategy, a go-to-market plan, a measurement framework and a creative brief as a take-home assignment. Mid-level role, unpaid, due in 72 hours.
The quick answer: a take-home assignment is a fair test when it’s scoped to one skill and honestly capped at about two hours. It’s free work when it asks for a finished deliverable the company could have paid a consultant to produce.
The posting said it should take “no more than three hours.” Nobody builds that in three hours, and the company knows it. So the number isn’t a time limit, it’s cover. Here’s the thing most candidates get wrong, though: the answer isn’t to refuse every assignment. Some of them are the fairest step in the whole process. You just need a way to tell which one you’re holding.
The deliverable test
Run one question at the assignment before you run anything else. Could they hand this to a consultant, pay the rate, and use what comes back? If yes, it’s a deliverable. If no, it’s an assessment.
An assessment takes a slice. It uses sample data, a fictional company, or a problem the team already solved last year. Therefore it tells them how you think without producing anything they can ship. A deliverable, by contrast, uses their real product, their real market, and their real open problem, and it arrives finished.
The federal government actually runs a version of this question. When the Department of Labor decides whether unpaid work is legitimate, it applies a primary beneficiary test – who gets the main benefit from the arrangement. That rule governs internships, not job candidates, so it won’t help you legally. As a question to ask yourself, though, it’s the sharpest one available. If you’re the primary beneficiary, the assignment is teaching you something about the role. If it’s them, you’re working for free.
Even the people who argue hardest for assignments agree on the size. Harvard Business Review’s case for prioritizing assignments over interviews recommends a small test of the primary skill the job requires, paired with a conversation afterward. Small test. One skill. A conversation. That’s the whole design, and a 72-hour strategy deck breaks all three parts of it.
Four questions to ask before you start
Ask these before you open a blank document. Send them in one email, and keep the tone flat and professional.
- What specifically are you evaluating? A well-built assignment has an answer ready. If nobody can name the skill it measures, the assignment wasn’t designed, it was copied.
- Where does this sit in the process, and how many candidates are at this stage? Doing the work when you’re one of two finalists is a reasonable trade. Doing it as candidate nineteen isn’t.
- Who reviews it, and what happens to the work afterward? Ask for a line in writing saying the material won’t be used internally. Reasonable teams write it without blinking.
- Is there a live version instead? Plenty of hiring managers will swap a take-home for a 45-minute working session once you ask. They wanted your thinking, not your weekend.
None of these read as difficult. They read as someone who scopes work before doing it, which is the exact behavior the job requires anyway. For more on what to surface early, see the questions to ask a recruiter before your interview.
How to scope down a take-home assignment without saying no
Most candidates treat the assignment as fixed. It almost never is. So counter with a scope, not a complaint:
“Happy to take this on. To keep it inside the three hours you mentioned, I’ll do the market analysis and the top-line strategy, and leave the go-to-market plan and creative brief out. If you’d rather see one of those instead, tell me which and I’ll swap it in. I’d also like 20 minutes afterward to walk you through my thinking.”
Three things happen when you send that. First, you’ve shown you can prioritize under a constraint, which is most of the job. Second, you’ve capped your own exposure. Third, you’ve asked for the debrief – and the debrief is where you actually win, because that’s where you explain the tradeoffs the document can’t show.
Scope your slice toward whatever the posting emphasized rather than whatever you enjoy most. Learning to read what a job description actually asks for matters more here than raw effort, since hiring managers decide on obvious fit, not on volume delivered.
When to decline, and exactly how
Decline when at least two of these are true: the honest time cost runs past three hours, they want work on their real live problem, they won’t offer a debrief, and the candidate field is still wide.
Then say it cleanly:
“Thanks for sending this over. I’m going to pass on the assignment as scoped, since it’s a multi-day deliverable rather than a skills check. I’d be glad to do a 45-minute working session with your team on the same problem, or a two-hour version with a narrower scope. If neither works on your end, I understand completely, and I appreciate the time so far.”
No apology, no lecture about unpaid labor, no argument. You’re not trying to reform their process. You’re deciding how to spend a weekend.
I’ve had clients push back on scope and stay in the process. I’ve also watched clients burn a full weekend on a finished deliverable and still get the “we went with someone more closely aligned” email. The work isn’t what protects you. The judgment about which work to do is.
And if the answer is no, no is a complete sentence.
You’re auditing them too
Here’s the part candidates forget while they’re panicking about the deadline. How a company scopes one of these is a live sample of how it scopes work internally.
A team that hands twenty candidates a 72-hour unpaid strategy project is telling you something specific about how it plans, how it values other people’s time, and what a Thursday night looks like once you’re on the payroll. Because they’re on their best behavior right now. This is the version of them that’s trying to impress you.
Take the data. Although it’s uncomfortable, it’s the cheapest information you’ll ever get about a future employer.
Frequently asked questions
Is it normal for a take-home assignment to be unpaid?
Yes, unpaid is standard practice for short skills checks, and that’s not unreasonable on its own. What isn’t standard is a multi-day deliverable built on the company’s real problems. Some companies do pay for larger exercises, and it’s fair to ask whether yours does.
How long should a take-home assignment take?
Two hours is a reasonable ceiling for most roles. Treat any stated estimate as optimistic and assume the real cost runs roughly double, then decide against that number rather than the one in the email.
Can I ask for a paid version instead?
You can. In my client work, that ask carries the most weight at senior levels, or when the scope is genuinely large. Frame it around scope rather than principle: the exercise as written is consulting work, so you’re happy to do it at a day rate or do a smaller unpaid version.
Will pushing back cost me the job?
It can, at a company that wanted compliance more than judgment. However, that’s useful information arriving early rather than after you’ve signed. Teams that value scoping treat a clear, professional counter as evidence, not friction.
What to do next
If you want to know what a stalled search is actually costing you while you’re weighing all this, run the job search cost assessment. It takes about 90 seconds and gives you a monthly dollar figure plus the stage of your search that’s leaking the most.
If reading a company accurately is the part you want to get better at, read Interview Red Flags: 5 Signs to Catch Before You Accept next.
If you’d rather have someone look at your actual process and tell you which assignments to take and which to decline, book a free strategy call.