Product Designer
I design technology that fits into life rather than interrupting it.
Designing products with precision — and a sense of wit.
Four years across SaaS, design systems, and user research. I design technology that fits into life rather than interrupting it — and I'll show you what I considered and cut, not just what shipped.
Architecture before ornament. Component libraries and token systems built to survive the six-month mark.
Interviews, usability testing, synthesis. Evidence over assertion. Opinions with their trade-offs attached.
Three engineering teams, founding design at an edtech startup. Figma to merged PR. Specs developers read.
[Opening]
Product designer.
Occasional artist.
Product · Systems · Research
Seattle — remote friendly
Selective — right team, right problem
“I design technology that fits into life rather than interrupting it. The phone stays in the other room.”
Product designer with four years of experience across SaaS, design systems, and user research. Founding designer at an edtech startup, shipping the core learning product with three engineering teams. Previously a UX research TA at the UW iSchool. Deeply engaged in the AI and product design community in Seattle.
Building Ambient Data, Gentle Data — a dashboard that renders data as generative artwork.
Selective — AI-forward teams onlyLiterature, baking, learning things, and wandering Seattle.
Four years designing products where the hardest part wasn't polish — it was figuring out what to build. As founding designer at an edtech startup, I inherited a blank Figma file and three engineers who'd been designing in code. I built the system first, then the product. When the startup didn't find the market, I took 2025 to be deliberate about what came next rather than jump at the first thing available.
Systems before surfaces. Specific before general. I'd rather write down one honest decision with its trade-offs than list ten capabilities without evidence. Before the iSchool, I learned to explain my reasoning out loud — it's still how I work through a problem. AI is increasingly part of that process: I attend every AI and product design event I can find in Seattle, and I'm actively building design workflows and practices around it.
End-to-end flows, prototyping in Framer, spec writing, shipping with engineers.
Component libraries, token architecture, documentation that developers actually read.
Interviews, usability testing, synthesis, journey mapping.
Figma, Framer, Principle, Webflow, Linear, Notion.
Actively developing AI-integrated design workflows. Regular at Seattle AI and product design events.
Since January 2026, building Ambient Data, Gentle Data — an app that turns your personal data into generative artwork on your TV. Sleep, weather, your schedule. Art that shifts with your day rather than demanding your attention. Selectively open — looking for teams working at the edge of AI and product design.
Four years. One SaaS startup from founding to "we didn't find the market." One research TA gig at the iSchool — about 30% teaching, 70% helping undergrads realize their hypothesis is wrong. 2025: deliberately not working while deciding what to actually do next.
Since January 2026, building Ambient Data, Gentle Data — a dashboard that looks like a painting and knows what kind of day you're having. I go to every AI and design event in Seattle not to network, but to actually learn what's changing. I think too much about why design systems fall apart six months after the person who built them leaves.
Reading. Baking. Learning things for no reason. Wandering.
Figma for flows. Framer when something needs to feel alive. Principle when a flat click-through won't cut it.
Atomic design is a great idea most teams implement in a way that makes everyone miserable. The trick is knowing when to stop abstracting.
The methodology matters less than how honest you are about what you found.
It's not a threat to good design thinking. It's a threat to designers who've been coasting on deliverables. I want to work on the products that are figuring out what the new practice actually looks like.
Building Ambient Data, Gentle Data. Selectively open — right team, right problem, ideally both involving AI.
Built from zero. Adopted by 3 engineering teams.
What happens when a blank Figma file is the entire design system?
Built from zero. Adopted by 3 engineering teams. Reduced design-to-dev handoff time by 40%.
What happens when a blank Figma file is the entire design system?
Built from zero. Adopted by 3 engineering teams. 40% faster handoff.
[Designer take: Phase 3]
Redesigned onboarding for 2,000+ learners. Reduced drop-off at step 3 by 28%.
Most onboarding flows are designed for the person who built them, not the person using them.
Redesigned onboarding for 2,000+ learners. Reduced drop-off at step 3 by 28%.
Most onboarding flows are designed for the person who built them, not the person using them.
Redesigned onboarding for 2,000+ learners. Drop-off at step 3 down 28%.
[Designer take: Phase 3]
[Outcome — Phase 2]
[Hook — Phase 2]
[Outcome — Phase 2]
[Hook — Phase 2]
[Outcome — Phase 2]
[Designer take: Phase 3]
[Showcase brief — one sentence, one image, one link — Phase 5]
[Full artist's statement + gallery — Phase 5]
[Technical deep-dive — how the generative system works — Phase 5]
[Process section — structured, opinionated — Phase 6]
[Process section — messy middle, honest — Phase 6]