Take-Home Assignments and Paid Trial Projects: How to Handle Them Well

If a remote employer has sent you a take-home task or offered a paid trial, this guide helps you decide whether it is reasonable and how to do it well. It covers the questions to ask before you start, how to present your work, and the signs that an assessment has turned into unpaid work.

Why remote employers use take-home tasks

For a distributed team, a practical task does two jobs at once. It shows your skills, and it shows how you work without someone looking over your shoulder: how you read a brief, manage your time and communicate in writing. Some companies use it instead of a live technical interview. Automattic, a distributed company, says on its careers pages that some roles use a practical test or a longer trial of real work in place of a traditional technical interview, and its trial guidance states that trials are paid at an hourly rate that is the same whatever role you apply for. Practices vary a lot between employers, so treat any single company's process as one example rather than the norm.

You are likely to meet one of these formats:

• Short skills test: a timed coding exercise, quiz or writing prompt, usually done in one sitting.
• Take-home assignment: a self-contained task completed in your own time, often over a few days.
• Paid trial project: a longer piece of work, sometimes inside the company's own tools, paid at an agreed rate.
• Live exercise: pairing or solving a problem together on a video call, which is closer to an interview than a take-home.

What reasonable scope looks like

There is no universal rule for how long a take-home should take. It depends on the role, its seniority and how far along you are in the process. These signals suggest a task is designed to assess you rather than to extract work:

• The brief states an expected time, and the task genuinely fits inside it.
• The task uses a simulated scenario, sample data or an exercise repository rather than the company's live product or a real client's project.
• You are told what reviewers will focus on, or at least what matters most.
• The deadline leaves room for someone who already has a job.
• Anything substantial is paid. Automattic's trial guidance, for example, describes a standard paid trial of about 25 to 40 hours for many roles, and its design hiring FAQ describes a paid trial project of about 8 to 12 hours in total, with a suggested limit of one week.

Regulators in some countries have also considered where the line falls. The UK government's minimum wage guidance says an unpaid trial of a few hours may be reasonable, but that a trial lasting more than one day is likely to entitle the person to at least the minimum wage in all but very exceptional circumstances. It lists factors such as whether the tasks have value to the employer beyond testing, whether they happen in a real or simulated environment, and whether the length goes beyond what is needed to test the person. Rules differ by country and depend on the facts, so treat this as an illustration of the principle, not as legal advice for your situation.

That guidance is about the UK minimum wage, so it does not settle what happens when you apply from India to a company based somewhere else. In practice you rely on the employer's own policy, which is one more reason to ask before you start whether a task is paid.

Ask clarifying questions before you start

In remote hiring, how you ask questions is part of what is being assessed. Automattic's trial guidance, for instance, encourages candidates to ask their trial lead questions and to flag delays and blockers promptly. A short, organised message early on is far better than silence followed by a late submission. Useful questions include:

1. How long do you expect this to take, and is there a hard time limit?
2. What is the deadline, and can it move if I tell you in advance?
3. What will reviewers focus on: correctness, code quality, design reasoning, writing quality or something else?
4. Where the brief is open, may I make assumptions as long as I document them?
5. Which tools and languages are acceptable, and what is your policy on AI-assisted tools?
6. Is this task paid? If so, what is the rate, how should I track my time and how will payment be made?
7. How will my submission be used, and who will see it?

For a paid trial, get the key terms in writing before you begin: the rate, the expected hours, how to record time, the payment method and the currency. If the payment will come from abroad, for example against a one-off invoice, our guide to working remotely for foreign companies from India explains how foreign payments reach an Indian bank account, how purpose codes work and which remittance documents to keep.

Red flags: when an assignment is really free work or a scam

Most take-home tasks are genuine. Be cautious when you see any of the following:

• The unpaid task is a real piece of the company's work: articles they plan to publish, a design for their live site, a fix for their production code or replies to real customer tickets.
• The scope keeps growing after you submit, with request after request for one more revision.
• A large task arrives before you have spoken to anyone or seen a clear job description.
• You are asked to log into production systems or handle real customer data while still a candidate.
• You are asked to pay for anything: training, software, a starter kit or a refundable deposit. The US Federal Trade Commission says honest employers will never ask you to pay to get a job.
• You are asked to deposit a cheque and send part of the money back, or to receive packages and reship them to another address. The FTC describes both as common job scam patterns.
• The work consists of simple tasks such as rating products or liking videos, with small early payouts followed by a request to deposit your own money to unlock earnings. The FTC calls these task scams.

If a request feels like free production work, you can decline politely or propose an alternative: a shorter version of the task, an existing sample that shows the same skill, or a paid arrangement. A genuine employer will usually respond reasonably. One that refuses any discussion has told you something useful about what working there might be like.

Presenting your submission

Reviewers often look at submissions in between other work, so make yours easy to understand in a few minutes. A clear structure helps:

1. Start with a short summary: what you built or wrote, what is complete and what is not.
2. Give instructions to run, view or test the work, and check that they work from scratch.
3. List the assumptions you made and the trade-offs you chose.
4. Note what you would improve or add with more time.
5. State honestly how long you spent. Going far over the suggested time is not always seen as a positive.
6. Use the format and channel they asked for, and reread the brief once more before you send.

For code, a tidy repository with a README and a few meaningful tests is usually more convincing than extra features. For design work, a short written walkthrough of your reasoning helps reviewers who were not in the room. For writing tasks, add a brief cover note on the audience and approach you assumed. Keep your own copy of everything you submit, along with the original brief and any messages about it.

If you hear nothing back

Silence after a take-home is frustrating and common. It more often means a slow process, a paused role or a decision made elsewhere than a verdict on your work. A calm plan helps:

1. When you submit, confirm the timeline they gave you or ask when you can expect to hear back.
2. If that date passes, send one short, polite follow-up a few working days later, allowing for time zones and public holidays in their country.
3. If there is still no reply after another week or so, send a brief final note thanking them, then move on.
4. Keep applying elsewhere throughout. Never pause your search for a single assignment.

If you later discover that an unpaid assignment has been used without your agreement, for example published as an article or shipped as a live design, save copies of the brief, your submission and the correspondence, and raise it with the company in writing. If the role was advertised on a job board, that board may have a way to report it. What else you can do depends on local law, so consider speaking to a qualified professional if the matter is significant.