Should you do an unpaid take-home assignment for a job?

The short answer

Yes, sometimes — but not automatically. A take-home assignment can be a sensible part of hiring when it is brief, clearly connected to the work, and used to check how you think, not to get free labour.

If it is open-ended, unusually large, or asks for work that looks useful to the employer on its own, you should be cautious. You do not owe unlimited time just because you want the job.

What the task is really for

A take-home assignment is supposed to answer a simple question: can you do this kind of work to a useful standard? In a fair process, it gives the employer a way to see your thinking, your judgement, and your ability to communicate without putting you on the spot in real time.

That is the legitimate version. The less legitimate version is when the task starts to function like unpaid production work. The line between the two is not always neat, but the intention and the scope matter.

If the assignment is basically a test, it should feel like a test. If it feels like a piece of work that could be dropped into the business with minimal changes, you are entitled to ask harder questions.

The first thing to check

Before you decide whether to do it, read the brief as if you were already being asked to spend your time on it. You are looking for four things:

• how long it should reasonably take
• what kind of skill it is meant to show
• whether the inputs are complete enough to do it fairly
• whether the output is clearly for assessment rather than use

If any of those are missing, the assignment is already weaker than it should be.

A good brief tells you the purpose, the constraints, the expected format, and the deadline. A poor brief makes you guess.

When an unpaid take-home assignment is reasonable

An unpaid task can be reasonable when it is small enough to respect your time and specific enough to evaluate the work properly. That usually means it is focused on one or two skills, not a full project.

Typical signs of a reasonable task:

• it is limited in scope
• it is tied closely to the role
• it does not ask for original work that the employer could directly use
• it has a clear time expectation
• it comes after some real contact with the hiring team
• the instructions are specific and professional

The closer the task is to the actual work, the better. That is not the same as asking you to do real work for free. A fair assignment should simulate the job, not replace part of it.

When you should be wary

You should be wary when the brief is too big, too vague, or too close to free consultancy.

Warning signs include:

• the assignment is open-ended with no clear limit
• it asks for polished work that would take substantial time
• it requires research, design, writing, analysis, or planning that looks directly reusable
• the employer cannot explain why the task is necessary
• they are unwilling to say how long it should take
• they expect a full weekend’s worth of effort as a standard step
• the same task could easily be used to gather ideas from multiple candidates

A bad task often feels like a real brief without a real boundary. That is the problem.

If you cannot tell whether the exercise is reasonable, ask. A fair employer should be able to explain the goal in plain language.

How long should a take-home test take?

A take-home assignment should take a bounded amount of time. If the employer cannot tell you what that is, that is already a warning sign.

What matters is not just the content but the expectation. A short exercise with clear limits is very different from a vague project that can expand to fill your weekend.

If the task is supposed to be quick, the instructions should reflect that. If it is not quick, then it should be treated with the same seriousness as real work: there should be a reason for the length, a fair process, and a clear benefit to you as a candidate.

A useful question is: if I do this well, what will they learn that they could not learn from my CV, interview, or work history? If the answer is not much, the assignment may be doing too much.

How to judge whether it is really unpaid work

The easiest way to spot the difference is to ask whether the output is useful only as evidence of your ability, or useful as work in itself.

A genuine test usually has one or more of these qualities:

• it is based on a hypothetical or controlled scenario
• it deliberately limits the time and scope
• it asks for explanation of reasoning, not just a finished artefact
• it is easy to compare across candidates

A task starts to look like unpaid labour when it asks for:

• real deliverables that could be used immediately
• detailed work on the employer’s actual problem
• content, strategy, code, design, or analysis with obvious commercial value
• multiple hours of refinement with no real boundary

The more the assignment resembles work product the employer could keep, the more justified you are in pushing back.

What to ask before you start

If the task is not obviously tiny and fair, ask a direct question before you agree. Keep it calm and practical.

You can ask:

• How long do you expect this to take?
• Is this meant to be a short exercise or a fuller case study?
• Will the output be reviewed only for assessment?
• Is there any scope to complete part of it live instead?
• What part of the work matters most to you?

These are sensible questions, not awkward ones. A serious employer should welcome them.

If they respond defensively, that tells you something. A good process does not require you to pretend your time is free.

What if the task is very interesting?

Sometimes the assignment itself is useful practice, and that can make it tempting to accept even when the process is flawed. That is understandable, but do not let interest become an excuse for a bad boundary.

If you want the job and the task is genuinely relevant, it can still be worth doing. Just be honest with yourself about the trade-off. You are not only deciding whether you can do the work; you are deciding whether this employer treats candidates in a way you can live with.

A role can be attractive and still not be worth a long unpaid assignment.

What if you are early in your career?

Early-career candidates often feel they cannot say no. That is not true. What changes is how you weigh the opportunity.

If you have little experience, a reasonable assignment can be a fair way to show what you can do. It may even help you compete with people who have more direct experience. But that does not mean you should accept anything.

