Job interviews have always asked candidates to prove they can do the work. The argument now is about how much work a company can reasonably ask someone to do before the interview starts to look like an unpaid project.
Across Reddit, Hacker News, LinkedIn, career forums, and hiring guides, the same tension keeps showing up. Employers want evidence beyond a résumé and a polished conversation. Candidates increasingly say they are being asked to build presentations, write strategy plans, code applications, analyze real business problems, or spend entire weekends completing assignments for jobs they may never get.
This is a different problem from the outright rude behavior covered in our recent story on the most disrespectful job interviews candidates shared online. A take-home assignment can be perfectly professional. The question is whether the exercise is bounded, job-related, hypothetical, and actually designed to evaluate the candidate—or whether the candidate is quietly being asked to produce useful work for free.
A Good Work Sample Is a Real Hiring Tool
The basic idea behind a work sample is legitimate. The U.S. Office of Personnel Management describes work-sample tests as exercises that ask applicants to perform tasks similar to the work they would actually do on the job. OPM says these tests can have strong content validity because they measure job-relevant behavior instead of relying only on self-description.
That can be better than a vague interview full of trivia. A support candidate might draft two sample customer replies. A technician might diagnose a fictional fault. A developer might review a small piece of code. A finance candidate might analyze a short mock data set. The exercise can give the employer useful evidence while also showing the candidate what the job may feel like.
OPM’s broader assessment guidance also reports that work samples and structured interviews are among the stronger predictors in its comparison of selection methods. The problem is not the existence of a test. The problem is scope.
The Weekend Project That Looked Like a Backlog Ticket
In one 2026 r/recruitinghell post, a recent graduate said a company assigned a highly specific software feature after an initial screening. The candidate spent the entire weekend building it, adding tests and documentation, then received an automated rejection early Monday morning.
The poster said a more experienced engineer later looked at the prompt and believed it resembled a real backlog item rather than a generic assessment. That allegation is not independently verified, but it captures exactly why candidates become suspicious when an assignment maps too neatly onto a company’s live product.
When “A Couple of Hours” Becomes a Full Case Study
Another 2026 poster described repeated case studies involving mockups, roadmaps, sandbox accounts, research, and presentations layered on top of three, five, or six interview rounds. The candidate said one recent case study was praised during the presentation—and then the company stopped responding.
That frustration is easy to understand because interview time has an opportunity cost. Every evening spent building one employer’s deck is an evening not spent applying elsewhere, preparing for another interview, working a current job, or handling normal life. That is why the earlier BitcoinVersus story on how candidates know an interview failed matters here too: a long hiring process can consume substantial time even before a formal rejection arrives.
The 50-to-100-Hour Assignment
A 2025 software-developer candidate posted about a six-page take-home project that they estimated would take 50 to 100 hours over three weeks. The role was described as entry-level, while the candidate felt the assignment resembled a mid- or senior-level project. The company still planned another interview after the project.
There is no universal rule that says a legitimate take-home must be exactly one hour, two hours, or four hours. But once an assessment begins to resemble a part-time job, the employer should be able to explain why the scope is necessary, how it will be scored, whether every finalist receives the same task, and why a smaller simulation would not answer the same hiring question.
Twenty Hours After a Full-Time Job
One of the most widely discussed r/recruitinghell examples came from a candidate who said they completed more than six interview rounds and then spent about 20 hours on a take-home assignment while already working a full-time 9-to-5 job. They were rejected afterward.
The important point is not that a rejection proves the assignment was illegitimate. Employers are allowed to reject strong work. The problem is the imbalance of risk: the company may spend an hour reviewing something that cost the candidate several evenings to produce.
That imbalance becomes more obvious in a remote-hiring world. BitcoinVersus previously covered how strongly many workers feel about remote-work flexibility. A remote interview removes the commute, but it does not make a candidate’s nights and weekends worthless.
One Candidate Put a Price on the Homework
In a 2025 Reddit post that drew more than a thousand upvotes, a marketing candidate said they reached the third interview round and were asked to create a six-month marketing plan for a hypothetical company. The candidate responded by quoting a consulting fee—starting at $5,000 and increasing with scope.
That example is important because it cuts both ways. The assignment was described as hypothetical, so it may have been a legitimate evaluation rather than an attempt to obtain free production work. But the candidate still decided the amount of strategy being requested had market value. The disagreement was not really about whether skills should be tested; it was about who absorbs the cost of the test.
That is ultimately a negotiation question. Our negotiation masterclass makes the same broader point: a negotiation can fail without either side being irrational. The company can decide the test is required. The candidate can decide the price of participating is too high.
Where the Line Should Be
Good hiring guidance increasingly converges on a simple idea: keep the task realistic but bounded. OPM says a work sample should mirror the job. Indeed’s 2026 work-sample guide describes a work sample as a product evaluated against predetermined criteria. And Terra Talent’s structured-interview guidance goes one step further: it explicitly tells hiring teams not to use candidates for free work and recommends assignments adjacent to the company’s work rather than live deliverables the business actually needs.
That gives employers a workable standard. If the company needs to judge writing, give every finalist the same fictional brief. If it needs to judge code, use a contained repository or synthetic problem. If it needs strategy, provide a hypothetical market or an old problem whose answer is already known internally. The task can still be hard without being commercially useful to the employer.
Five Questions to Ask Before You Start
- How long should this take? Ask for the employer’s expected time budget, not just the deadline.
- Is the problem hypothetical? If it appears tied to live customers, a current product backlog, or a real campaign, ask directly.
- How will it be scored? A real assessment should have criteria beyond “we know good work when we see it.”
- How many candidates are doing it? A ten-hour project given to 100 applicants is a very different process from a two-hour exercise given to three finalists.
- Can the scope be reduced or compensated? If the project is extensive, asking about a paid trial, smaller exercise, portfolio review, or live walkthrough is reasonable.
AI Is Making the Boundary Even Messier
Generative AI complicates take-home tests from both directions. Candidates can now produce code, research, slide decks, wireframes, and strategy drafts much faster. Employers therefore may demand more complex deliverables because the old assignment no longer proves the same thing. But that can create an arms race in which candidates are expected to spend even more time polishing AI-assisted work.
The better answer may be to test judgment instead of sheer output: give a candidate a bounded problem, let them use the tools they would actually use on the job, and then ask them to defend their decisions live. That reveals far more than simply counting how many slides, features, or pages someone produced overnight.
The Interview Should Not Become the Job
A strong work sample can protect both sides. It helps employers avoid hiring someone who interviews well but cannot perform the work, and it helps candidates see what the role actually demands.
But the test stops serving that purpose when the assignment becomes so large that completing it requires unpaid nights, weekends, or production-ready deliverables with real business value. At that point the candidate is no longer simply demonstrating the job. They may be doing the job before anyone has agreed to hire them.
Leave a comment