Blog/How to Design a Fair Take-Home Assignment for Freshers

How to Design a Fair Take-Home Assignment for Freshers

Rules, a step-by-step design process and an example rubric for take-home assignments when hiring freshers in India, including pay and AI-use policy.

Last updated: 23 October 2026 · By the Asuraa Team

Quick answer: To design a fair take-home assignment for freshers, keep it to about two to three hours of stated effort, base it on one slice of the real job, share a written rubric, state an AI-use policy, and review it in a short walkthrough call. Wellfound's hiring guidance suggests paying for or shortening any project over about four hours, because longer tasks lose candidates.

Key takeaways

  • A fair fresher take-home states expected effort up front, usually two to three hours, and asks candidates to stop at the cap and note what they would do next.
  • Wellfound's hiring guidance says projects longer than about four hours should be paid or shortened, because longer tasks reduce completion.
  • Holloway reports that about 20% of Dropbox candidates did not complete take-homes before the company dropped them, and effort on one task can range from 2 to 40 hours.
  • A rubric of four or five weighted, observable criteria shared in the brief keeps reviewers consistent and tells candidates what matters.
  • A 20 to 30 minute walkthrough call confirms authorship and reasoning more reliably than trying to detect outside help or AI use.

A fair take-home assignment for freshers is short (two to three hours of real effort, stated up front), mirrors one slice of the actual job, comes with a written rubric shared with the candidate, has an explicit AI-use policy, and is followed by a short call where the candidate walks you through their work. Anything that would take a working engineer a full day is too big, and anything long enough to look like free work should be paid or cut down.

What makes a take-home assignment fair for freshers?

A take-home is fair when every candidate gets the same task, the same time expectation, the same evaluation criteria and the same rules on outside help. Freshers are especially sensitive to unfair take-homes: many are juggling final-year exams, several applications at once and, often, limited laptop or internet access at home.

The evidence on candidate behaviour is consistent. Wellfound's engineering hiring guidance warns that the longer a project takes, the less likely candidates are to finish it, and suggests that anything over about four hours should be paid or shortened (Wellfound). Holloway's technical recruiting guide reports that before Dropbox dropped take-homes, about 20% of candidates did not complete them, and notes that effort on the same task can range from 2 hours to 40 without a clear cap (Holloway).

What rules should a take-home assignment follow?

Set these rules before you send the first assignment, and put them in the brief itself.

RuleRecommended practice for fresher rolesWhy
Time capState expected effort (for example "about 2 to 3 hours") and ask candidates to stop at the cap and list what they would do nextUncapped tasks reward whoever has the most free time, not the most skill
Completion windowGive 3 to 5 calendar days, including a weekend, and avoid exam weeks for campus hiresEffort is small, but freshers need flexibility
ScopeOne slice of real work: fix a bug, add one feature, clean and analyse one dataset, write one short proposalMirrors the job; easy to compare
Starter materialProvide boilerplate, sample data and setup steps that work in minutesSetup time is unpaid time that measures nothing
RubricShare 4 to 5 criteria and weights in the briefCandidates focus on what you value
Paid vs unpaidUnpaid only if short; pay a fixed amount if it goes beyond about four hoursAvoids the task looking like free work
AI-use policyState clearly: banned, allowed, or allowed with disclosureRemoves guesswork and unfairness
OwnershipSay the work is for evaluation only and will not be used in productionAddresses a common candidate worry
ReviewA 20 to 30 minute walkthrough call for shortlisted candidatesConfirms authorship and shows reasoning
FeedbackTwo or three lines of written feedback, even for rejectionsRespects the time invested

Several of these come straight from published practice. Wellfound describes TuneIn asking candidates to carve out two hours and stop there, and Frame.io setting a four-hour stop with a short write-up of what the candidate would add next (Wellfound). Holloway recommends telling candidates exactly what you are evaluating and making clear the work is only for evaluation (Holloway). SHRM lists candidate worry that employers will use their work without hiring them as a real downside of take-home tasks (SHRM).

How do you design a take-home assignment step by step?

Design it backwards from the job, then test it on your own team. A practical sequence:

  1. List two or three things a new joiner does in month one. For a backend fresher that might be "add an endpoint, write tests, fix a bug in existing code".
  2. Pick one of them as the task. Keep it to a few clearly defined requirements. Wellfound cautions that vague briefs push candidates to overdeliver.
  3. Write the brief. Include context, exact requirements, the time expectation, the rubric, the AI policy, how to submit (GitHub link or zip) and the deadline.
  4. Build the starter kit. A repository that runs with one command, or a clean CSV with a data dictionary.
  5. Pilot it. Ask a junior team member to do it under the cap. If they cannot finish in the stated time, cut scope.
  6. Write the rubric and two sample answers (one that meets the bar, one that does not) so reviewers calibrate.
  7. Plan the walkthrough call. Prepare three or four standard questions: why this approach, what you would change with more time, what shortcut you took and why. Holloway suggests exactly these kinds of follow-ups.

Where it fits in the funnel matters too. Holloway's guide notes take-homes work better later in the process, not as a first screen, because the time cost makes strong candidates drop out. For freshers, send it after a short online test or a phone screen, and before the final structured interview.

