A product designer is a few jobs under one coat

Most of my career has been at GotPhoto, a B2B SaaS platform with a B2B2C twist: photographers run their businesses on it, and parents buy school photos through it. Designed across the platform: dashboard, finance, account setup, activation surfaces. Saw the product mature from sales-led to growth-led and shipped for both phases.

Worked in an autonomous product trio on the growth team, designing, testing, and shipping activation work for the XS customer segment. Heavy on user research: interviews, AHA-moment definition, sub-persona work to understand what looked like one user group but wasn't. The work spanned signup funnels, onboarding tours, and the dashboard surfaces that connect them.

Worked end-to-end with a PM and an engineer in autonomous trios. The format where the trio owns scope, decisions, and outcomes together. Comfortable in workshops, design critiques, async with stakeholders, and pushing scope expansion when research surfaces a bigger problem than the brief named. The shape of the work I want to keep doing.

Spent two years on the GotPhoto Shop team, designing the photographer-facing storefront and the parent-facing checkout flow. Worked on the prepay shop system: handling checkout, billing, and the mechanics of getting money from end customer to photographer. Commerce surfaces are where small UX decisions become measurable revenue, which makes them satisfying to design.

Started in physical object and textile design at MOME (Moholy-Nagy University of Art and Design, Budapest) before moving into digital. Visual design and illustration are still the parts I enjoy most. I've contributed illustrations to shipped products and like working on art direction. On the systems side, I contributed to managing a complex multi-product design system and cared a lot about the structure underneath what users see.

Currently using AI tooling end-to-end on the rebuild of this site: Claude Code, Claude Design, Figma Make, AI image tools. The methodology and the build log are themselves a case study in what changes when AI is part of the workflow rather than a feature you bolt on at the end. Open to roles where this is part of the work.