An unpaid interview project sits in a gray area of the hiring process. Some assignments are a reasonable way for both sides to test the fit. Others quietly cross into free labor a candidate should decline. The Complete Interview Guide for Today’s Hiring Process covers what a healthy interview process looks like overall. This piece focuses on one specific decision inside that process. The right answer depends less on the request itself and more on three things. Those are its scope, its purpose, and what happens to the work afterward.
What Counts as a Reasonable Unpaid Interview Project?
A short writing sample, a brief case study, or a one-hour exercise is a normal part of hiring. These assignments let a hiring team see real work rather than a rehearsed answer. A reasonable project asks for an hour or two of effort. It closely mirrors the actual role, and it gets evaluated by someone who gives real feedback afterward. A sales candidate might be asked to record a short mock pitch. A writer might be asked to submit one sample article on a relevant topic. Both fall well inside a reasonable scope. A candidate who understands these baseline expectations is better positioned to spot a request that falls outside them.
When an Unpaid Project Crosses Into Free Labor
The line gets crossed when a project asks for real, deliverable work rather than a sample of thinking. A marketing candidate asked to build an actual campaign plan for a real product launch is a clear example. That request is free labor dressed up as an interview step. So is a developer asked to build a working feature for a company’s live product. The clearest sign is whether the company could plausibly use the output, regardless of who ends up getting hired. A second sign worth watching for is scope that keeps growing after a candidate agrees to start. That kind of expansion rarely shrinks back down on its own.
Why Do Companies Ask for Unpaid Projects at All?
Most companies that ask for a project genuinely want a better read on skill. A resume or interview alone often can’t give them that. Some also use it, intentionally or not, as a cheap way to get real work done. A pool of unpaid applicants ends up doing that work for free. Both motivations can be present in the same request. That is part of why a candidate needs to look closely at what is actually being asked for. Accepting the stated reason at face value isn’t always enough. A company’s hiring volume is a useful clue here. A team running the same project past a dozen finalists for one open role has a real incentive problem. That’s different from a team asking one strong candidate for a narrow work sample.
Questions to Ask Before Agreeing to Do the Work
A candidate does not have to accept a project assignment without asking a few direct questions first. How long should this reasonably take? Who reviews it, and will there be real feedback either way? Will any part of this work actually get used by the company? Questions Candidates Should Ask During an Interview covers more questions worth asking earlier, before a project ever comes up.
How Much Time Is Too Much Time?
A useful rule of thumb: two to four hours is a reasonable ask for most roles below the executive level. Anything approaching a full workday should raise a real question. Candidates juggling a current job or several interview processes at once have a lot already on their plate. That workload is worth weighing against the request. A company that respects a candidate’s time will usually say so upfront, in writing, rather than leaving the scope open-ended.
What to Do When the Project Feels Excessive
Excessive scope is worth raising directly rather than silently completing it or silently declining. A candidate can ask to scale the assignment down. A candidate can also propose a shorter version that still demonstrates the same skill. Asking for a specific time cap works too. Interview Preparation Checklist: Everything to Do Before Your Interview is a useful reference for walking into that conversation ready.
Is It Reasonable to Ask to Be Paid for the Work?
Asking for payment on a substantial project is increasingly normal. That’s especially true for senior, technical, or creative roles where the deliverable resembles real client work. A company confident in its process usually has an answer ready. Sometimes that answer is a flat stipend. Sometimes it is a firm policy of not asking for anything beyond a short exercise. A company that reacts defensively to the question is showing something worth noting on its own. Candidates should also ask whether the same policy applies to every finalist. A company that pays only when pushed is signaling something different than one with a consistent stated policy.
Signs the Project Is Being Evaluated Fairly
A few signals suggest a company is running a genuinely fair process. Every finalist gets the same assignment and the same amount of time to complete it. Someone reviews the work using a defined rubric, not just a gut reaction. Feedback goes to every candidate, not only the one who gets the offer. The recruiter or hiring manager can explain, specifically, what the assignment is meant to reveal about the role. A process missing most of these signals is not necessarily malicious. It is still worth asking about before investing real hours. Candidates who ask these questions upfront often get a clearer read on a company’s hiring maturity. That read can say more than the interview itself.
When Saying No Is the Right Answer
Declining a project is reasonable when the scope is excessive or the ownership of the work is unclear. It’s also reasonable when the company can’t explain why the assignment is structured the way it is. When and How to Say No to Job Interview Projects covers how to decline without damaging the relationship. It also looks at why these assignments are controversial in the first place. Turning down one project rarely closes every door with a company that respects the decision. More often, the reaction to that decision reveals whether the company was worth pursuing.