Measurable results

The numbers, with the story behind them.

Anyone can list stats. These are the results I'm proud of — across community, leadership, and product — each with the context, the approach, and what actually moved.

Talks given

Across 22 countries.

Yrs to JSNation Community of the Year

ZurichJS won Global Community of the Year (highest impact) at JSNation's OSS Awards, under two years after founding.

Release Time

88% faster releases (multi-day to same-day): stabilized E2E selectors to cut flakiness, parallelized unit tests, better feature-flag management, and QA gates across dev, staging, RC, and production.

0 %

New Indian Subs on UPI

On Smallpdf (tens of millions of monthly users), UPI carried ~83% of new Indian subscriptions within three months, reopening a market card-only checkout had closed.

Case studies

Three results, in depth

3.5 ×

Product

Revenue growth in APAC after launching Alipay

Local payment methods aren't a nice-to-have in Asia — they're the difference between converting and not. I led the frontend work to integrate Alipay and design a checkout that felt native to the region.

Context: Western-built checkout was underperforming in APAC; card-first flows didn't match local behavior.
Approach: Framework-agnostic payment orchestration, region-aware UX, and resilient fallbacks for flaky networks.
Result: 3.5× revenue uplift in the region after introducing Alipay as a local method.

425

Community

Growing ZurichJS into a thriving community

Community is where I get to lift people up at scale. As an organizer of ZurichJS, I focused on making it a place engineers actually want to come back to.

Context: A local meetup with potential but inconsistent momentum and turnout.
Approach: Consistent cadence, strong speakers, hands-on workshops, and a genuinely welcoming room.
Result: 425 new members added during 2025, with sold-out workshop days.

Leadership

Leading a cross-functional squad of 15

The best leadership keeps you close to the work. I led 15 engineers across frontend and backend — plus the skip-level management in between — without losing the plot technically.

Context: Two teams shipping a shared product surface, with coordination overhead slowing delivery.
Approach: Clear ownership, pragmatic architecture decisions, and mentoring engineers into more senior roles.
Result: Faster, more predictable delivery — and several engineers leveled up along the way.

Available · Q3 2026

Let's add your numbers to this page

Whether it's a payments problem, a performance ceiling, or a team that needs leveling up — let's talk.

Explore services Invite me to speak