You made it through two rounds of interviews, and then the email arrives: a take-home assignment that looks a lot like a real project the team needs finished. They are calling it an assessment, but the scope is ten to fifteen hours of unpaid work, and nothing about the process guarantees you will get an offer.
Declining feels risky. You do not want to be the candidate who seems difficult or unwilling to put in effort. But there is a real difference between a fair technical assessment and a free work request dressed up as one, and you are allowed to say no to the second.
The key is how you decline. A blunt refusal closes the door. A carefully worded message either gets you a lighter version of the assignment or removes you from a process that was not going to treat you well anyway.
Below you will find how to tell the two situations apart, a comparison of the decline-first versus counter-offer approaches, and three email templates you can adapt to your own situation.
The core principle: Decline the scope, not the company. Keep the tone warm, be specific about what you would accept instead, and never accuse anyone of trying to exploit you.
Is This a Real Assessment or a Free Work Request?
Not every take-home challenge is a problem. A short, clearly bounded exercise with a defined time limit is a normal part of many hiring processes, and declining all of them will cost you opportunities.
The trouble starts when the assignment looks less like a test and more like a deliverable. These signals tell you which one you are dealing with.
- Scope creep. The task takes more than four hours and the instructions say something vague like "spend as much time as you need."
- Business relevance. The assignment asks you to solve a problem the company is currently facing, or to work with their real data, codebase, or design system.
- No time box. There is no stated limit, which means the person who does the most unpaid work wins.
- Repeated rounds. This is the second or third unpaid exercise you have been asked to complete.
- Production-ready expectations. The brief asks for deployment, documentation, tests, and a presentation for a role that already listed those skills on your resume.
- Vague next steps. There is no clear timeline for a decision, no name attached to the reviewer, and no explanation of how the work will be evaluated.
- Ownership language. The terms mention that the company will retain your submission or that it becomes their property.
If two or three of those boxes are checked, you are not being assessed. You are being asked to work for free, and the polite move is to say so with your time rather than your words.
Warning: If the assignment requires you to sign an agreement that transfers ownership of your work to the company, read it carefully before you start. Submitting unpaid work under a broad IP assignment clause can restrict what you can reuse in your own portfolio.
Decline Outright or Counter With an Alternative?
Once you have decided the assignment is too much, you have two options. Both are professional, and the right one depends on how much you actually want the job.
Option A: Decline outright. You send a short, warm message thanking them for the opportunity and withdrawing from the process. This is the cleanest approach when you are lukewarm on the role, already have other offers, or the process has shown multiple warning signs.
Option B: Counter with an alternative. You decline the specific assignment but offer something else: a live pairing session, a walkthrough of similar past work, a shorter version of the exercise, or a paid contract for the full scope. This is the stronger move when you genuinely want the job and want to test whether the company is reasonable.
Here is the honest trade-off. Option A protects your time and your standards but ends the conversation. Option B keeps you in the running and often reveals the company's real character, but it costs you one more email and sometimes one more call.
For senior candidates and anyone with a portfolio of public work, Option B is usually worth trying first. For early-career candidates who need the practice, a bounded two-hour exercise is often a reasonable investment. The line is not about your seniority. It is about whether the request is proportionate to the role.
Email Templates for Three Common Situations
Each template below keeps the tone warm while being clear about what you will and will not do. Replace every placeholder with your own details, and do not send any of these in anger.
Template One: Polite Decline With a Clear Reason
Best when you want to withdraw from the process entirely but leave the relationship intact for the future.
Subject line options:
- Thank you — withdrawing from the [Job Title] process
- Following up on the take-home assignment
- Updating you on my candidacy for [Job Title]
Hi [Recipient Name], Thank you for sending over the assignment and for the time your team has
already invested in my candidacy. After reviewing the brief, I am going to step back from the process. The
scope is larger than I can commit to alongside my current work, and I would
rather be upfront about that than submit something rushed. I have enjoyed our conversations and have a lot of respect for what
[Company Name] is building. If a shorter exercise or a live technical
conversation would work better on your side, I would be glad to explore
that instead. Either way, thank you again for the opportunity. Best,
[Your Name]Template Two: Firm and Direct Counter-Offer
Best when the assignment is clearly outsized and you want to test whether the company will negotiate in good faith.
Subject line options:
- Question about the scope of the take-home exercise
- Proposing an alternative to the take-home assignment
- Following up on the [Job Title] assignment
Hi [Recipient Name], Thank you for sending the assignment details. I want to be transparent
about where I stand. Based on the brief, this looks like roughly [number] hours of work,
including [specific requirements such as deployment, tests, or
documentation]. That is more than I can take on unpaid alongside my current
commitments. I am still very interested in the role, so here are two alternatives I would
happily do instead: 1. A live pairing session of about [number] hours where we work through a problem together.
2. A walkthrough of [similar project or system] that I have built, including the architecture decisions and trade-offs. If the full scope is essential to your evaluation process, I would also be
open to discussing it as a paid engagement. Let me know what works on your side and I will make time for it. Best,
[Your Name]Template Three: Short and Warm Decline
Best when you have already decided the company is not a fit and want to close the loop without further negotiation.
Subject line options:
- Thank you for the opportunity
- Withdrawing my application for [Job Title]
- Quick update on my candidacy
Hi [Recipient Name], Thank you for the assignment and for the conversations so far. I have
decided to withdraw from the process. The exercise is more involved than I am able to take on unpaid, and I did
not want to leave you waiting on a submission I could not deliver well. I appreciate the time you and your team spent with me and I wish you the
best in finding the right person for the role. Best,
[Your Name]Pro tip: Never send one of these templates within the first hour of receiving the assignment. Give yourself a night to check whether the frustration is about the scope or about something else in the process.
Tone Rules That Keep the Door Open
Everything in these emails comes down to wording. Two candidates can send the same decision, and one gets a warm reply while the other gets a polite dismissal.
- Attack the scope, never the motive. "This is more than I can take on unpaid" works. "This feels like you are asking for free work" does not.
- Use "I" statements. "I am not able to commit that time" is a boundary. "You are asking too much" is an accusation.
- Thank them for the time already spent. Recruiters and hiring managers have invested hours too, and acknowledging that softens everything that follows.
- Offer a concrete alternative. A specific suggestion reads as cooperation rather than rejection.
- Keep the message short. Three short paragraphs is plenty. Long explanations sound defensive.
- Do not over-apologize. One "thank you" is warm. Four apologies make you sound guilty of something.
- Leave the door visibly open. Even if you never speak to them again, the recruiter may move to another company and remember you.
- Skip the lecture about industry norms. You are not there to teach them how hiring should work. You are there to protect your time and your reputation.
What If They Push Back or Go Silent?
Their reaction tells you more than their job posting did. Handle each outcome differently.
If they respond warmly and offer a lighter exercise, take it. That is a company that listened, and it is worth giving them a real chance.
If they insist on the full scope with no flexibility, politely decline and move on. You have learned what working there would feel like when you ask for something reasonable.
If they go completely silent, do not chase them. Send one short follow-up after a few days restating your position, and then close the file. Silence after a reasonable request is an answer.
If they react badly, be grateful. A hostile response to a polite boundary is the clearest possible signal about the culture you would be joining.
In every case, keep your own records. Save the assignment brief and your emails so you have a clear picture if the same company reaches out again later.
Final Checklist Before You Hit Send
Run through this list once before the email goes out. It takes two minutes and prevents most of the regret that follows a rushed reply.
- Confirm the scope. Estimate the hours honestly rather than assuming the worst.
- Check for ownership clauses. Look for language about who retains the work you submit.
- Decide between declining and countering. Pick one and commit to it in the email.
- Write the first draft and wait. Read it again before sending, ideally the next morning.
- Remove every accusation. If a sentence implies bad intent, rewrite it as a statement about your own capacity.
- Add one concrete alternative. A live session, a portfolio walkthrough, or a shorter version.
- Keep it under 200 words. Anything longer starts to read as a negotiation you are not ready to have.
- Proofread for tone. Read it out loud. If it sounds cold in your own voice, it will sound colder in theirs.
- Save a copy. You may want to reference it if the same company follows up later.
Frequently Asked Questions
Q: Is it unprofessional to decline a take-home coding challenge?
A: No. Declining is a normal professional decision, especially when the assignment takes many unpaid hours or resembles real work the company needs done. What matters is how you decline. A short, warm message that thanks them for their time and explains your capacity is perfectly professional and often leaves the relationship intact.
Q: How do I know if a take-home assignment is actually free work?
A: Look for a scope over four hours, no stated time limit, use of the company's real data or codebase, production-level requirements, an ownership or IP transfer clause, or a request for a second unpaid exercise. If two or more of those are present, the assignment is functioning as unpaid work rather than a fair assessment.
Q: Should I offer to do a live coding session instead?
A: Yes, if you are genuinely interested in the role. A live pairing session gives the interviewer the same signal about your skills, costs you far less time, and shows you are willing to be evaluated. It also tests whether the company is flexible or insists on a process that only benefits them.
Q: What if the recruiter insists the full assignment is required?
A: You can still decline politely. Restate that the scope is more than you can take on unpaid, thank them for their time, and withdraw from the process. If they will not adjust a reasonable request at the interview stage, that pattern will likely continue after you are hired.
Q: Can declining a take-home assignment hurt my chances at other companies?
A: Rarely. Recruiters move between companies, but a calm, professional decline is not something they hold against candidates. What does follow you is a reputation for being difficult or for sending hostile emails. That is entirely a matter of tone, and tone is fully within your control.
Q: Should I ask to be paid for the take-home assignment?
A: It is reasonable to raise it, especially for senior roles or assignments that clearly mirror real deliverables. Frame it as an option rather than a demand, and keep your message brief. Some companies will agree, many will not, and either answer is useful information about how they value your time.