Why Do Companies Ask You to Do Unpaid Work?
The short answer
You already gave the company your resume, your time, and probably several interviews. Being asked to surrender a weekend too can feel less like evaluation and more like paying for the chance to be considered. Jobbris is an AI resume optimizer that turns your real experience into a job-specific resume. Here is how to tell whether a take-home is fair.
Why do companies ask for unpaid work as part of interviewing?
A take-home assignment is work you complete outside an interview so a company can judge your skills. Companies use it because it saves interviewer time and shifts evaluation effort to you. A short, hypothetical test can be reasonable. Work on a real product, real data, or a live strategy can become unpaid consulting.
There is a legitimate reason for some assignments. A resume shows what you have done, but it may not show how you structure a messy problem, explain a tradeoff, or use a tool. Candidates who dislike live performance can also prefer a take-home because it gives them time to think.
The problem is the imbalance. The employer writes one prompt and sends it to several people. Each candidate may spend an evening, a weekend, or paid time off completing it, with no guarantee of feedback or another round. In a survey of roughly 700 interviewing.io users, about 85% said they had received a take-home at some point, and these assignments appeared in roughly 20% of the interview processes they encountered.
That survey is mostly useful as a directional look at engineering hiring, not a population-wide estimate. Still, its compensation gap is revealing: 58% thought take-homes deserved payment, while only 4% reported ever receiving it. The company saves screening time. The candidate absorbs the cost.
When does a take-home stop being a skills test and become free consulting?
A take-home starts looking like free consulting when it asks you to solve the employer's current problem using its real product, data, customers, or launch plan. A fair skills test uses a hypothetical, anonymized, or already-solved problem. The closer your deliverable is to something the company could use, the firmer your boundary should be.
A generic prompt can show how you think without creating business value for the employer. For example, analyzing a fictional product, critiquing a public campaign, or explaining a past project can reveal judgment and communication. The company learns about you, but it does not leave with a ready-to-use roadmap, feature, strategy, or sales plan.
Real company inputs change the bargain. Product leader Michelle Cavanaugh describes this boundary in The Free Consulting Interview: actual product materials, actual data, a live business problem, and an NDA can turn an exercise into a disguised consulting engagement. Reports that companies use rejected candidates' ideas remain anecdotal, so do not assume theft. Judge the scope you can see before you begin.
> A take-home should test how you think, not transfer a real business problem onto your unpaid weekend.
What should you ask before agreeing to a take-home assignment?
Ask what skill the assignment measures, how long the company expects it to take, who will review it, whether you will receive feedback, and whether the work concerns a live business problem. Clear answers signal a designed assessment. Vague scope, real deliverables, no named reviewer, or pressure to sign away your work are reasons to pause.
Use these questions before opening the document:
- What specific ability are you evaluating? - What is the expected time limit? - How many candidates are completing it? - Who will review it, and will we discuss my reasoning afterward? - Is the problem hypothetical, historical, or currently being worked on? - May I keep the work in my portfolio? - Is compensation available if the scope exceeds the stated limit?
You are not being difficult by asking. A serious hiring team should know what its own assessment measures. If it cannot explain why the task exists, the task may be measuring compliance or free time more than job performance.
How do you protect your time without walking away from every opportunity?
Set a timebox before you start, state it to the recruiter, and submit what fits within it. If the requested scope cannot fit, ask the company to reduce it, accept an existing work sample, or pay for the extra hours. Decline when the assignment remains real, open-ended, or disconnected from the role.
You can say: "I am happy to demonstrate this skill in a 90-minute exercise. The current brief appears to require a full strategy for a live initiative. Could we narrow the scope, review an existing work sample, or discuss a paid project?"
This protects your time without turning every take-home into a confrontation. It also gives the employer a chance to correct an oversized prompt. If the company refuses, you have learned something useful about how it values candidate time.
Opportunity cost matters too. Six unpaid hours on one uncertain assignment are six hours you cannot spend researching stronger roles, contacting people, resting, or submitting other thoughtful applications. If resume tailoring is consuming the time you are trying to protect, Jobbris creates a truthful, job-specific resume in about two minutes, so more of your effort can go toward deciding which opportunities actually deserve it.
What else should you know about unpaid interview work?
The practical questions are how common these assignments are, how much time is reasonable, and when the tradeoff is worth it. There is no universal cutoff, but you can judge each request by its scope, realism, review process, and the opportunity cost of the hours it demands.
They are common in technical hiring and increasingly visible in product, strategy, and other business roles. In interviewing.io's survey, about 85% of users had received one during their careers, and take-homes appeared in roughly one in five processes. Treat those figures as directional because the sample was largely engineers using one interview platform.
One to two hours is a reasonable ceiling for many unpaid skills tests. Beyond that, ask the company to narrow the scope, accept a work sample, or pay for the project. Complexity matters, but an estimate of four hours that actually demands a weekend is still an oversized assignment. Decide your limit before starting.
It can be worth completing a short, relevant, hypothetical test for a role you genuinely want, especially when you can discuss the work with the decision-maker. It is usually not worth doing live company work, producing an open-ended deliverable, or sacrificing many hours without clarity about review, feedback, and the next step.
Tanul Tewari
Founder, Jobbris
Building Jobbris to fix the part of the job search nobody talks about: the hours of tailoring and the silence that follows.