Unpaid Take-Home Assignments: How to Push Back Without Losing the Role

Somewhere between the recruiter screen and meeting anyone who would actually be your manager, an email arrives with a brief attached. Build a go-to-market plan. Design the schema. Write the campaign. Six to ten hours, unpaid, due Sunday.

You have not spoken to the hiring manager. You do not know the budget, the team, or whether the role is even funded. And you are being asked to do a piece of real work on the promise of being considered.

The advice you will get is one of two extremes. Either do everything they ask because you need a job, or refuse on principle and accept you will be dropped. Both are worse than the thing that actually works, which is a counter-offer.

Why a flat refusal usually fails

Not because employers punish it. Because of who receives it.

The person who emailed you the brief is very often a coordinator working through a checklist. They did not design the stage and they have no authority to remove it. When you refuse, there is nothing they are permitted to say back, so the thread simply stops. From your side that looks identical to being blacklisted for having a spine. It is not the same thing at all, and the difference matters, because it tells you what to send instead.

Give them something they are allowed to forward.

The counter-offer, in one paragraph

Do not argue about whether the assignment is fair. Accept the goal, cap the input, and offer a second option:

"Happy to show you how I would approach this. I cap unpaid work at ninety minutes, so here is what I would deliver in that time. Alternatively I can walk you through the same problem live on a call using work I have already done, whichever is more useful for you."

That does three things at once. It keeps you in the process. It hands the coordinator a yes they can take upstairs without needing permission. And the live-call option is frequently the one that comes back, because a call costs the company an hour and costs you nothing to prepare.

The two questions that tell you what you are dealing with

Before you commit any hours at all, send these. They are polite, they are reasonable, and the answers are diagnostic.

A real assignment has a named reviewer and a date. A pipeline has neither, and asking costs you nothing. If the answers are vague, you have learned something worth more than the assignment.

If the brief is obviously real work

Sometimes the task is not a test at all. It is a live problem the team currently has, with real constraints and real data, and completing it would produce something the company can use on Monday.

That is not an interview stage. That is a small project, and it is entirely normal to say so:

"This looks like a live piece of work rather than an exercise. I am glad to do it as a paid short engagement, or I can do a scoped version that demonstrates the approach without delivering the finished artefact."

The scoped version matters. It lets you say yes without handing over the deliverable, which is the part you are actually protecting.

What to do while you wait

Whatever you decide, do not let the assignment pause your search. The single most reliable way to make a slow process move is another live process, and a take-home stage is exactly where timelines quietly stretch from two weeks to six.

Keep applying at the same rate you were before the brief arrived. If the assignment leads somewhere, you have lost nothing. If it does not, you have not spent three weeks waiting on a thread that had already gone quiet.

The short version

Do not refuse, counter. Cap the hours out loud and offer a live call as the alternative. Ask who reviews it and when you will hear back, before you start. If it is real work rather than an exercise, say so and offer a scoped version. And keep applying the whole time.

At AI Applyd we keep sending applications while you are stuck in a stage like this one, so a six-hour brief does not quietly become a six-week gap in your pipeline. The advice above works with or without us.