A recruiter emails you after a good first call: "Before the final round, please complete a small test project. It should take about three hours." You want the job. You also remember a friend who did a "test" that turned out to be a real client deliverable, and never heard back. How do you say yes without being used?
Trial tasks are a normal part of remote hiring, and many are fair. Remote employers can't watch you work in an office, so they want evidence. The problem is not the test itself. It is tests with no limits, no feedback and no payment. This guide shows you how to tell the difference and how to negotiate scope or pay in plain words.
Why companies use trial tasks
A CV and an interview show how you talk about work. A task shows how you do it. For roles such as writing, design, development, customer support, bookkeeping and virtual assistance, a short exercise often predicts performance better than another interview.
That is a fair reason to ask. It stops being fair when the company is really collecting free labour. Your job is to work out which one you are dealing with before you spend hours.
Fair test or free work: a quick check
| Sign | Usually fair | Warning sign |
|---|---|---|
| Subject | A made-up or generic scenario | Their real product, real customers, real live content |
| Time | Stated limit, such as 1-3 hours | "Take as long as you need" or multiple days |
| Brief | Written, with clear criteria | Vague, changing, or only given by chat |
| Feedback | They promise a review or next step | No timeline, no reply to questions |
| Stage | Late, with a short list of candidates | First step, sent to everyone who applies |
| Ownership | You keep the work or it is clearly a sample | They ask for editable source files or full rights |
One warning sign is not a verdict. Two or three together mean you should push back or walk away. Also run the basic company checks in our guide on spotting a fake remote job offer, because fake employers love "test projects" that produce usable work.
Step 1: Ask five questions before you start
Reply in writing and keep the tone friendly. Ask:
- How many candidates are at this stage?
- How long should the task take, and is there a deadline?
- What will you be judging it on?
- Will the work be used by the company in any way?
- Will I get feedback, and when will I hear the decision?
A real hiring manager answers these easily. If the replies are evasive, you have learned something useful for free.
Step 2: Cap the scope yourself
If the brief is open-ended, set the limit. Write something like:
Thanks for the brief. To keep this to the three hours you mentioned, I'll deliver an outline and the first section rather than the full piece, plus a note on how I'd finish it. Does that work?
This shows judgment, which is often what they are testing. It also protects you from producing a complete deliverable that can be used without you.
Step 3: Ask for payment when it is reasonable
You are more likely to get paid for a task when it is longer than a few hours, tied to real company material, or at a stage where you are one of few candidates. Many companies have a budget for it, but they will only pay if you ask.
Try:
I'm happy to do a test. Since this is about six hours of work, do you pay for trial projects? If so, I'd charge my usual hourly rate. If not, could we shorten it to a one-hour version so I can show my approach?
Notice the structure: a clear request, then an alternative. You are offering a way forward, not an ultimatum. If they pay, agree the amount, currency and payment method before starting. Our post on asking a foreign employer about pay timing and currency covers the wording.
Worked example (hypothetical)
Imagine Ada, a customer support specialist in Lagos, applies to a software company. They send a task: write replies to 15 customer tickets and a help-centre article, "no rush."
Ada replies with her five questions. She learns there are three finalists, the tickets are fictional, and the company will review within a week. Good. But the help-centre article looks like real content for their site. She writes back: she will answer 8 tickets and submit an outline of the article, in about two hours. They agree, she delivers, and they give feedback in four days.
Compare Kemi in the same position, who receives a task to "rewrite our onboarding emails" with the actual customer database export attached and a 48-hour deadline. No limit, real data, no feedback promise. Kemi should decline politely or ask for payment. The numbers here are invented, but the pattern is common.
Step 4: Protect yourself on the deliverable
- Mark it as a sample. Add "Sample submission for hiring evaluation" to the document or file name.
- Deliver partial work for creative or strategic tasks. Share a finished piece, not every asset.
- Use PDFs or view-only links instead of editable source files where possible.
- Do not sign away rights for an unpaid test. If a form says they own everything you submit, ask them to remove it.
- Keep records. Save the brief, your questions and their answers, and your submission with dates.
Handling the task on weak power and data
A test is no time for a blackout to cost you the deadline. Start early, save work offline, and keep a backup connection ready. Our guide on power and internet backup for a remote desk helps. If a delay happens, tell them early and ask for a few extra hours rather than going silent.
Common mistakes
- Doing more than asked. Extra polish rarely wins; following the brief does.
- Accepting a test before a conversation. If nobody has spoken to you, a test is likely a filter at scale. Ask for a call first.
- Skipping the questions because you fear seeming difficult. Good employers read questions as professionalism.
- Doing the task for several "finalists" in a row with the same pattern: no feedback, vague outcomes. After two such cases, treat it as a pattern and decline.
- Sending files before checking who is asking. Confirm the email domain matches the company site.
When to say no
Decline if the task takes more than a day with no pay, uses a real client's material, comes from a company you can't verify, or the contact refuses to answer basic questions. A short, polite message is enough: "Thank you for the opportunity. I can't complete an unpaid project of this size, but I'd be glad to continue if a paid trial or a shorter exercise is possible."
Having a portfolio ready also lowers how many tests you need to take, because you can point to existing work as proof.
Frequently asked questions
Is it normal to be paid for a trial task?
It happens, especially for longer tasks, but it is not universal. Asking politely costs you little.
Can I charge for a test if they said it's unpaid?
You can propose it, but they may say no. Then decide whether the shorter version is worth it.
What if they use my work and reject me?
Keep your dated records and ask them in writing to stop using it. Legal options depend on the contract and country, so get advice from a qualified professional if the amount matters.
Do I need a contract for a paid trial?
A short written agreement by email covering scope, rate, payment date and ownership is enough for small tasks.
Your next step
Take the five questions above, save them as a template, and send them the next time a test lands in your inbox. Notice how the company responds before you write a single line.
Always apply through the employer's official website or verified channels. Genuine employers never ask applicants to pay for a job, training, or an interview.