BYND

The Problem

Design assignments don’t end when you hit submit.

Designers spend hours completing hiring assignments, often with no idea whether their work was viewed, considered, or simply ignored. I wanted to understand what happened after that final “Submit” button.

25+

Design assignment posts explored

20+

Designers interacted with

2

Developers collaborated with

Research

I studied real assignment requirements and spoke with designers who had experienced the process firsthand.

The Pivot

From protection → visibility

My initial direction was to protect designers from having their assignments copied. After discussing the technical and legal constraints with developers, I realized that guaranteeing protection wasn’t realistic.

I pivoted the product toward something I could genuinely deliver: visibility into recruiter engagement.

The Product

Designed from 0→1

I designed the complete SaaS experience—from assignment submission to recruiter engagement, analytics, notifications, and subscriptions.

18+ User Journeys

One Design Decision

Turning “Was it viewed?” into useful insight

Dashboard → Assignment Status → Analytics

Rather than simply telling designers that an assignment was viewed, I designed an engagement layer showing views, viewing duration, first and last viewed dates, and engagement over time.

From idea to live product.

I worked closely with developers throughout implementation, iterating around technical constraints and feedback to launch BYND as a live product.

Research → Strategy → UX → UI → Development → Launch