Professional engagements, each described by the problem I was responsible for rather than the screens I shipped.
01·Engagement·B2B concierge and booking marketplace
GoCierge
Problem owned
A booking workflow where payments, providers and customers all have to agree, even when the external systems don’t.
Ownership
- Booking and Stripe payment flows built to tolerate duplicate actions and partial failure.
- An adapter layer over third-party service-provider APIs, with deliberate retry and conflict handling.
- Product ownership from requirements to production, across NestJS, PostgreSQL / Prisma and Next.js.
02·Engagement·Fintech and crypto platform
Zeply
Problem owned
A platform of many small services that had to cooperate without waiting on each other.
Ownership
- Roughly eight Node.js / TypeScript microservices working together as one platform.
- Asynchronous, event-driven workflows over RabbitMQ, with services decoupled from each other.
- Fastify-based services written in TypeScript.
03·Engagement·Product and platform engineering
Tiketti
Problem owned
Several front ends that needed shared foundations, not duplicated ones.
Ownership
- A TypeScript monorepo carrying multiple Next.js applications on shared foundations.
- Shared React and UI architecture, documented in Storybook.
- A Blocks Builder / CMS and the backend integrations behind it.