Design Challenges: A Double-Edged Sword

Whiteboarding challenges? Good or bad? My own thoughts and personal experiences to let you decide.

Jun 15, 2025

|

2-3 min

Over the past year, I’ve come to really appreciate UX/UI design challenges—not just as part of the interview process, but as a way to prove myself. A design challenge is one of the rare opportunities where I get to show recruiters and professionals how I actually think, not just how my work looks in a polished portfolio. It's where the “what would you do?” becomes “watch me do it.” And for someone who’s trying to break into this competitive field, that space to act instead of just speak feels empowering.


That said, my feelings about them have grown complicated.

Recently, I participated in a design challenge for a small start-up company’s upcoming product feature. I already had my suspicions on their true intent, but being told there were few applicants and I was already a top contender clouded my head and judgment. I spent hours researching, studying their current product branding, wireframing, thinking through edge cases, and designing a thorough solution—one I was genuinely proud of. But after submitting, I heard nothing. It took two or three follow-up emails just to get a rejection. No feedback, no nothing, just empty promises of keeping me in mind for the future.

It was hard not to feel used. I poured my creativity and effort into helping improve their actual product direction—for free—and left with nothing but disappointment. These experiences can leave young designers like me questioning if our ideas are being valued, or just extracted.


But not all challenges are like that. A few months ago, I had the chance to participate in a live, in-person design challenge. I stood at a whiteboard, sketching my way through a problem in front of two designers from the company. It was nerve-wracking but incredibly rewarding. I got to explain my thought process in real time, ask questions, and iterate on the spot. That challenge felt collaborative, human, and fair. I passed, and while the role didn’t ultimately work out, I walked away proud—knowing it wasn’t my skills that fell short. I left with confidence, clarity, and a better understanding of what strong design thinking looks like in the real world.


So here’s where I land:

Design challenges can be amazing tools. They give designers a chance to prove themselves beyond a résumé or portfolio. But when companies treat them as free labor—soliciting unpaid work that directly contributes to product features, with little regard for the person behind the screen—it chips away at the excitement, hope, and goodwill that young designers bring to the table.

I’ll always love design challenges for what they can be: a moment to rise to the occasion. I just hope more companies start treating them with the respect and transparency that designers deserve.

— Emma

Over the past year, I’ve come to really appreciate UX/UI design challenges—not just as part of the interview process, but as a way to prove myself. A design challenge is one of the rare opportunities where I get to show recruiters and professionals how I actually think, not just how my work looks in a polished portfolio. It's where the “what would you do?” becomes “watch me do it.” And for someone who’s trying to break into this competitive field, that space to act instead of just speak feels empowering.


That said, my feelings about them have grown complicated.

Recently, I participated in a design challenge for a small start-up company’s upcoming product feature. I already had my suspicions on their true intent, but being told there were few applicants and I was already a top contender clouded my head and judgment. I spent hours researching, studying their current product branding, wireframing, thinking through edge cases, and designing a thorough solution—one I was genuinely proud of. But after submitting, I heard nothing. It took two or three follow-up emails just to get a rejection. No feedback, no nothing, just empty promises of keeping me in mind for the future.

It was hard not to feel used. I poured my creativity and effort into helping improve their actual product direction—for free—and left with nothing but disappointment. These experiences can leave young designers like me questioning if our ideas are being valued, or just extracted.


But not all challenges are like that. A few months ago, I had the chance to participate in a live, in-person design challenge. I stood at a whiteboard, sketching my way through a problem in front of two designers from the company. It was nerve-wracking but incredibly rewarding. I got to explain my thought process in real time, ask questions, and iterate on the spot. That challenge felt collaborative, human, and fair. I passed, and while the role didn’t ultimately work out, I walked away proud—knowing it wasn’t my skills that fell short. I left with confidence, clarity, and a better understanding of what strong design thinking looks like in the real world.


So here’s where I land:

Design challenges can be amazing tools. They give designers a chance to prove themselves beyond a résumé or portfolio. But when companies treat them as free labor—soliciting unpaid work that directly contributes to product features, with little regard for the person behind the screen—it chips away at the excitement, hope, and goodwill that young designers bring to the table.

I’ll always love design challenges for what they can be: a moment to rise to the occasion. I just hope more companies start treating them with the respect and transparency that designers deserve.

— Emma