You are three rounds deep into a contract search. A vendor recruiter just forwarded a 'quick technical exercise' from the client. It says four hours. You know it means ten.
Here is the uncomfortable truth: some take-home assignments are legitimate screens. Others are unpaid deliverables wearing a disguise. The skill that separates consultants who protect their time from those who burn a weekend for nothing is knowing which is which, fast.
This is not a call to refuse every assessment on principle. That advice is lazy and it will cost you real opportunities. What you need is a framework, and a script that lets you counter without sounding difficult.
Who asked matters more than what was asked
The source of the request tells you almost everything about its intent.
- Vendor or staffing recruiter: Often forwarding a generic client requirement without context. They may not know if the task is scoped reasonably. Push back here is low-risk because you are not yet talking to the decision-maker.
- Client technical lead or hiring manager: This person wrote or approved the assignment. They understand the scope and can modify it on the spot. A direct, respectful question to them carries more weight and gets a faster answer.
If a recruiter cannot tell you why the task was chosen, what it is meant to evaluate, or how long the client expects it to take, that is a signal the assignment was copy-pasted from a template with no thought given to a contractor's time. Ask the recruiter to loop in the technical lead before you commit.
Set a hard time cap before you open the instructions
Every legitimate take-home has an honest time estimate. Every dishonest one hides behind vague language like 'should only take a few hours.'
Before you write a line of code, ask directly: what is the maximum time you expect this to take, and is that a hard cap enforced by a timer, or a soft suggestion? If there is no cap, set your own. Two hours is reasonable for a mid-level contract screen. Four hours is the outer edge for anything more senior. If the task cannot be meaningfully attempted in that window, the problem is the assignment, not your skills.
Write your own cap into your calendar. When the timer runs out, stop, write a short note explaining what you would do next, and submit what you have. A thoughtful partial submission with clear reasoning often reads better than a rushed complete one.
Does it look like a deliverable, or does it look like a screen
This is the question that matters most, and the one candidates skip because they are in a hurry to impress.
A fair technical assessment tests a concept: a sorting problem, a small API integration, a data transformation with sample input and output. A deliverable disguised as an assessment asks you to build a feature that maps suspiciously well onto the client's actual product. Watch for these patterns:
- The task references the client's real domain, schema, or business logic in specific detail.
- You are asked to integrate with the client's actual repo, Figma file, or internal API.
- The brief includes production concerns like logging, error handling for edge cases specific to their system, or deployment instructions.
- Multiple candidates are rumored (or confirmed) to be solving the same real problem the team has not yet shipped.
None of those are automatically disqualifying on their own. Together, they are a pattern worth naming out loud to the client before you spend a weekend building something that ends up in their codebase for free.
Check your pipeline before you check your pride
The honest answer to 'should I do this' depends partly on how many other conversations you have running.
| Your pipeline state | How to weigh the ask |
|---|---|
| One active lead, rate and role are strong | Reasonable to invest the capped time if the task is scoped fairly. This might be the placement. |
| Multiple active leads, comparable rates | Lean toward the counter-offer script below. Your time is the scarce resource right now, not your proof of competence. |
| Dry pipeline, need to land something soon | Do the assessment if it is capped and reasonable, but still flag any deliverable-shaped scope in writing before you start. |
| Assignment has no cap and smells like real product work | Counter, regardless of pipeline state. This is the one category where declining or redirecting is almost always correct. |
The counter-offer script that works
You do not have to choose between 'yes, unlimited hours' and a flat 'no.' The middle path is a live, timeboxed pairing session, and most technical leads respect the ask because it is a better signal for them too. A 45-minute pairing session shows how you think under real conditions, which a solo take-home cannot replicate.
Here is language you can adapt and send to the recruiter or the technical lead directly:
'Thanks for sending this over. I am glad to demonstrate my approach to this kind of problem. Given the time constraints on my side right now, would the team be open to a 45-minute live pairing session instead, where I work through a similar but smaller version of the problem with someone from the team? I find that gives a clearer picture of how I communicate and debug in real time, and it respects everyone's schedule. Happy to prep anything useful beforehand.'
Notice what this script does. It does not say no. It offers something the client arguably prefers: a live read on communication, debugging, and reasoning under mild pressure, delivered in less total time than a take-home usually consumes once you count the writing and polishing. Most technical leads who have screened a hundred candidates already know take-homes are a blunt instrument. You are giving them an easier yes.
When to simply decline, no counter-offer needed
Some situations do not deserve a counter. Decline cleanly and move on when:
- The task has no stated time cap and the recruiter cannot get one from the client within a day.
- The scope explicitly asks you to solve a problem the client has stated they have not yet solved internally.
- You are asked to sign no agreement regarding ownership of the work product, and the client declines to clarify who owns what you submit.
- This is the third unpaid assignment in a row from the same vendor across different client logos, suggesting a pattern rather than a one-off.
A clean decline costs you nothing. A pipeline with ten leads and zero boundaries costs you every weekend between now and your next contract.
The one thing to remember
A take-home assignment interview is a tool, not a test of your worth. Used well, it is a fair, capped, concept-level screen. Used poorly, it is unpaid deliverable work with a deadline attached. Your job is to tell the difference in the first email exchange, not after you have already given up your Saturday.
If you are navigating a stack of client screens right now and want a second opinion on whether a specific assignment crosses the line, the Josh Pros LLC team is glad to talk it through. Email contact@joshpros.com or visit https://joshpros.com.
#TakeHomeAssignment #ContractInterview #TechContracting #ITConsulting #TechnicalScreen #ContractRoles #JobSearchTips #CodingTest #InterviewProcess #ConsultantLife #JoshPros #CareerAdvice
Talk to a real recruiter, not a bot.
We'll tell you the rate, the client, and the terms before you interview. And if we're not the right fit, we'll say so.