Take-home assignments:
how much unpaid work is too much?

The email arrives after a good first interview: "As a next step, we'd like you to complete a short assignment." Attached is a brief. You open it, and within a minute you're doing mental math. How long will this really take? Is everyone else spending a weekend on it? Should you?

Take-home assignments are common in engineering, design, data, marketing, writing and product roles, and they're one of the few parts of hiring where a candidate can reasonably push back. Some are a fair way to show what you can do. Some are a weekend of unpaid work that one person skims for five minutes. Telling them apart early saves a lot of resentment.

Why companies use them

It helps to understand the honest case for take-homes, because it tells you what a good one looks like.

A take-home replaces the most artificial part of interviewing: solving a problem live, under time pressure, with someone watching. Many people do much better work at their own desk, with their own tools, at their own pace. A well-designed assignment is closer to the actual job than a whiteboard ever is.

The problem is that the cost falls on you. An interviewer's hour is paid; your evening isn't. A fair process is one where that trade is reasonable and respected.

What a fair assignment looks like

Most reasonable take-homes share these traits:

• A stated time budget, and it's honest. "Spend about three hours" is a good sign. "There's no time limit" usually means the strongest submissions came from people who spent two days.
• A small, well-defined scope. One problem, clearly described, with an obvious finish line.
• A made-up or public problem. A fictional company, a public dataset, a generic feature. Not their real backlog.
• A review conversation afterwards. The best processes use your submission as the starting point for a discussion. That's when the work turns into evidence about how you think.
• It comes at the right stage. After at least one conversation, so they've invested time in you too. Not as a filter before anyone has spoken to you.

The warning signs

Some patterns suggest the assignment is about getting work done rather than learning about you:

One sign alone isn't a reason to refuse. Two or three together are a good reason to ask questions before you start.

How much time is reasonable?

There's no official number, but a useful way to think about it is relative to the stage and the seniority of the role.

A few hours is the comfortable zone for most roles. That's enough to show real skill and judgment without asking for a weekend.

A full day is a big ask. It can be fair in a final round for a senior role, especially if the company says so upfront and the review conversation is substantial. Some companies pay for longer assignments, and that's worth asking about.

More than that is a project. Unless you're being paid for it, or it's for a role you want more than any other, it's reasonable to decline or negotiate.

Also count the hidden time: reading the brief, setting up, writing up your decisions. A "three-hour" task often takes five once that's included.

How to push back without losing the role

You have more room to ask than you might think. Companies that use take-homes usually want good candidates to finish them, and a polite question rarely hurts.

Ask before you start.

"Thanks for sending this. Before I begin, how much time do you expect it to take, and how will it be reviewed? I want to make sure I focus on what matters most to you."

The answer tells you a lot. A clear time budget and a review call is a good sign. A vague answer is a warning.

Offer an alternative when the scope is too big.

"I'm excited about the role, but I can't commit a full weekend right now. Would it work if I focused on the core of the problem, around three hours, and explained what I'd do next with more time?"

Many companies will say yes. If they don't, that's useful to know about how they treat people's time.

Offer existing work instead. If you have a portfolio, a public project or a writing sample that shows the same skills, ask whether it could replace the assignment, or shorten it.

Ask about payment for large tasks. "Is this assignment compensated?" is a normal, professional question for anything over a day of work.

Doing it well when you do it

If the assignment is fair and the role is one you want, make the hours count:

1. Respect the time budget. Going far beyond it can backfire. Reviewers often value judgment about what to leave out more than polish.
2. Write down your decisions. A short note explaining what you prioritized, what you skipped, and what you'd do with more time is often read more closely than the work itself.
3. Solve the brief, not a different problem. Read it twice. Many submissions fail because they answer an easier or more impressive question than the one asked.
4. Prepare for the review. Be ready to explain every choice and to discuss how you'd change your approach. This conversation is often where the decision is made.

The bigger picture

A take-home tells you something about the company too. A short, thoughtful assignment with a real review conversation usually comes from a team that's careful about hiring. A sprawling, unscoped task with no follow-up often comes from a team that's careless with people's time, and that rarely stops at the hiring process.

You're allowed to treat it as information. The question isn't only "can I do this?" but also "does the way they asked tell me I want to work there?"

A take-home is easier to say yes to when it's one of a few live processes, not one of fifteen. Jobiz helps you aim applications at roles that fit, so the assignments that reach you are ones worth your evening.