How to Decline an Unpaid Take-Home Assignment in English

Take-home assignments are a normal part of many interview processes, but some cross a line — many hours of unpaid work, or scope that looks suspiciously like real production work. Declining or pushing back on this needs care: you want to protect your time without appearing difficult or unwilling to demonstrate your skills. This guide gives you the English to do both.

---

Asking About Scope Before Committing

Before agreeing or objecting, get clarity on exactly what’s being asked and how long it should take.

• “Before I start, could you tell me roughly how much time this is expected to take?”
• “Is there a suggested time box for this, or is it open-ended?”
• “Can you share what specifically you’re hoping to evaluate with this assignment, so I can scope my time accordingly?”

Naming the Concern Directly

If the scope feels excessive, say so clearly and specifically, rather than vaguely expressing discomfort.

• “Based on the requirements, this looks like it would take significantly more than the [X hours] mentioned — I wanted to flag that before starting.”
• “I want to be upfront: I’m not comfortable with an open-ended, unpaid assignment of this scope.”
• “This looks close to production-level work rather than an evaluation exercise, and I’d like to understand the reasoning behind the scope.”

Proposing a Capped Alternative

Offer a specific, smaller version of the task that still lets you demonstrate the skill in question.

• “Would you be open to me completing a scoped-down version — say, [specific reduced scope] — within [X hours]?”
• “I’d be glad to do a timed version of this, capped at [X hours], and we can discuss the rest live in a follow-up conversation.”
• “Rather than the full assignment, could I walk you through my approach to the harder parts in a live session instead?”

Asking About Compensation for Larger Scope

If the task genuinely requires substantial time, it’s reasonable to ask whether it’s compensated.

• “Given the scope here, is this a paid assignment, or is there flexibility to reduce it to an unpaid-appropriate size?”
• “I’m happy to invest real time in this if it’s compensated — otherwise, I’d like to propose a smaller version.”
• “Would the team consider a small stipend for assignments of this size, similar to what some other companies do?”

Declining While Staying in the Process

If they won’t adjust and you decide not to proceed, say so professionally, without burning the relationship.

• “I appreciate the opportunity, but I’m not able to commit unpaid time at this scope — I’d welcome staying in touch for other formats, like a live technical conversation instead.”
• “This isn’t the right fit for me given the assignment’s scope, but I remain very interested in the role if there’s a different way to evaluate my skills.”
• “Thank you for understanding — I hope we can find another way to continue the conversation.”

Offering a Constructive Alternative to the Process

Suggest a different evaluation method that respects both sides’ time.

• “Would a live pairing session or a walkthrough of a past project work as an alternative to the take-home?”
• “I’d be glad to discuss a project I’ve already shipped in depth, if that would give you similar signal without the additional unpaid time.”

---

Vocabulary Reference

Term	Meaning
Take-home assignment	A coding or written task candidates complete outside of a live interview
Time box	A fixed, capped amount of time allotted for a task
Scope creep	A task growing beyond its originally intended size or effort
Stipend	A small payment offered for time spent, distinct from full compensation
Live pairing session	An interview format where a candidate solves a problem collaboratively with an interviewer in real time

---

Key Takeaways

• Ask about expected time and scope before agreeing to any take-home assignment.
• Name concerns about excessive scope directly and specifically, not vaguely.
• Propose a smaller, capped, or paid alternative rather than simply refusing outright.
• If the scope isn’t adjusted, decline professionally and suggest staying in touch.
• Offer a constructive alternative evaluation format that respects both parties’ time.

Navigating Unpaid Work Requests – A Practical Approach

Let’s face it: sometimes the enthusiasm of a hiring manager can lead to requests that feel… off. An extended, unpaid take-home assignment, especially early in the interview process, isn’t necessarily indicative of a great company culture or a realistic job offer. It’s perfectly acceptable—and increasingly common—to politely push back on such demands while still demonstrating your commitment and professionalism. The key is to frame your response strategically using precise language that conveys respect for their time while firmly establishing your boundaries around fair compensation.

Consider this scenario: you’ve been invited to complete a 40-hour take-home project as part of the final stage of your interview process at a mid-sized tech firm. During your initial discussion, the lead engineer suggests dedicating an entire week to this unpaid task, promising it’s standard practice for their team and will allow them to deeply assess your skills. You could simply say “no,” but that can feel abrupt. Instead, you might respond with something like: “That’s a really generous offer, and I appreciate you outlining the process. However, given the time commitment involved—40 hours—I’m concerned about the impact on my other commitments and the value of this project relative to the overall role. Could we discuss exploring alternative ways to demonstrate my abilities? Perhaps a smaller, paid challenge focused on [mention specific skill] or a dedicated technical interview covering similar areas?”

Another approach might be more direct within a Slack channel after receiving the initial request: “Hey team, thanks for reaching out about this extended take-home assignment. While I’m excited to contribute and demonstrate my skills, dedicating that much time without compensation feels a bit outside standard practice. I’m happy to explore a focused assessment – perhaps a code review of a small feature or a technical deep dive – that aligns better with the scope of the role.”

Finally, when drafting your pull request description after a brief paid task (perhaps a smaller proof-of-concept), you could include a sentence like: “This PR demonstrates my ability to [key skill] within a reasonable timeframe and aligns with the compensation expectations for this position. I believe a more extensive, unpaid assignment at this stage isn’t the most effective way to evaluate my suitability.” Remember, clarity and professionalism are your allies here.