A take-home assignment is fair when it runs under about three hours and mirrors work you’d actually do in the role. It stops being fair the moment it produces something the company could ship on Monday.
You already know the version that isn’t fair. It lands in your inbox on a Thursday: build a 12-slide go-to-market deck, due Monday. Nobody has mentioned how long it should take, and nobody has mentioned paying you. Here’s the part most job seekers don’t believe until they try it: you can push back, and a good company won’t punish you for it.
Most candidates stay quiet because they think the assignment is the test. It isn’t – or at least, it isn’t only that. How a company scopes the assignment tells you exactly how it will scope your job.
What a fair take-home assignment actually looks like
Work samples aren’t the enemy. Harvard Business Review has argued that companies should prioritize assignments over interviews, because interviews predict performance poorly and leave a lot of room for bias. That’s right. A well-built assignment is the fairest stage in the whole process, because it’s the one place where what you can do outranks how comfortable you sound in a room.
So the problem isn’t assignments. The problem is scope.
A fair take-home assignment:
- Takes three hours or less, and the company tells you that up front
- Uses a fake or anonymized dataset, not their real Q3 numbers
- Has a defined deliverable (“a one-page memo”) instead of an open one (“a strategy”)
- Gets reviewed by a named human who gives you feedback afterward
Notice what those share. Each one costs the company something – time to write the prompt, time to read your answer, time to respond. Companies that respect your hours tend to spend their own.
Four signs the assignment is really unpaid work
It’s scoped to their live problem, not a hypothetical. You’re building a launch plan for a real product, with their real constraints, on their real timeline. That’s not an evaluation. That’s a deliverable.
There’s no time cap. “Take as long as you need” means as long as the other four finalists take, and one of them has the whole weekend.
It arrives before a human conversation. If round one is a six-hour project and you haven’t spoken to the hiring manager, they’re using free labor as a screening tool because reading resumes costs them money.
Nobody can name the reviewer. Ask who reads it and what they’re looking for. When nobody knows, nobody reads it.
One of these is a yellow flag. Two is a pattern. At three, you’re not a finalist – you’re a vendor working a spec project you never bid on. Sometimes the process never ends in a hire at all, because the role was never real to begin with.
The script that pushes back without withdrawing
Pushing back isn’t a confrontation. Instead, it’s a scoping conversation – the same one you’d have in week one of the actual job. Send this to the recruiter:
“Happy to do this – it looks like a good way to show how I’d approach the role. Two quick questions so I can size it right: how many hours do you expect it to take, and who reviews it? If it runs much past three hours, I’d rather build a focused version and walk you through my thinking live.”
Three things happen inside that message. First, you say yes, so you haven’t refused anything. Second, you ask for a time box, which forces the company to name a number it can be held to. Third, you offer an alternative that’s genuinely better for them, because a live walkthrough is faster to evaluate and much harder to fake.
That last part matters. You’re not asking for a favor. You’re proposing a cheaper test.
What actually happens when you push back
Usually the response falls into one of three buckets.
Sometimes they give you a number and it’s reasonable. Do the assignment, stay inside the box, and stop at the stated time even if it isn’t perfect.
Occasionally they shrink it. A company that wants you will find a smaller version of the test, because the goal was always to see how you think.
Or they go quiet and get defensive. That’s your answer too, and it cost you one email instead of one weekend.
I’ve placed 250+ mid-career tech professionals. In all of it, “how long should this take?” has never been the question that sank a candidacy. The lost weekend, though – I hear about that constantly.
When to actually walk away
Withdraw when any of these are true:
- The assignment runs past a full workday and they won’t scope it down
- They want work product on a current business problem and won’t pay for it
- You still haven’t had a real conversation with the hiring manager
- The process has already moved the goalposts twice
Because how a company runs its interview process is the cheapest culture data you’ll ever get. Hiring hasn’t gotten sharper over the last few years, either. It’s gotten slower: 93% of managers told Robert Half that hiring takes longer than it did two years ago. An employer that burns eight unpaid hours of a finalist’s time before a single hiring-manager conversation is showing you precisely how it will treat your calendar once you’re on payroll. Believe it the first time.
Walking away isn’t only defensive, either. It’s negotiating power. Clients who negotiate see roughly +$26K in total comp, and that negotiation starts with the credible belief that you’d be fine without this particular job. You can’t fake that belief in the offer call if you spent the interview process proving you’d do anything.
Common questions about take-home assignments
Should I do a take-home assignment at all?
Yes, when it’s scoped and time-boxed. A work sample tests your output instead of your interview polish, which makes it the fairest stage in the process. Refusing every one of them will cost you good roles.
How long should a take-home assignment take?
Three hours or less is the working rule. Anything past a full workday is a project, not a test.
Should I be paid for a take-home assignment?
If the work solves a live business problem the company would otherwise pay someone to solve, yes. Ask directly. Plenty of companies have a standard rate and simply don’t advertise it.
Can I ask to do the assignment live instead?
Yes. Offer a shorter version plus a 30-minute walkthrough. That’s less work for you and stronger signal for them, so a recruiter who has already scoped the assignment has a real reason to say yes.
Will pushing back get me rejected?
Rarely, and when it does, it told you something true about the employer. A company that eliminates you for asking about scope was going to manage you the same way.
What to do next
If you want to see where your search is weakest before the next assignment shows up, take the RHINO quiz. Five minutes, no email required.
If you’d rather catch a bad process before you’re four rounds deep in it, read The Questions to Ask a Recruiter Before Your Interview next. Most of what you need to know is available on the first call, if you ask.
If you’re staring at an assignment right now and want a second opinion on whether it’s worth your weekend, book a free strategy call.