Senior Product designer

Overview

I joined qlub in January 2025 as a Senior Product Designer, stepping into a fast-moving environment where designers were trusted to own their work and collaborate closely across product areas.

My main responsibility was the Vendor Panel, qlub's merchant-facing platform, with a second major stream in the customer app. Alongside those, I supported the QSR app and led work on the Vendor Panel design system.

Vendor Panel

The Vendor Panel was my primary ownership area. It is the platform merchants use to run their business on qlub, and my work centered on merchant-facing workflows: making day-to-day operations clearer, easier to use, and better structured as the platform continued to grow.

The focus was usability, structure, clarity, and scale. Across a product used in 30+ countries, this was product thinking for a growing platform — understanding how merchants actually operate and what the interface needs to carry — not just interface design.

Vendor Panel design system

Alongside product work, I led the Vendor Panel design system. The goal was a more consistent, reusable foundation: fewer one-off decisions, faster product delivery, and less design inconsistency accumulating over time.

This was a systems-thinking contribution as much as a design one — it reduced repeated cleanup, standardized component behavior, and created a stronger foundation for the product to scale on.

Customer app · Gift Cards

The customer app was the other major part of my contribution — customer-facing flows and experience improvements, focused on making interactions simpler, clearer, and easier to complete.

One of my main feature contributions was Gift Cards. I worked on the gift card buying flow and the gift card redemption flow, helping shape an experience that felt lightweight, intuitive, and practical.

How we worked

This was not a heavy upfront research project. The team moved quickly, so the process leaned on fast, collaborative loops instead of long discovery.

• Early flow design to frame the journey before high-fidelity work
• Brainstorming sessions to explore directions quickly
• UX review sessions to pressure-test decisions
• Close collaboration with PMs, product owners, and developers
• Iterative refinement before and after launch

Live usability signals with Microsoft Clarity

We used Microsoft Clarity as a usability testing and monitoring tool as part of our regular product workflow. Reviewing Clarity became part of the day-to-day process — it showed how users actually behaved inside the application, where friction appeared, where journeys dropped off, and which areas needed UX improvement.

That continuous monitoring helped us spot pain points in live flows. One example was the split journey, where Clarity revealed usability issues that were then refined through iteration. Instead of relying only on upfront discovery, we used live behavior, usability signals, and continuous tuning to improve the experience over time.

QSR app

I also contributed to the QSR app as part of the wider product workload. It was not my primary ownership area, but it reflected what the role required: the flexibility to work across multiple product surfaces at the same time without losing quality on any of them.

Team & working style

The design team was four designers and one design lead, with a fairly flat working model. Everyone owned their streams, moved quickly, and worked closely with product and engineering. Decisions were made fast, responsibility sat with the individual, and the environment rewarded practical, clear thinking over process for its own sake.