Take-Home Assignments: Reasonable Screening Tool or Free Labor

Somewhere between a 30-minute coding exercise and a 12-hour strategy deck sits a real line, and most candidates can feel exactly where a given assignment falls on it, even before they finish reading the brief.

A take-home assignment exists, in theory, to test whether you can do the job. That's a legitimate goal. Plenty of roles benefit from seeing actual work rather than relying on an interview conversation alone. The problem isn't the format. It's how often the format gets stretched well past what a reasonable screening step requires.

A few signs the line has been crossed: the assignment asks you to solve a real, current problem the company is actually facing, rather than a representative sample task. The scope keeps growing after you submit, more rounds, more revisions, more "just one more thing." There's no time limit communicated upfront, which tends to produce an unspoken expectation that more hours equals a better impression. And the deliverable, if you're honest with yourself, looks suspiciously like something the company could use whether or not they ever hire you.

None of these signs are proof of bad intent on their own. A hiring manager might genuinely believe a real-world problem makes for a more honest assessment than a canned exercise. But intent doesn't change what it costs the candidate, often several unpaid hours, sometimes more, with no guarantee of anything in return.

A fair version of this process tends to share a few traits: a clearly stated time box, ideally under two or three hours, an assignment built specifically for evaluation rather than pulled from a live project, and, where the scope is larger, actual payment for the time. Some companies do pay for substantial take-home work. It's not common, but it exists, and it's a meaningful signal about how a company values the time of people it hasn't hired yet.

If you're deciding whether to spend your weekend on an assignment, it's worth checking whether the company has a documented pattern here, not just relying on how the one recruiter described it. A company with a track record of average test burden well above what's typical for the role is telling you something about what's actually expected, regardless of how the assignment is framed during the interview.