Take-Home Interview Tasks: Fair Test or Free Labour?
Workizon Editorial
20th November 2026
4 min read
0
6
Last month a friend of mine spent a Saturday building a dashboard for a company she had never met. Two interview rounds, a friendly call with the team, then a task brief with a 48-hour deadline. On Tuesday she got a polite rejection. Nobody said a word about the work itself.
That story is not unusual in 2026. Take-home assignments have crept back into hiring. Part of it is AI: a generated CV and a polished interview answer are cheap now, so teams want to see how someone thinks when nobody is watching. Part of it is simply that remote hiring makes a written brief feel safer than a gut feeling.
So the homework is probably here to stay. The question is how to tell a fair test from a free project before your weekend disappears.
Why the homework came back
Recruiters keep telling me the same thing. A CV lists what you have done. A take-home shows how you work: how you cut scope, what you ignore, whether your document survives a second read. For a design, data or writing role that signal is genuinely hard to get any other way.
I get that. I have also seen briefs that were clearly lifted from a backlog. The line between the two is not always obvious from the job ad, but it becomes pretty clear once you read the task carefully.
The two-hour question
Before you agree to anything, ask one thing: how long would this take a current employee? If the honest answer is around two hours, it is a test. If it is a day or two, it is a project, and projects usually come with a budget.
A reasonable brief can be finished in one sitting. It uses a sanitized or public dataset, states the deliverable format, and comes with a rubric, even a short one. If none of those exist, ask for them. How a company reacts to that question tells you more than the task ever will.
Negotiating the scope before you start
- Ask what "good" looks like. If nobody can describe it, the evaluation will be a coin toss.
- Offer a time-box: "I can give you four focused hours this week, so a narrower version of the brief would work better for me."
- Ask once, politely, whether longer tasks are paid. Some companies do pay, others offer a voucher. A flat no is information, not an insult.
- Propose an alternative: a live 60-minute case session, a walkthrough of past work you are allowed to share, or a short paid trial.
- Get the deadline in writing, including the time zone.
What a good brief actually contains
Context, audience, constraints, output format, a time estimate, and the name of the person who will read it. No real client data, no confidential material, no live credentials. If the task needs access to a production system just to start, that is not an assignment, that is an onboarding exercise, and it should be paid.
Red flags worth walking away from
Vague deadlines like "as soon as possible". A task that mirrors an actual open business problem, with no mention of payment. Requests for logins or customer data. An NDA before you have spoken to a hiring manager. Silence from every human on the team. And the competition format: "we will review the best submissions and maybe hire someone" is spec work, not hiring.
After you hit send
Agree a date for the answer and put it in your calendar. If it passes, send one short follow-up and move on. Keep a copy of what you submitted and add a line in the footer saying it was prepared for evaluation. A small note in the corner of a slide is fine; a giant watermark across the middle looks like you expect to be robbed, which is rarely the impression you want.
None of this is about refusing homework. A well-designed task is one of the better parts of hiring, because it lets you show craft instead of performing confidence. The trick is telling the difference early. Clear brief, honest time estimate, a named reviewer, a rubric? Do it and do it well. Mirrors a live project, no payment, no feedback promised? Say no politely, and keep your Saturday.