Private freelancer search moment

Asked to do a free test project? Pause before you agree

Free test tasks often sound reasonable because the client frames them as a way to assess fit. The risk is that you give away strategy, concepts, code, or design work before any agreement exists.

What you are probably trying to decide

You want the opportunity, but the unpaid test request feels a little wrong.

What to watch before replying

  • Free tests can become disguised spec work
  • Paid trials are usually safer than unpaid samples
  • Portfolio links and a discovery call may be enough proof
  • If you do a test, limit scope and ownership in writing

Clarify this before committing

  • Is the task useful to the client even if they do not hire you?
  • Will the test be paid?
  • Who owns the concepts, code, or files created during the test?

Quick answers

Is a free test project always a red flag?

A free test project is not always a red flag. It becomes risky when the task creates usable client work, has unclear ownership, requires strategy or original concepts, or replaces a paid discovery process. A safe test should be limited, non-commercial, and clearly separate from work the client can use.

How should I respond to an unpaid test task?

Respond by offering proof without giving away usable work. You can share portfolio samples, suggest a short paid trial, or propose a tightly limited exercise that cannot be used commercially without payment. If they need real project work to assess fit, that is usually a paid discovery or pilot project.