I've always had an eye before I had a title for it.

In the early 2000s, I was selected for a city-funded arts project and helped build a DVD that premiered at the Bellevue Art Museum, recognized by the Mayor of Kent. I hadn't taken a single art class yet. That came that fall, at Green River through Running Start, in the same stretch of years I graduated from college one day before I graduated high school.

That instinct for making things, clear, considered, worth looking at, is the same instinct that, years later, would click into place the moment I sat in on a user research study at F5 Networks. I was working as a web developer at the time, watching someone struggle through a task I'd helped build. Something clicked. It wasn't just "this is broken." It was the realization that understanding why something is broken is its own discipline, and it was the one I actually wanted to practice.

But that clarity came after a fairly winding road to get there.

At 25, after leading an arts co-op with international artists in Taipei, I took a ferry to Xiamen in mainland China, then a two-day train ride to Shanghai, where I interned at a government-run art museum, translating materials in the education department and, at one point, leading a tour for expats. I applied to grad school from there. The applications were rejected, not for merit, but because my identity was stolen and the payments never went through. I moved back to the U.S. dejected, into a recession-era job market that meant years in customer service before I found my way into tech.

I started in development. It was there, building things, then later watching that research study at F5, that I realized art school not working out didn't mean design wasn't mine to have. I found my footing at the intersection of engineering, customer experience, and craft: not choosing between the analytical and the artistic, but building a career at the place where they overlap.

Ways of Working

I think of my background as three lenses:

The art lens— Composition, tension, emotional resonance. I notice when something feels off by two pixels, and I care about the details most people won't consciously register but will absolutely feel.

The empathy lens— Years in customer service taught me that users aren't edge cases to be handled; they're people having a bad day who just want something to work. I design for them first.

The engineering lens— My dev background means I think about constraints and implementation from the start, not as an afterthought. I discuss technical tradeoffs early, optimize for clean handoffs, and speak fluently with engineers about what's feasible and what's worth fighting for.

This means I bridge the gap between design and engineering—not by writing production code, but by designing with real-world constraints baked in from day one.

Career Highlights

  • Systems thinking and scalable design architecture
  • User research that actually informs decisions
  • Early constraint mapping and implementation-aware design
  • Visual craft and obsessive attention to detail
  • Accessible, cross-cultural design

Building

Doom Pile Destroyer, an AI chat companion app that helps people break down overwhelming clutter and task paralysis into manageable steps. I'm using it to stay hands-on with LLM integration, prompt design, and shipping a real product end-to-end.

It lives under BlueRose Imaginarium, my personal label for side projects. The name's a nod to Twin Peaks' impossible cases and Terry Gilliam's Imaginarium felt right for work that sits at the edge of practical and a little strange.

Rewatching

Twin Peaks, for the third (fourth?) time. Still noticing new details. Still unsettled by that ceiling fan. The owls are not what they seem.

Watching

Mr Ballen and The Why Files on YouTube. Strange-but-true stories and deep dives into the unexplained—the perfect wind-down after a day of making interfaces make sense.

Exploring

The trails around Capital Forest in Olympia. Nothing resets my brain like a few hours in the woods where the cell signal dies and the only decisions are "left fork or right fork."

Let's talk

I'm exploring senior product design roles, especially teams that value craft, collaboration, and a little bit of weirdness.

Based in the Pacific Northwest ✨