Technology lead who still codes.

Modern travellers are inspired by watching video. The businesses selling those destinations still run on static photography, or on social media footage where rights clearance is tricky. The video that actually moves people is being made by travellers, and it never reaches the brands who need it.

Closing that gap is an engineering problem before it is a content one. It means making 250k+ unedited clips findable by place, mood and season rather than by filename, clearing rights so that licensing is one click instead of one email thread, and serving a single library through four products that each want something different from it: a consumer discovery app, a licensing platform for business, a B2C booking OTA, and a commercial API.

• 01Front-end architecture: Every public front end over a shared platform API, behind a BFF layer, with typed clients generated from the OpenAPI spec.
• 02Native apps: The React Native iOS and Android clients, from build config to store release.
• 03Discovery and search: Clustered map browsing with deck.gl and supercluster, plus the taxonomy the consumer product is navigated by, across country, vibe, place type, experience, traveller type and season.
• 04Licensing and checkout: Stripe payments, webhook-driven fulfilment, licence delivery and download.
• 05Booking: The OTA side, where a video becomes a trip. Hotels, tours and experiences, with member pricing through the Travel Club.
• 06MOATS and the commercial API: The branded hub that turns guest and creator video into approved brand content, and the public API I oversaw the creation of, with proximity, taxonomy and natural-language search, and SDKs in TypeScript, Python and Ruby.
• 07Leading the team: A distributed engineering team, while staying hands-on with architecture, code review and production delivery.