How long should a take-home assignment take to complete?
TL;DR: A well-scoped take-home should take 1-3 hours for most roles, capped at what the employer states upfront. If the "suggested" time is under 2 hours but the task realistically needs 10-15, that's a red flag worth naming to the recruiter before you start.
The short answer
There's no universal standard, but a strong norm has emerged across engineering, data, and writing roles: respect the stated time cap, don't over-invest trying to impress, and treat any assignment structured to secretly demand a full day of free labor as a signal about how that team will treat your time later.
The evidence
- r/technicalwriting: "A technical writing take home assignment shouldn't take more than an hour, two at most. Everything should be under an hour."
- r/cscareerquestions: consensus rule of thumb — "don't spend more time on the assignment than they've indicated, unless you have a good reason."
- r/managers: a hiring manager describes capping a take-home at "no more than 2 hours" as a matter of fairness policy.
- r/ExperiencedDevs: some candidates self-report take-homes stretching to 15 hours when the scope wasn't honestly communicated — a widely-cited example of what to watch for and push back on.
- r/recruiting: recruiters themselves debate whether to publish an estimated completion time on multi-part assessments, suggesting the practice is inconsistent across companies — so you often have to ask.
Fair vs. red-flag take-home assignments
| Signal | Fair take-home | Red flag |
|---|---|---|
| Stated time | Explicit cap (e.g., "2 hours max") | No time estimate given at all |
| Actual scope | Matches the stated time when done honestly | Realistically needs 3-5x the stated time |
| Deliverable | Single focused task, clear rubric | Multi-part project resembling real production work |
| Compensation | None expected for 1-3 hr tasks | No pay offered for 8+ hour deliverables |
| Follow-up | Debrief call to discuss your approach | Silence after submission, no feedback |
Step-by-step: handle a take-home fairly
- Ask for a time estimate upfront if none is given — this is a normal, expected question, not a red flag on your side.
- Time-box yourself to the stated cap; stop and submit what you have rather than spiraling into unpaid overtime.
- If the real scope clearly exceeds the stated estimate once you start, email the recruiter and ask whether to submit a partial solution or extend the deadline — don't silently absorb the extra hours.
- Prioritize the parts of the rubric you know will be scored (readability, correctness, tests) over polish nobody asked for.
- If a company asks for 8+ hours of unpaid work with no debrief or compensation offered, treat that as information about the role, not just the hiring process.
FAQ
Is it normal for take-home assignments to have no stated time limit? It happens, but it's increasingly seen as a poor practice — you're within your rights to ask the recruiter for an estimate before starting.
Should I spend extra time to stand out on a take-home? Marginal extra time on the actual rubric criteria helps; padding scope beyond what was asked rarely moves the needle and can look like poor time-management judgment.
What should I do if a take-home realistically needs way more time than stated? Flag it to the recruiter directly and ask how they'd like you to proceed — submitting a well-reasoned partial solution is usually better than silently working unpaid hours.
InterviewBoost.ai's mock interviews and Resume Copilot help you spend your prep time on rounds that actually predict outcomes — not open-ended take-homes with no time cap.
By Pinal Dave | Last updated: 2026-07-24
This page embeds FAQPage and HowTo structured data (JSON-LD) for answer engines.