What Is a Work Sample Test and Should You Be Paid for It?
By Pinal Dave | Last updated: 2026-08-01
TL;DR: A work sample test is a scoped exercise — a mini project, writing sample, or case task — meant to simulate real job work so employers can assess ability directly rather than through interviews alone. Short exercises (under 2 hours) are usually unpaid and standard practice; anything longer, or work the company could actually use, should reasonably come with pay or a clear time cap.
Why Companies Use Work Samples
Structured hiring research consistently shows work sample tests are one of the more predictive assessment methods available, often outperforming unstructured interviews alone at predicting job performance. That's why they've become common for design, writing, data, product, and engineering roles — the company gets a direct look at how you actually work, not just how you talk about your work.
Work Sample Norms by Scope
| Test Scope | Typical Pay Expectation | Reasonable Time Cap |
|---|---|---|
| Short exercise (under 2 hours) | Usually unpaid, standard practice | 1-2 hours |
| Take-home project (2-6 hours) | Often unpaid but should be clearly time-boxed | 4-6 hours max |
| Project resembling real, usable work | Should be paid or use a fictional/sanitized scenario instead | N/A — flag this directly |
| Live paired exercise (during interview) | Unpaid, standard | 45-90 minutes |
| Multi-day project | Should be paid | Negotiate scope down or ask for compensation |
Step-by-Step: Handling a Work Sample Request
- Ask for a time estimate upfront. A reasonable employer can tell you roughly how long the exercise should take — if they can't, that's worth probing.
- Time yourself honestly. Don't massively over-invest beyond the stated scope; going far beyond the ask doesn't usually improve your odds and sets a bad precedent.
- Flag if the task resembles real company work. If you're asked to redesign an actual product feature or write real marketing copy the company could plausibly use, it's fair to ask whether it's paid.
- Keep a copy of your submission. For your own records and to reference in a follow-up interview discussion of your approach.
- Ask what the evaluation criteria are. This helps you focus effort where it's actually scored rather than polishing things that don't matter.
- Request feedback regardless of outcome. Even unsuccessful candidates can reasonably ask for a brief note on how the sample was evaluated.
- Decline politely if the ask feels disproportionate. A multi-day unpaid project for an entry- or mid-level role is a reasonable thing to push back on or decline.
Frequently Asked Questions
Is it normal for companies to not pay for take-home assignments? Yes, for reasonably scoped exercises (a few hours) — this remains standard practice across most industries, though the trend toward paying for longer assignments has grown.
What counts as "too long" for an unpaid work sample? There's no universal legal cutoff, but hiring best practices commonly cite roughly 2-4 hours as the ceiling for unpaid exercises — beyond that, compensation or a shorter alternative becomes reasonable to request.
Can I ask for payment before starting the assignment? Yes — asking "is this paid, and if not, is there a way to scope it down" is a professional, direct way to raise the question before investing your time.
Does refusing a work sample test hurt my candidacy? It can, since some companies won't move forward without it — but pushing back on disproportionate scope, rather than refusing outright, is usually a more productive path.
Should the work sample match the actual job I'd be doing? Ideally yes — a well-designed test closely mirrors real job tasks, which is also a good sign about how the company evaluates work internally.
What if I suspect the company is using submissions as free work? This is a legitimate concern with tasks that mirror real product or content needs — ask directly whether submissions are used internally, and consider declining if the answer is unclear or evasive.