Test tasks: Should I stay or should I go?

Someone recently asked me to complete a test task before we could even discuss the project details or budget.

Unpaid, of course.

After 6+ years in the industry, working with global brands like Adobe, Google, Shake Shack, and dozens of others – my portfolio exists for exactly this reason. Anyone can see how I work, what I create, what the results look like, all without me spending hours on something speculative and free.

But here's where it gets interesting. This was a big, recognizable brand. The kind that would look impressive in a portfolio. So I almost said yes.

Almost.

Before agreeing, I asked one simple question: what's the budget for the actual project if the test goes well?

Their number? About 10 times lower than what I would normally charge for that scope and level of customization.

That's when I knew – this wasn't about vetting my skills. This was about getting free work from someone who might do it for "exposure."

No thanks!

Why clients ask for test tasks (and why I get it)

Clients want certainty. Completely fair.

They're about to invest money into creative work, and they want to know what they're getting. They want to see if we can handle their specific needs, work within their constraints, deliver on their vision.

I understand this. Hiring someone always carries risk, especially if they've never worked together before.

And honestly, in the age of AI, this concern has gotten more legitimate. Anyone can put together a portfolio now that looks impressive but might not actually be their work. It's easier than ever to take someone else's projects, present them as your own, or even generate convincing-looking work that doesn't reflect real capabilities.

So I get the skepticism.

But here's the thing – a test task isn't how they solve that problem either.

If they're worried about portfolio authenticity, they should look at testimonials. Check references. Review our public presence and online footprint. See if our work history adds up, if we have documented projects with real companies, if other people vouch for our work.

A free test task doesn't tell them if someone's portfolio is real. It just tells them if we're willing to work for free.

And asking an experienced professional with years of documented work, client testimonials, and a public track record for unpaid spec work isn't vetting – it's signaling that they don't value the expertise they're trying to hire.

Your portfolio IS the test

This is what I don't understand about test tasks for experienced creatives.

My portfolio shows real work for real clients with real results. It shows how I solve problems, how I adapt to different brand voices, how I work across different formats and industries. It shows years of delivered projects, happy clients, successful collaborations.

What exactly does a test task show that my portfolio doesn't?

If anything, a rushed unpaid test done in my "spare time" shows less about my actual capabilities than work I was properly briefed on, paid for, and given appropriate time to complete.

The portfolio is the test. That's literally what it's for.

When test tasks actually make sense

I'm not saying test tasks should never exist. There are situations where they make sense.

• If you're early in your career and don't have much client work to show yet – a test task can be an opportunity to prove yourself. You're building your portfolio, and sometimes that means doing work that isn't paid yet.

• If you're switching niches or trying to break into a new industry – a test might help demonstrate you can handle this specific type of work, even if your portfolio is strong in other areas.

• If the test is paid – then it's not really a "test," it's a small paid project. That's different. That's fair.

But if you have years of experience, a strong portfolio full of relevant work, and a client still asks for unpaid spec work? That's not a test. That's fishing for free labor.

Red flags that it's just free work

Here's how to spot when a "test task" is actually just them trying to get work done without paying for it:

The scope is suspiciously detailed and usable. If the test task looks like something they could actually implement and use in their business, that's not a test. That's a project.

They're vague about timeline and budget for the real work. Like in my case – they wanted free work upfront but couldn't commit to realistic compensation for the actual project.

They ask experienced professionals with strong portfolios. If my 6+ years and client roster isn't enough evidence of what I can do, a free test task won't change that. They either trust my work or they don't.

They don't offer to pay for it. Even a small payment shows they value your time and expertise. Free signals they don't.

Multiple rounds or revisions on the "test." One round, maybe. But if they're asking for changes and iterations on unpaid work, you're being used. I personally never include revisions in a test assignment, none at all.

What I said (and what you can say too)

When I was asked for that unpaid test task, here's how I responded:

"I appreciate the opportunity, but I don't do unpaid test tasks at this stage of my career. My portfolio demonstrates how I work and the results I deliver for clients. If you'd like to move forward, I'm happy to discuss the project scope and provide a quote. Alternatively, I can do a paid test project if that helps you feel more confident in moving forward."

They didn't take me up on either option. Which told me everything I needed to know about how they valued creative work.

And honestly? I'm glad I asked about budget before investing time. Imagine spending hours on a free test only to find out the actual project pays a fraction of what your work is worth.

If you decide to do it anyway

Sometimes you might choose to do a test task even when you know it's not ideal. Maybe you really need the work. Maybe the brand is so aligned with your goals that it's worth it. Or maybe you're genuinely excited about the opportunity.

If that's the case, at least negotiate the terms:

→ Set a time limit. "I can spend 2 hours on this, not more."
→ Clarify what happens to the work. "This test is for evaluation only and won't be used in any live projects."
→ Get the project details and budget in writing first. Don't do spec work without knowing if the real project is even worth pursuing.
→ Ask for feedback regardless of outcome. If you're giving free work, at least get something useful back.

But if you have the choice, and you have the experience – just say no. Your time is valuable!

What clients should do instead

If a client is genuinely concerned about vetting someone, here are better ways they could approach it:

→ Look at the portfolio closely. Not just pretty pictures, but case studies, process, results.
→ Have a detailed conversation. Talk through the project, ask how we'd approach it, discuss our process.
→ Check references. Talk to our past clients about working with us.
→ Start with a small paid project. Turn the "test" into an actual small engagement. Pay fairly for limited scope work.
→ Trust experience. If someone has years of work with reputable clients, that experience speaks for itself.

Long story short

Test tasks can exist. But they should be paid, especially for experienced professionals.

If our portfolio, experience, and client roster aren't enough evidence of our capabilities, a free test task won't magically create the trust that's missing.

Value expertise. Pay for work. Respect people's time.

And if you're asked to do free spec work? It's okay to walk away. Your experience and portfolio are enough. But, at the end of the day, it’s always up to you to decide anyway 🙂

Thank you for reading,