$ show --impact --interactive

Loading explorer...

Measurable Results

Impact by the Numbers

Real results from community building, engineering leadership, and public speaking. Every number backed by data.

Outcomes= what changed

How= approach

Proof= evidence

Click any metric, then switch views

👥

Community

3 metrics

Expanded the top of the funnel for the community

Added 425 new members in a single year, which increased reach for events, improved speaker turnout, and made sponsorship and venue partnerships easier to secure. More importantly, it increased the number of newcomers who had a low-friction way to meet peers in Zurich.

A meetup only works if it stays welcoming and discoverable. In 2025, ZurichJS brought in 425 new members, which sounds like a simple growth stat, but it changed the dynamics of the group. A larger, healthier top of funnel meant better turnout consistency and better topic diversity, plus it made the community more resilient when schedules get busy or seasons change. I treated onboarding like product onboarding. I reduced ambiguity in what the meetup is for, wrote clearer event pages, and kept the default experience free so people could try it without overthinking it. The result was a steady stream of new members who then turned into attendees, volunteers, and in some cases, future speakers.

ZurichJS community page Sponsor or host an event

Source: Meetup.com member analytics

Unlocked sustainability through partnerships

Engaging more than 20 partners shifted ZurichJS from ad-hoc to sustainable. Partnerships covered venues, food, and speaker travel support, which kept meetups free and workshops low-cost while raising the overall production quality.

Meetups die when they rely on personal funding and last-minute logistics. In 2025, I activated more than 20 partners across sponsors, venue hosts, and community collaborators. That changed the operating model. It let us offer food consistently, keep the meetups free, and run workshops at accessible prices without draining the organizers. I approached partnerships like a product surface: clear tiers, clear expectations, and reliable delivery. Partners do not want vague community goodwill, they want outcomes they can understand, like brand placement, hiring visibility, or meaningful engagement with engineers. Once that proposition became repeatable, ZurichJS stopped feeling fragile and started feeling self-sustaining.

Partner and sponsorship info

Source: ZurichJS partner records

Improved quality, not just volume

A 4.8/5 average rating signals that the format delivered real value to attendees. That matters because it compounds: it increases return attendance, strengthens speaker referrals, and reduces the effort needed to fill rooms and secure partners.

Growth metrics are easy to chase, quality is harder to hold. In 2025, ZurichJS sustained an average rating of 4.9/5. I care about that number because it reflects whether the meetup respects people’s time. To keep the quality bar high, I treated each event like a mini product release: clear goals, a tight agenda, good facilitation, and speakers who can teach from real projects. I also made operational consistency non-negotiable. If people show up and the experience varies wildly, they stop trusting the brand. A high rating makes everything downstream easier. It reduces the marketing burden, increases repeat attendance, and creates a positive feedback loop where strong speakers want to associate with the meetup.

See the ZurichJS format

Source: Meetup.com ratings

💰

Product / Monetization

4 metrics

Removed payment friction in a key market

Adding Alipay dramatically increased successful checkouts in Asia, proving that local payment methods are a primary growth driver in region-specific markets.

The Alipay rollout showed that payment methods are not a backend detail, they are product features. By aligning UX, routing, and observability, we turned a single integration into a 3.5x revenue uplift in Asia. This became a reference point for how we evaluated and prioritized future payment methods.

Payments orchestration talks

Source: Payments and revenue dashboards

Improved conversion and reliability"

A smaller checkout bundle reduced load times, lowered error rates on slower connections, and improved overall conversion, especially in emerging markets.

Checkout performance directly affects revenue. By reducing the checkout bundle size by 70%, we improved load times and resilience under poor network conditions. This mattered most in regions where connectivity is inconsistent, turning performance work into a revenue lever rather than a purely technical win.

Source: Build metrics and performance tooling

Turned monetization into a measurable, repeatable system

Running more than 20 experiments shifted monetization decisions from opinion-driven to data-driven. This reduced rollout risk, improved conversion, and enabled consistent learning across regions, payment methods, and subscription flows.

Monetization experiments only work if the underlying system can change safely. At Smallpdf, I ran more than 20 experiments, but the real impact came from building a platform where experimentation was the default, not a risk. By unifying checkout and subscription flows and enforcing proper instrumentation, teams could test pricing, payments, and lifecycle changes without fear of breaking core revenue. This approach reduced decision latency, increased confidence in results, and made monetization a continuous optimization loop instead of a series of one-off bets.

Talks on monetization systems

Unblocked global expansion

Reducing rollout time enabled faster entry into new markets and quicker response to regional payment needs, directly impacting revenue velocity and experimentation throughput.

Before orchestration, adding or adjusting payment methods was slow and risky. By building a reactive payment orchestration layer, we reduced rollout time from days to minutes. This changed how the business approached expansion. New regions, pricing models, and payment experiments no longer required heavy engineering investment, which increased speed without sacrificing reliability.

Payments architecture consulting

Source: Internal delivery timelines

🎯

Engineering Leadership

1 metric

Improved delivery and career progression at squad scale

Led a 15-person cross-functional group while keeping execution moving and making space for career development. Skip-level management across two squads improved alignment and removed blockers earlier, which reduced delivery risk and improved team confidence.

At Navro, I led a 15-engineer cross-functional squad spanning frontend and backend Java. The outcome I cared about was not “more meetings,” it was smoother delivery with healthier careers. I focused on two things: execution reliability and leadership leverage. I set a clear cadence for planning and delivery, then used it to surface risks early rather than late. In parallel, I coached tech leads so decisions did not bottleneck through me. Skip-level management across two squads helped me spot misalignment, scope creep, and morale issues before they turned into delivery incidents. The result was a team that shipped consistently while still making space for progression, feedback, and talent growth.

Coaching or advisory call

Ready to create impact together?

Let's build something meaningful

Whether you need a speaker for your conference, a community leader for your meetup, or technical expertise for your team, let's discuss how I can contribute.

Invite me to speak Explore services

Explore more

Speaking → Consulting → Mentorship → About →