Title: VizualTravel — a platform where travellers build, publish and share trip plans Role: Lead Product Engineer (built with a team) · Link: vizualtravel.com Skills (3): TypeScript · Next.js · Node.js

Planning a trip means twenty browser tabs and a spreadsheet you abandon halfway. VizualTravel is where travellers build an itinerary properly — day by day, costed — then publish it for everyone else to use. One person's planning becomes the next person's starting point, on web and mobile.

I'm a lead product engineer on the team that builds it. Two pieces were mine end to end:

A video rendering service, so a trip plan can travel. An itinerary animates beautifully in the browser and is impossible to share. I built the service that renders it to video: a request goes onto a BullMQ queue, a worker drives headless Chrome through Puppeteer, plays the animation, records it, and delivers the file to whoever asked. DynamoDB holds job state, so a request survives a worker dying and a user can always be told where their render is. Video rendering is slow and bursty by nature — it needed a queue and durable state, not a request handler.

The migration to Next.js. I ported a large React single-page app across. Published itineraries became server-rendered and indexable, so the plans themselves bring in traffic instead of being invisible to search.

Alongside the team I worked on the AI itinerary generator, Stripe subscription billing, and real-time collaboration on Supabase Realtime so two people planning one trip see each other's edits rather than overwriting them.

I also helped on the mobile app — I write React Native, so I built screens and carried web features across to keep the two in step. I didn't build the app.

TypeScript throughout: Next.js and React on the web, Node.js for the render service and API, Postgres and Supabase, DynamoDB for job state, continuous deployment.