You have just received an email from a hiring manager that includes a link to a take‑home task. The message says the assignment will help the team gauge your skills before a final interview. You recognize the format from previous applications, but you also wonder how much time is reasonable to invest and whether the work borders on unpaid labor. This guide breaks down what a proportionate task looks like, how to set boundaries, and what steps to take if the brief feels like actual production work.
What a reasonable task looks like
A proportionate take‑home task is typically short, focused, and can be completed in a few hours. It should target a specific skill relevant to the role—such as writing a brief code snippet, drafting a short design outline, or answering a set of scenario questions—rather than replicating a full project. The deliverable is usually a single file or a short set of artifacts that the hiring team can review quickly. If the assignment asks for a complete feature, a polished UI, or extensive research, it likely exceeds the normal scope for an assessment.
Distinguishing assessment from free work
The line between an assessment and unpaid work appears when the task produces value that the company could use directly. An assessment asks you to demonstrate your thought process, not to deliver a finished product that will be shipped or published. If the brief requests a market analysis, a full blog post, or a prototype ready for release, that is production work, not a test. In those cases, the effort you invest could be considered labor that benefits the employer without compensation.
Setting expectations for time
Before you start, ask the recruiter how long the task is expected to take and confirm that the estimate matches the scope. A clear time frame protects you from scope creep and lets you allocate your schedule realistically. If the response is vague, propose a reasonable window—typically one to three days for a 2‑hour task or up to a week for a more involved assignment. Stick to the agreed limit; if additional work is requested, treat it as a new request and negotiate accordingly.
Handling production‑type briefs
When the brief reads like a real project—asking for a complete feature, a polished design, or a detailed report—raise the concern early. Explain that you are prepared to showcase your approach, but a full production deliverable exceeds a typical assessment. Suggest a reduced version that captures the core challenge, such as a high‑level architecture diagram instead of a fully coded module. This signals professionalism while protecting your time.
Negotiating format or scope
If the requested format doesn’t suit your strengths or tools, propose an alternative that still meets the evaluation goal. For example, replace a lengthy coding exercise with a concise algorithm description and pseudocode, or swap a design mockup for a wireframe sketch. Communicate the change clearly, stating why it better demonstrates the relevant skill. Most hiring teams appreciate flexibility and will accommodate reasonable adjustments.
Declining while staying in the pipeline
If the task remains unreasonable after discussion, you can decline without closing the door. Respond politely, thank the recruiter for the opportunity, and explain that the scope exceeds what you can allocate at this stage. Offer to continue the process through a different assessment method, such as a live coding session or a structured interview. This approach preserves the relationship and leaves room for future consideration.
Worth remembering: Treat take‑home tasks as a short, skill‑focused assessment, not a free project. Clarify time expectations up, for scope that feels like production work, and negotiate format when needed. If the request stays unreasonable, decline politely while expressing interest in alternative evaluation methods.
Common questions
How long should a take‑home task take?
A typical assessment is designed to be completed in a few hours, usually no more than one to three days of part‑time effort. If the recruiter does not specify a timeframe, ask for an estimate and propose a reasonable window that matches the task’s scope.
What if the task feels like actual work for the company?
When the brief asks for a finished product, a detailed report, or a feature ready for release, it crosses into production work. In that case, raise the concern, suggest a reduced version that demonstrates your approach, or request a different assessment method.
Can I ask for a different format for the take‑home task?
Yes, proposing an alternative format is acceptable as long as it still lets the hiring team evaluate the targeted skill. Explain why the new format is a better fit for you and how it meets the assessment goal; most recruiters will accommodate reasonable requests.