You are still allowed to reject tasks that are too long, too vague, or too close to doing real work for free. Being junior does not cancel your judgement.

What if you are changing careers?

A take-home assignment can help if it lets you show transferable ability in a practical way. If you are moving into a new field, a small exercise can be one of the clearest ways to prove you can already think like the job.

That said, career changers are often more vulnerable to overdoing it. It is easy to think you need to prove yourself by spending far longer than requested. Do not do that unless the process genuinely calls for it.

If the task is fair, complete it well. If it is not, the fact that you are changing careers does not make the burden smaller.

What if the assignment is optional?

If it is optional, read that literally. Optional means you have a choice.

Sometimes an optional task is a useful extra signal. Sometimes it is a way for the employer to see whether candidates are willing to do more than the minimum. The second version is not automatically bad, but you should be conscious of what you are agreeing to.

If the task is optional and substantial, ask yourself whether it is likely to change the outcome enough to justify the time. If the answer is no, skip it or offer a shorter response.

What if everyone else is doing it?

That argument is common and not very strong. The fact that other candidates may comply does not automatically make the task fair.

You only need to decide whether it makes sense for you. If you want the role enough to accept the cost, that is your call. But do not confuse competition with obligation.

A process can be widespread and still be poor. Popularity does not fix an unfair burden.

How to push back without burning the opportunity

If you do not want to refuse outright, you can respond with a boundary and a willingness to continue.

For example:

Thanks — I’d be happy to do a short exercise if you can confirm the expected time commitment and the main thing you want to assess. If the task is likely to take much longer, I’d prefer to discuss the approach live.

That keeps the conversation open while making your limit clear.

You are not being difficult. You are showing judgement.

What to do if they insist on a large task

If they want a large assignment and will not adjust it, decide whether the role is still worth the cost.

A few questions help:

• Is this role genuinely worth several hours of unpaid work to me?
• Does the process suggest they respect candidates?
• Would I still want to work here if this is how they hire?
• Am I being asked to do something that gives them usable work rather than a fair test?

If the answer to the last question is yes, be careful. A process that starts with taking advantage of your time can be a bad sign about the job itself.

A better way to think about the decision

Do not ask only, “Can I do this?” Ask, “Is this a fair use of my time for this stage of hiring?” That is the more useful question.

A reasonable take-home assignment can be worth doing when:

• the role is a strong fit
• the task is short and well-defined
• the employer is clear about expectations
• the output is clearly for assessment
• you are comfortable with the time cost

It is usually not worth doing when:

• the scope is vague or excessive
• the employer cannot explain the purpose
• the work looks reusable
• the process feels one-sided
• the time demand is disproportionate to the stage of hiring

What if you already spent a lot of time on it?

If you have already started and the task is turning out to be bigger than expected, you still have options.

You can:

• send a partial submission with a note about the time you had
• explain the assumptions you made
• highlight the parts you completed and why
• keep the tone professional and calm

Do not disappear without a word if you have committed to something. But do not quietly accept moving goalposts either. If the brief changed in a way that makes the task unreasonable, say so.

What a good submission usually looks like

A strong take-home submission is usually clear, concise, and easy to assess.

It should:

• answer the question directly
• show your reasoning, not just the outcome
• stay within the scope of the brief
• be polished enough to read well, not so polished that it becomes a portfolio piece for them to keep
• make it easy for the reviewer to compare your work with others

You do not need to overproduce. In many cases, clarity beats volume.

What to avoid if you decide to do it

If you accept the task, avoid two common mistakes.

First, do not turn it into an unpaid love letter to the employer. The assignment is not a chance to prove loyalty.

Second, do not over-invest in perfection if the brief does not justify it. If they asked for a sketch, do not build a cathedral.

Match the effort to the question.

When you should simply say no

Sometimes the right answer is no.

Say no if the assignment:

• is too large to be fair
• lacks a clear limit
• asks for real work that the employer could use
• arrives too late in the process for the amount of effort requested
• feels inconsistent with the rest of the hiring experience

You do not need to apologise for protecting your time. A brief, polite refusal is enough.

For example:

Thanks for the opportunity. I’m going to step back from the exercise, as the scope is more than I’m able to commit to at this stage. I appreciate your time and wish you well with the search.

That is clear, civil, and final.

What this says about the employer

How an employer handles a take-home assignment tells you something important.

A good process usually shows:

• respect for candidate time
• clarity about what matters
• confidence in a fair assessment method
• discipline about scope

A poor process often shows the opposite.

That does not mean every imperfect assignment is a red flag. Hiring is messy, and some teams are simply not great at designing tests. But if the task repeatedly feels inflated, vague, or extractive, take that seriously.

The simplest rule

Do the assignment if it is short, relevant, and clearly meant to assess you. Push back if it is vague, too long, or looks like free work. And if the employer will not treat your time with basic respect, you are allowed to walk away.