How would you improve reliability and latency for Guest App at global scale

Problem Statement Description

Product context: Airbnb is a travel marketplace connecting guests and hosts; its products include stays, experiences, host tools, guest booking, trust and safety, payments, and reviews.

Airbnb’s Guest App serves travelers around the world who search, compare, book, manage, and get support for stays and experiences. For families, the workflow can be especially high-stakes: multiple guests, stricter filters, date flexibility, safety needs, longer planning cycles, and greater sensitivity to booking failures or slow responses during checkout, messaging, trip changes, and support moments.

You are being asked, as a Technical PM, to define how you would improve reliability and latency for the Guest App at global scale. The scope should cover both the user-facing experience and the underlying product, platform, data, and operational systems that make the app dependable across regions, devices, network conditions, traffic spikes, and marketplace dependencies.

This is not only an infrastructure question. You should connect technical choices to guest trust, conversion, host supply health, marketplace quality, and competitive expectations versus travel alternatives such as Booking.com, Expedia, Vrbo, hotels, Google Travel, and local rental platforms.

The experience should consider:

- Critical guest journeys, including search, listing detail pages, wishlists, checkout, payments, booking confirmation, host messaging, trip management, cancellations, and support.

- Reliability and latency definitions, including availability, error rates, page/API response times, app startup time, checkout success, message delivery, and regional performance.

- Global constraints such as geography, localization, payment methods, device quality, network variability, peak travel demand, and cross-border data or compliance requirements.

- APIs, services, and data dependencies across search, pricing, availability, identity, trust and safety, payments, notifications, messaging, and customer support.

- Trade-offs between speed, correctness, personalization, inventory freshness, fraud prevention, privacy, and marketplace fairness.

- Observability needs, including instrumentation, service-level objectives, alerting, incident detection, customer-impact measurement, and cohort-level diagnostics.

- Rollout and risk management, including experimentation, phased launches, backward compatibility, graceful degradation, incident response, and rollback planning.

- Family-specific expectations, such as confidence in availability, accurate amenities and policies, reliable communication, and low-friction booking for higher-consideration trips.

The goal is to describe a clear technical product approach for improving Guest App reliability and latency in a way that is measurable, scalable, safe to roll out, and aligned with Airbnb’s trust-based marketplace.