Changing a critical system
without losing its behaviour.
As a Software Engineer at Tripadvisor / Viator, I worked across backend systems, frontend projects, technical SEO, and internal tooling. I led the availability workstream within a broader legacy backend migration. Availability determines whether someone can book an experience; correctness and continuity were central to every decision.
Read the supplier integration storyThe engineering challenge
Bring the core availability logic into the new system, preserve the business rules, and redesign inefficient asynchronous and batch calendar processing. We found work running synchronously without a reason to block, and moved it into asynchronous processing.
The release mattered as much as the design
We first ran shadow requests to check the new behaviour. Once the results matched our expectations, we shifted live traffic progressively, starting at 1% and increasing until the new system handled all availability traffic.
My responsibility was the availability workstream. The migration and its wider outcomes were a team effort.
Other work at Viator
- Supplier connectivity migration to COIN, including FareHarbor, Bokun, and Rezdy.
- Per-customer SQS queues for fairer processing and fault isolation.
- An event-driven sitemap pipeline, moving updates from roughly weekly to near real time across millions of pages.
- Rebuilding a monitoring application with Java 21, Spring Boot, React, and DynamoDB, bringing queries from seconds to milliseconds and eliminating daily crashes.
