SR. PRODUCT DESIGNER · AMSTERDAM
Together we make what we imagine real.
I meet people with curiosity, align on what matters, design it, and build it with AI.
STUDIO
OpenOrbit
An independent product and UX studio for thoughtful digital products, useful tools, and experiments with AI.

Meso+
A resistance training app I founded and bootstrap, built end-to-end with AI: periodized plans, daily readiness check-ins, and training insights.

WORK
- Training Scheduling PortalA client-facing SaaS portal for scheduling workforce training programs.Sr. Product DesignerLepayaOct 2024 – May 2025

- Design System for Client Branding ThemesClients wanted the learning app in their own employer branding. The design system is what made it themeable.Product DesignerLepaya2023 – 2024

- Learning App + AI CoachAn in-app AI coach that helps learners set an intention before their training track — Lepaya's first.Product DesignerLepaya2023
- Speed InterviewsDesigning fairer access to work at scale.Product DesignerDaresay2017, 2018–2020iF Design Award winner

ABOUT
I’m from Vienna. Stockholm is where I became a designer: eight years there, five of them consulting through Daresay, embedded in client teams from public services to startups.
In summer 2021 I moved to Amsterdam and joined Lepaya, one of three UX designers in a company that grew from 80 to 300 people in a few years. In the learning app I worked on onboarding and learning completion. In the client portal I designed how companies plan and schedule their training.
I also prototyped and shipped Lepaya’s first AI coach — I wrote the prompts and context that shaped how it behaved, then tested it with learners and with learning scientists.
I also built Lepaya’s design system — Figma libraries, the code repositories we maintained with the dev team, and a Zeroheight reference the company worked from. Specifics are under NDA, but the work was as much organisational as visual: workshops with leads across tech, product, and learning to agree on purpose, scope, governance, and which platforms we’d commit to. I presented the initiative to the tech teams and company-wide, and kept making the case for adoption on stage and in any meeting where it served a shared goal. Where a surface couldn’t adopt the system fully, we built bridging templates rather than holding the line — consistency where it was reachable, honestly scoped where it wasn’t.
At Lepaya I started and co-led the accessibility guild. I have dyslexia, so I know what it costs when things aren’t built for how you read. Designing for access isn’t extra work on top of the real design. It usually just makes the design better.

WRITING

