EXPERIENCE
These case notes cover shareable past development and operations work. They do not describe current commercial relationships.
Domain experience
Rail booking asks for more than an origin and destination. Fare conditions, times, station names, seats and change rules all affect a travel plan. In work involving Italo and Deutsche Bahn services, we treated that information in the order a customer uses to compare and choose. Product information and reservation state were considered together so confirmation remained useful after booking.
A London theatre booking is not chosen by title alone. Performance time, venue, seat, price and attendance conditions shape expectation together. In operating the service, the priority was deciding what to explain first and where a customer needed help. The journey supported customers before purchase and gave them a way to revisit their decision afterwards.
Across international API-based services, data formats, refresh cycles, reservation states and error policies varied by supplier. A customer should see a coherent service, while the product team must retain those differences. SORADA established how product and reservation states were interpreted, then reviewed what should be shown and who should decide during pending confirmation and exception cases.
Travel operations involve product information, multilingual content, reservation data and change requests at the same time. An operating interface is not a storage room for data; it is where a person sees evidence and chooses the next action. This work focused on bringing customer-facing information and internal status together so changes and exceptions could be handled in regular practice.
