Startup Hiring: Writing Take-Home Assignments Fairly
A good take-home assignment shows you how someone really works, and a bad one quietly drives away your best candidates. The difference is rarely the task itself. It is the time it takes, how clearly it is explained, how fairly it is scored and whether candidates hear back. This guide shows you how to write take-home assignments that respect people's time and still give you the signal you need to hire well.
Key takeaways
- Keep the task short and tied to the real job. A few focused hours beats a weekend project.
- Never use a take-home assignment to get free work you plan to use. Invent the scenario or use old, solved problems.
- Write the scoring rubric before you send the task, and score every submission against it.
- Offer alternatives and reasonable adjustments, and give every candidate a reply and some feedback.
Startups lean on take-home assignments because they are small, busy and nervous about a bad hire. That is understandable. But a candidate with a full-time job, children at home for the summer holidays or a few other interviews on the go has limited evenings. If your task feels like unpaid consulting, the strongest people often simply withdraw. The goal is a task that is fair, focused and quick to score.
A quick note: this article is general information, not legal advice. Hiring and anti-discrimination rules vary by country and state, so check with an employment lawyer or HR adviser if you are unsure about your process.
Decide whether you need a take-home at all
Before writing anything, ask what you are trying to learn that you cannot learn another way. A take-home assignment is useful when the job involves focused, independent work that is hard to see in a conversation: writing, analysis, design, code or planning.
It is less useful when:
- The candidate already has a public portfolio, writing samples or code that shows the same skill.
- The role is mostly about live collaboration, where a short paired session tells you more.
- You have not yet had a first conversation. Sending a task to everyone who applies wastes many people's time.
A good rule of thumb: only send a take-home to candidates who have passed at least one conversation and who you would genuinely consider hiring if the task goes well.
Offer a choice of formats
Some candidates would rather share past work, walk you through a portfolio piece or do a live exercise. Offering two or three routes to show the same skill is fairer and often gives you better signal, because people can show their best work in the format that suits them.
Design the task around the real job
The best take-home assignments look like a small slice of the actual role. If the job is writing customer emails, ask for a customer email. If it is building a data report, give a small dataset and a question. Avoid puzzles, trick questions and tests of trivia that nobody needs on the job.
- List the skills that matter. Pick three or four from the job description, such as clear writing, prioritization and technical quality.
- Write a realistic scenario. Invent a company, customer or dataset, or use an old problem you have already solved.
- Set the time box. Decide how long a strong candidate should need and design the task to fit it.
- Test it internally. Ask a team member who did not write it to complete it. If it takes them longer than the time box, cut it down.
- Write the rubric. Define what weak, good and excellent look like for each skill before anyone submits.
- Write the brief. Explain the scenario, the deliverable, the time box, the deadline and how it will be judged.
Common mistake
Asking candidates to solve a live problem from your backlog, such as redesigning your actual onboarding page or writing your real launch plan. Even if you never use the result, it looks like free work, and it damages your reputation. Always use invented scenarios or problems you have already solved and shipped.
Respect candidates' time
Time is the fairness issue candidates mention most. A task that "should take two hours" often takes four, because people want to do well. Design with that in mind.
- Keep it short. Aim for a task a strong candidate can finish in a few hours, and say so clearly.
- Make the time box real. Say "please stop at three hours and note what you would do next" and mean it. Score what they produced in that time.
- Give a flexible deadline. A week is kinder than 48 hours, especially in summer when many people are traveling or caring for children.
- Consider paying for longer tasks. If a task genuinely needs more than a few hours, many companies pay candidates for their time. If you pay, check how to handle the payment properly with your accountant.
- Send the task once. Do not add a second take-home later in the process. One focused task is enough.
Pro tip
Ask candidates to include a short note at the top: how long they spent, what assumptions they made and what they would do with more time. That note is often the most revealing part of the submission, and it rewards people who stop on time rather than those who can afford to spend a weekend.
Set AI tool rules that match the job
Candidates may use AI writing and coding assistants such as ChatGPT, Claude or Gemini. Decide your rule before you send the task. If your team uses these tools every day, it is fair to allow them and ask candidates to say how they used them. If you need to see unaided work, say so plainly and design a task where judgment matters more than volume. Whatever you choose, apply the same rule to everyone.
Write a clear brief and a scoring rubric
Ambiguity is unfair because it rewards people who guess what you secretly wanted. A clear brief tells candidates exactly what you are looking for.
Your brief should include:
- The scenario and any background data they need
- The deliverable and its format, such as a short document, a slide or a code repository
- The time box and the deadline
- The three or four things you will judge, in plain words
- Your rule on AI tools and outside resources
- Who to contact with questions and how quickly you will reply
- A line inviting candidates to ask for adjustments if they need them
A take-home rubric template
Copy this into a spreadsheet and fill it in before the first submission arrives. The criteria and scores below are made-up examples for a content marketing role.
| Criterion | 1: weak | 3: good | 5: excellent | Example score |
|---|---|---|---|---|
| Understanding of the reader | Generic, no clear audience | Clear audience, mostly relevant | Sharp audience insight shapes every choice | 4 |
| Clarity of writing | Hard to follow | Clear with minor issues | Concise, scannable and easy to act on | 3 |
| Prioritization and judgment | Tries to do everything | Sensible focus | Explains trade-offs and what was left out on purpose | 5 |
Ask two people to score each submission independently, then compare. Where scores differ by more than one point, talk it through and note why. This simple habit reduces bias and makes decisions easier to explain.
Common mistake
Rewarding polish over substance. A beautifully formatted submission from someone who spent a whole weekend can look better than a sharp, honest answer from someone who stuck to the time box. Score against the rubric and read the candidate's note about time spent.
Make the process fair and inclusive
Fairness is also about who can take part. A few practical steps widen your pool.
- Offer reasonable adjustments. Some candidates may need extra time, a different format or written instead of verbal instructions. Invite requests in the brief and handle them without fuss. Disability and equality laws in many countries require reasonable adjustments, so check the rules that apply to you.
- Avoid expensive tools. Do not require paid software candidates may not own. Offer free alternatives or temporary access.
- Remove names where you can. Ask someone outside the panel to strip names before scoring, if your team is big enough.
- Treat every candidate the same. Same task, same time box, same rubric, same feedback approach.
- Protect their work. State in the brief that you will not use their submission, and delete it after a set period in line with your privacy notice.
Hypothetical example
Imagine Priya, a founder hiring her first customer success lead. Her original task asked candidates to write a full onboarding program for her real product, with a 48-hour deadline. Three of her five finalists dropped out. She rewrites it: an invented software company, one frustrated customer email to answer and a one-page plan for the customer's first month, with a three-hour time box and a one-week deadline. All four finalists in the next round complete it, the submissions are easier to compare, and two candidates mention the fair task as a reason they accepted the next interview. (This scenario is made up for illustration.)
Close the loop with feedback
A candidate who spends three hours on your task deserves more than silence. Commit to replying to everyone, and to giving brief, specific feedback to anyone who submitted.
- Reply within the time you promised. State it in the brief, for example within five working days.
- Share two strengths and one area to grow. Tie them to the rubric, not to personal impressions.
- Discuss it in the next interview. If they move forward, ask them to walk you through their choices. You learn how they think and handle questions.
- Ask for feedback on the task. A short question about time and clarity helps you improve it for the next hire.
Your take-home assignment checklist
- Confirm a take-home is the best way to test this skill
- Send it only after a first conversation
- Use an invented scenario or an old, solved problem
- Set a short time box and test it internally
- Write the rubric before sending the task
- Include the AI tools rule, deadline, contact and adjustments in the brief
- Allow at least a week to submit
- Score with two people independently
- Reply to everyone and give brief feedback
Frequently asked questions
How long should a take-home assignment take?
Short enough that a strong candidate can finish it in a few focused hours. Test it internally, state the time box clearly and design the task so stopping on time still produces a useful submission.
Should we pay candidates for take-home assignments?
Many companies pay when a task needs more than a few hours, and it is a strong signal of respect. If you do, apply it to everyone at that stage and check with your accountant how to process the payment.
Can we stop candidates from using AI tools?
You can ask, but it is hard to enforce. It is usually better to decide a clear rule, ask candidates to explain how they used any tools and discuss their choices in a follow-up interview, where real understanding shows.
Is it fair to use a take-home for senior roles?
It can be, but senior candidates often have less free time and more existing work to show. Offer a choice, such as reviewing a past project or a live working session, and keep any task short and strategic.
Related reading
The bottom line
A fair take-home assignment is short, realistic, clearly briefed and scored against a rubric written in advance. It never asks for free work, it offers adjustments and alternatives, and every candidate hears back with something useful.
Take an hour this week to review your current tasks. Cut them down, write the rubric and add a promise to reply. Your next great hire will notice the difference before they ever meet the team.