What does a good take-home rubric look like?

A good rubric has four or five criteria with weights, written as observable outcomes, and is shared with the candidate. Example rubric for a fresher backend task:

CriterionWeightMeets the bar when...
Correctness30%Required features work for the given inputs and edge cases listed in the brief
Code clarity25%Readable names, small functions, no dead code; a reviewer can follow it without the author
Testing20%Meaningful tests for the main path and at least one edge case
Communication15%README explains setup, decisions and what they would do next
Walkthrough10%Can explain choices and modify one part live

Score each criterion separately before reading other reviewers' scores. Do not award points for extras outside the brief; Wellfound notes that Frame.io asks candidates to describe additional ideas rather than build them, which keeps comparisons fair.

Should take-home assignments be paid?

Short take-homes for freshers can reasonably be unpaid; longer ones should be paid or shortened. Wellfound's guidance puts the line at roughly four hours (Wellfound). Holloway notes that payment offsets the candidate's time cost but does not always change completion rates, and that candidates can misreport hours either way (Holloway).

A practical Indian approach: keep the assignment under three hours and unpaid, or, if the role genuinely needs a longer project (say, a design or data role), pay a fixed fee per completed submission and say so in the brief. A fixed fee avoids arguments about hours.

What should your AI-use policy say in a take-home?

Your policy should state plainly whether AI tools are banned, allowed, or allowed with disclosure, and the task should be designed to match that choice. Published policies differ: Anthropic's candidate guidance, as reported by Fortune in July 2025, allows its AI assistant on take-home assessments only when the instructions permit it (Fortune), while Canva's engineering team announced in June 2025 that it expects candidates to use AI coding tools in technical interviews and redesigned its problems to be more ambiguous and realistic (Canva).

For an unsupervised take-home, a ban is very hard to enforce. "Allowed with disclosure" usually works best for freshers: ask them to note where they used AI and why, then probe those parts in the walkthrough. Our guide on handling ChatGPT use in hiring tests compares the options in detail.

What do most guides on take-home assignments get wrong?

Most guides focus on making the task harder to cheat, when the bigger risk for fresher hiring is losing good candidates to the time cost. A strong final-year student with three take-homes due in exam week will finish the shortest, clearest one. Holloway's account of Dropbox's experience is a useful warning: about 20% non-completion, with less competitive candidates completing more often (Holloway).

The second mistake is treating the submission as the result. SHRM points out that with take-home tests it is hard to know whether candidates worked alone (SHRM). The walkthrough call solves this better than any detection tool: someone who cannot explain or change their own code in 20 minutes did not really write it.

For the rest of your fresher funnel, see the employer guide to hiring freshers in India and our guide on how startups can hire developers.

Related guides

FAQ

How long should a take-home assignment for freshers be?

Aim for about two to three hours of real effort, stated clearly in the brief, with a completion window of a few days. Wellfound's hiring guidance warns that longer projects are less likely to be completed and suggests paying for or shortening anything over about four hours. Pilot the task on a junior colleague to check it fits the stated time.

Should companies pay candidates for take-home assignments?

Short take-homes for freshers can reasonably be unpaid. If a task genuinely needs more than about four hours, Wellfound's guidance is to pay or shorten it. Holloway notes payment offsets candidates' time but does not always change completion rates. A fixed fee per completed submission, stated in the brief, is simpler than paying by the hour.

What should a take-home assignment rubric include?

Four or five weighted criteria written as observable outcomes, such as correctness, code clarity, testing, written communication and the walkthrough discussion. Share the rubric in the brief so candidates know what you value, prepare one example that meets the bar and one that does not, and have each reviewer score independently before comparing.

Can candidates use ChatGPT in a take-home assignment?

That depends on your stated policy, and you should state one. Anthropic, as reported by Fortune in July 2025, allows AI on take-homes only where instructions permit it, while Canva expects candidates to use AI tools in technical interviews. For unsupervised take-homes, allowing AI with disclosure and probing the work in a walkthrough call is usually the most practical choice.

How do you know a candidate did the take-home themselves?

Hold a 20 to 30 minute walkthrough call. Ask why they chose their approach, what they would change with more time, which shortcuts they took and why, and ask them to modify one small part live. SHRM notes that it is hard to know whether take-home tests were completed alone, and a walkthrough addresses that directly.

When should a take-home assignment come in the hiring process?

After an initial filter and before the final interview. Holloway's technical recruiting guide notes take-homes work better later in the funnel, because the time cost makes strong candidates drop out if used as a first screen. For freshers, a short online test or phone screen first, then the take-home, then a structured interview is a sensible order.

Final thoughts

The best take-home for a fresher is small, realistic and transparent: a stated time cap, a shared rubric, a clear AI rule and a walkthrough call. That combination gives you a strong signal while respecting candidates' time. Once your assessment is ready, you can post the role on Asuraa Jobs.

Related articles

Share this article

Continue Reading

Data Science Career Paths

Explore different career trajectories in data science and find your perfect fit.

Read article →

Building Your DS Portfolio

Learn how to create projects that impress hiring managers and showcase your skills.

Read article →

Salary Negotiation Guide

Get the compensation you deserve with our proven negotiation strategies.

Review Your Resume →