When to decline a take-home interview assignment: a guide
Take-home assignments are often legitimate skills demonstrations, according to an SHRM advice column published earlier this year. That same column confirms something specific: candidates can push back on a request, and they can decline one outright (SHRM). The harder question is knowing when to decline a take-home interview assignment rather than assuming every request is fair game.
That question sits inside a bigger hiring concern. A separate SHRM report published earlier this year found that in a survey of more than 2,000 U.S. workers and HR professionals, 63% said they'd worked with someone who looked strong on paper but couldn't perform once hired, and nearly 9 in 10 HR professionals said AI tools now make it significantly easier for candidates to appear more capable than they actually are (SHRM). That concern helps explain why employers may lean on skills assessments like take-home assignments, though the reporting doesn't establish how widespread the practice has become or whether it's growing.
This article builds a decision framework from that reporting, along with academic research on hiring fairness, organized around four questions: Is the assignment tied to the actual role? Is the time commitment clearly scoped? Will the employer explain how it's evaluated? And could the deliverable be useful to the company regardless of the outcome? That framework isn't published anywhere as a single test; it's this article's synthesis of the sources below, built to help sort a fair assignment from an excessive one.
It applies broadly to job seekers asked to complete a project, presentation, or work sample as part of an interview, from entry-level applicants to senior candidates, though the sources drawn on here don't speak to every career stage equally.
How long should a take-home interview assignment take?
SHRM's column sets a baseline: "A focused, time-bound assignment tied directly to the role is fair" (SHRM). The wording leans on those two qualifiers, focused and time-bound, not on the mere existence of homework.
A WinTech Learning Hub article published last year, citing 2023 Glassdoor research, reports that candidate drop-off climbs more than 30% once take-home tasks stretch past four hours, and it describes a two-to-three-hour limit as best practice for mid-level roles (WinTech Learning Hub). That figure reaches readers through WinTech's account of the Glassdoor data rather than Glassdoor's original research, so it's worth treating as a reference point rather than an industry standard. The same article notes that senior, executive, and caregiving candidates may need more flexibility, not less.
Sunflower Talent Strategies, a talent-strategy consultancy, recommends keeping assignments to one to two hours and using generic, low-stakes prompts. One example it gives for an executive-assistant role: draft a thank-you note to a donor on the CEO's behalf, rather than a task tied to a real client relationship (Sunflower Talent Strategies).
None of these figures function as a legal ceiling on assignment length. But asking a recruiter how long an assignment should realistically take, then comparing that answer against these benchmarks, may prompt further questions if the estimate and the actual workload don't line up.
Signs a take-home interview assignment is too much
The clearest warning signs tend to show up in scope and evaluation, not just hours logged. A 2025 study of 281 working adults found that work-sample tests, along with knowledge tests and in-person interviews, ranked among the most positively perceived selection methods candidates encounter. That same research found selection methods read as fairer to candidates when they're job-related and give them a genuine chance to demonstrate skill, rather than testing something adjacent to the role (Applicant Perceptions of Selection Methods, 2025).
Role matters here too. Sunflower's own examples show the range: a generic editing task on a short manuscript, or a 10-minute presentation on making a sandwich, demonstrates skill without asking for anything the company could use. A request to "prepare a campaign pitch for one of our current clients," without a specified budget, timeline, or deliverable format, sits at the other end, since it asks candidates to solve a live business problem (Sunflower Talent Strategies). The consultancy cites one case in which a candidate reportedly learned, after being rejected, that the campaign strategy she'd submitted was later implemented by the company that requested it. It's a single, extreme example, but it illustrates the underlying risk: real, usable work product looks different from a demonstration exercise.
SHRM's reporting on "skillfishing," a term for candidates appearing more capable than they actually are, adds a caution pointed the other direction. That reporting notes the practice is happening more frequently and more convincingly than before, partly because AI tools have changed how candidates present themselves (SHRM). The same report cautions employers against overcorrecting with burdensome assignments used as a substitute for well-designed assessment, since the goal is surfacing genuine capability rather than adding hurdles.
Combining those threads into a short checklist worth running before starting any assignment:
- Is the task tied to the specific role, not a generic skills test?
- Is the time commitment and scope clearly defined upfront?
- Will the employer explain how the work is evaluated?
- Could the deliverable be used by the company regardless of the hiring decision?
A "no" on the first three, or a "yes" on the last one, is worth raising directly with the employer.
Is a take-home interview assignment unpaid work?
Sunflower Talent Strategies says unpaid working interviews can raise wage-and-hour concerns and recommends compensating candidates for assignments beyond one to two hours (Sunflower Talent Strategies). That's one consultancy's position, not a determination from the Department of Labor itself, and it shouldn't be read as establishing a specific hour count as a legal threshold. Anyone facing a real unpaid work during the interview process question should verify current requirements with the Department of Labor or an employment attorney rather than treat a blog post as settled law.
WinTech's article, drawing on its own account of industry norms, describes payment for assignments longer than three hours or involving commercially valuable deliverables as "increasingly the norm" in creative, consulting, and engineering fields, citing figures in the roughly $100 to $500 range for U.S. tech and creative roles (WinTech Learning Hub). That characterization comes from a single secondary source, not an independently verified market survey, so it's a data point rather than a market standard.
SHRM's column focuses on time, evaluation, and scope rather than legal obligations. The clarifying questions it identifies: how long the assignment should take, how it will be evaluated, and whether the scope has flexibility, with the note that "serious employers will have thoughtful answers" (SHRM). Compensation doesn't appear among the questions identified in that source, though candidates facing a lengthy or commercially useful assignment can raise it separately, framed as a question about an honorarium rather than a wage claim. If that conversation starts to sound like a legal dispute, that belongs with the Department of Labor or a qualified employment attorney, not general hiring guidance.
Deciding whether to complete, negotiate, or decline
SHRM frames the interview itself as a two-way evaluation. "The company is assessing your skills," the column notes, while "you're assessing their judgment, culture, and what they prioritize in candidates" (SHRM). Asking for clarity fits naturally inside that dynamic. It isn't an imposition; it's part of how a well-run process is supposed to work.
Building on that framing, three practical responses are available, depending on how an assignment holds up against the checklist above.
Complete the assignment when it's tied to the actual role, scoped with a clear time estimate, evaluated against criteria the employer is willing to share, and unlikely to produce work the company could use regardless of the hiring decision.
Negotiate first when some of those answers are missing. SHRM's suggested questions offer a starting script: "Thank you for the opportunity to interview for this role. Before I begin, could you share roughly how long this should take, how it will be evaluated, and whether there's flexibility in scope?" A lengthy assignment, or one built around commercially useful deliverables, is also a reasonable moment to ask about compensation, a question SHRM's own list doesn't include but candidates can raise on their own.
Decline when the answers confirm a heavier lift than expected, the scope keeps expanding, or the request feels disconnected from the actual work despite the clarifying questions. SHRM recommends doing this professionally: thank the employer, keep the door open, and remember that "the hiring process is often the most organized a company will ever be." As the column puts it, "if it feels misaligned now, it likely won't feel better later" (SHRM). A short decline message can follow that same tone: "Thank you again for considering me for this position. After reviewing the assignment, I'm not able to commit the time it requires right now. I've enjoyed learning about the team and would welcome staying in touch for future opportunities."
Before opening any assignment, sending the clarifying questions above, and following up on wage or compensation concerns with the Department of Labor or an employment attorney if they arise, costs little compared to the alternative of working through a mismatch quietly.
