EPAM Systems (Poland)

As a Principal Product Designer and head of design for EPAM’s Warsaw office, I worked at two connected levels: leading the designers responsible for client work and designing complex product journeys myself. I helped teams frame ambiguous problems before they became feature briefs, then carried the direction into information architecture, interaction models, prototypes, and delivery with product and engineering partners.

Warsaw design leadership

A quality bar grounded in active product work

I led 12 designers across the Warsaw office. The role was not separate from delivery: the standards I set in critique came from the same constraints our teams faced on live enterprise products.

• Used critique to strengthen decisions, not only screens. Reviews focused on how another designer framed the problem, connected the full journey, and communicated behavior clearly enough for product and engineering partners to act on it.
• Helped teams find direction in incomplete briefs. I worked with designers to reconcile user needs, business priorities, and technical constraints before committing to a solution.
• Kept craft and implementation connected. I encouraged high-fidelity, implementation-oriented prototypes that showed interaction behavior and product logic, not just a polished happy path.

This made office leadership practical: designers received support on the work in front of them, while project teams gained clearer decisions and more consistent design-to-development handoffs.

Vhi.ie

Design system, headless CMS components, and adoption for public and authenticated services

For Vhi, I owned the design system and headless CMS components that supported the public website and authenticated client cabinet (maintained in both Figma and Sketch), and the onboarding that got teams onto that system. Insurance services had grown into fragmented interactions; a shared structure only held if design tools, CMS building blocks, and day-to-day delivery stayed aligned.

• Owned the shared design system. I maintained the component system for the public site and client cabinet in Figma and Sketch so teams could work from one coherent set of patterns.
• Designed the headless CMS components. The CMS assembled pages from those building blocks; I kept them aligned with the design system so designed and published UI stayed the same.
• Drove onboarding and adoption. I onboarded teams onto the system so reusable patterns became part of how work shipped, not a library that sat unused.

Across the account, my contribution was the system and adoption that let fragmented insurance journeys share a stronger structure across both surfaces, while giving designers in the Warsaw office a concrete standard for consistent, implementable delivery.