The problem
oneworld’s Round the World program lets travelers build a single itinerary spanning 20+ member airlines and over a thousand cities, priced either by how many continents the trip touches (oneworld Explorer) or by total distance flown (Global Explorer). Turning that into a self-service web product meant giving travelers a way to construct a multi-leg, multi-airline route, price it against those alliance-wide fare rules, and book it — without falling back on a travel agent or manually piecing fares together across carriers.
My role
Technical Architect for OneWorld Round the World, Fly OneWorld, and Noble Caledonia — owned the technical architecture and UI layer, plus the production infrastructure and deployment automation that kept all three booking platforms running.
Approach
Built the itinerary-building and fare UI in Angular against a Node.js and MongoDB/PostgreSQL backend, then owned the AWS production environment end to end — EC2, RDS, S3, Lambda, and CloudFront for the application tier, Route 53 and ACM for domains and certificates, CloudFormation for repeatable infrastructure, and auto-scaling, CloudWatch, and IAM for the operational and security side. Set up the deployment pipeline and monitoring so releases across the three products stayed predictable.
Outcome
Kept OneWorld Round the World, Fly OneWorld, and Noble Caledonia live and stable in production for travelers booking across a 20+ airline global alliance — with self-service architecture and infrastructure automation replacing what used to require manual, agent-assisted fare construction.