Before I go further... I'm not talking about self-directed design challenges. Daily UI, Sharpen.design, community briefs, these are fantastic tools for skill development, and I'd recommend them to any designer at any stage of their career. What I'm talking about is something different: the design challenge as a hiring requirement, where companies ask candidates to produce unpaid work as part of a job application process.

‍

The Unpaid Trial Shift Never Died. It Just Got a Rebrand

When I was studying graphic design at university in the late 1980s and early 1990s, I did what virtually every student did to pay the bills: I worked in hospitality.

And if you worked in hospitality back then, you know what a trial shift was. You'd show up, work a full service, sometimes four or five hours, clearing tables, making coffee, running food, and keeping up with the Saturday night rush. You'd do the whole job. And at the end of the night, the owner would shake your hand and say they'd be in touch. No pay. No guarantee. Sometimes, not even a thank you.

It was rampant. Cafés, restaurants, bars, nightclubs, the trial shift was industry standard. You needed the job, they knew you needed the job, and the power imbalance did the rest. It wasn't until years later that the practice was widely called out for what it was: unpaid labour dressed up as an audition. The laws changed. The culture shifted. We decided, collectively, that asking people to work for free, even people who desperately needed the work, was not acceptable.

I'm a Senior UX/UI Designer now, with 20+ years of experience. I have a portfolio website. I have case studies. I have documented outcomes, conversion metrics, and a career's worth of shipped work that anyone can look at, right now, for free, at any time of day.

And yet here we are in 2026, and the design industry has quietly invented its own version of the trial shift. We call it the Design Challenge.

What a Design Challenge Actually Asks of You

Let me be specific, because I think the industry has gotten very comfortable with vague language that obscures what's actually being requested.

A design challenge typically asks a candidate, who is either unemployed and anxious, or employed and exhausted, to spend anywhere from a few hours to several days solving a real business problem for a company they don't yet work for. The work is unpaid. The brief is usually real. The outcomes sometimes end up in product roadmaps. And the candidate receives nothing except the possibility of progressing to the next round.

The briefs vary in scope and ambition, but the pattern is consistent. You might be asked to redesign a specific user flow, propose a solution to a known product problem, or conduct and present UX research on a target audience. Some challenges come with a time estimate — "this should take around two to four hours" — that bears no resemblance to what the work actually requires to do properly. Others are open-ended enough that a conscientious candidate could spend an entire working week on them without feeling finished.

What they all have in common is this: the thinking is yours, the time is yours, the expertise is yours — and the compensation is zero.

I want to be clear: I understand why companies do this. Portfolios can be polished to the point of fiction. Slide decks can hide weak thinking. Seeing how someone approaches a problem in real time has genuine value. I get it.

But there is a meaningful difference between assessing how someone thinks and extracting unpaid work from people who are financially vulnerable and time-poor. And I think the design industry needs to be more honest about which side of that line many design challenges fall on. The fact that it has become standard practice does not make it fair. The trial shift was standard practice once too.

The Hospitality Parallel Is Not a Stretch

The trial shift was defended the same way. "We just need to see how you work in a real environment." "It's only a few hours." "Everyone does it." "If you're serious about the job, you won't mind."

Sound familiar?

The power dynamic is identical. The candidate needs the job. The company holds the offer. And somewhere in that gap, hours of skilled, professional work happen for free.

The difference is that a hospitality trial shift asks for your physical labour. A design challenge asks for your intellectual labour, your professional expertise, and sometimes your most creative thinking — the very thing you've spent years and significant money developing.

And unlike a trial shift, the work product from a design challenge is portable. It can inform thinking. It can end up in a Confluence doc. It can seed a roadmap conversation that happens long after your application was declined.

"But We Have a Portfolio"

This is the part that genuinely frustrates me.

If a candidate has a portfolio website with documented case studies, published outcomes, and real shipped work, what exactly is the design challenge adding? What question does it answer that the portfolio does not?

I have case studies showing a 97.9% reduction in trade account approval processing times. I have documented conversion rate lifts across multiple states and sectors. I have an automated design system that was one of the first of its kind in Figma, integrated with GitHub, Storybook, and Chromatic. I have AI product work that went to a corporate board for approval and came back greenlit.

What will a three-day unpaid exercise on a fictional brief tell you that those outcomes don't?

The honest answer, in most cases, is: nothing. The design challenge isn't filling an information gap. It's a habit. An industry norm that nobody has stopped to question because it benefits the company, and the cost is borne entirely by the candidate.

What Good Hiring Looks Like

I want to be fair here, because not all design challenges are created equal. And I want to speak to this not just as a candidate, but as someone who has been on the other side of the hiring table.

During my career I have been directly responsible for hiring UX/UI and Product Designers. Not one of them came with a design challenge. Every hire was made on the basis of a portfolio walkthrough, a conversation about their thinking, and their ability to articulate the decisions behind their work, why they made the choices they made, what they tried first, what didn't work and why. That was enough. More than enough, as it turned out. Every designer I hired stayed for over three years. One went on to become a Principal Designer at a global tech company. Another is now Head of UX at a consultancy. A third became Lead UX/UI Designer at one of Australia's largest retailers.

I didn't need a free proof of concept to know they would shine. I needed to understand how they thought.

I also spent two years mentoring emerging designers at a design education program, helping them build their online portfolios and structure their case studies so prospective employers could make confident, informed decisions about their fit for a role. What I taught them, and what I saw work, repeatedly, was this: show your thinking, not just your outcomes. Document your process. Explain your decisions. Make it easy for a hiring manager to see how your mind works.

That is what a portfolio is for. That is what a structured interview is for. And when those two things are done well, they give a hiring manager everything they need to make a confident decision.

The model I have respect for is simple: ask the candidate to walk you through smething they have already built. Push on it. Ask hard questions. Understand the tradeoffs they made and why. It costs both parties nothing but time in a conversation, which is fair, because the cost is equal.

If you genuinely need to see original work on your specific problem, pay for it. A few hundred dollars for a senior designer's day is not a meaningful cost against the cost of a bad hire. Paid design challenges exist, and they are a reasonable middle ground. Unpaid ones, dressed up as standard practice, are not.

A portfolio is a living document of real, delivered work. For a senior designer, it represents years of craft, client relationships, NDAs navigated, and outcomes earned. If that isn't enough to get me in the room, I'd gently suggest the problem isn't my portfolio.

A Note to the Hiring Managers Reading This

I'm actively job searching right now. I'm applying for roles across Melbourne and beyond. I'm good at what I do, and I have the receipts to prove it.

I will complete a design challenge for a role I genuinely want, if the process is respectful of my time and the brief is genuinely about understanding my thinking rather than extracting my expertise. I'm not precious about it.

But I wanted to write this because I think the industry deserves a more honest conversation about what we're normalising. We spent years calling out the hospitality trial shift for what it was. We updated the laws. We decided that skilled labour — even from people who desperately need work - has value and deserves compensation.

The design industry is having a slower version of that same reckoning. I hope it speeds up.

Because the student who spent her Friday nights making cocktails for free in 1990, hoping to be called back, grew up to be the designer you're trying to hire in 2026.

And she remembers exactly how that felt.