Design the event instrumentation for Pricing Tools at scale 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 hosts use Pricing Tools to set nightly rates, discounts, fees, minimum stays, and availability rules across listings and markets. At global scale, these tools influence marketplace conversion, host earnings, guest trust, and competitiveness against hotels and online travel agencies, especially for business travelers who are sensitive to price transparency, reliability, and policy consistency.

In this interview, you are asked to design the event instrumentation for Pricing Tools: what should be tracked, where events should fire, how data should flow, and how the instrumentation should support product decisions, experimentation, debugging, compliance, and operational monitoring. The scope includes host-facing workflows, backend pricing calculations, guest-visible price outcomes, and cross-surface consistency across web, mobile, APIs, and internal systems.

Your answer should focus on the technical product design of a scalable, reliable instrumentation system rather than recommending pricing changes. You should clarify assumptions, define the key entities and workflows, identify the events and properties needed, and explain how teams would use this data to understand adoption, correctness, latency, revenue impact, and marketplace health.

The experience should consider:

- Core user workflows, including hosts configuring pricing rules, reviewing recommendations, accepting or rejecting suggestions, and seeing updated prices reflected to guests.

- Event taxonomy and data contracts for pricing actions, recommendation exposure, edits, saves, errors, overrides, experiments, and downstream price rendering.

- APIs, data pipelines, schemas, versioning, identity resolution, and how instrumentation remains consistent across regions, currencies, devices, and listing types.

- Reliability requirements such as event delivery guarantees, deduplication, ordering, latency, backfills, monitoring, and failure handling.

- Privacy, security, and compliance constraints around host earnings, guest search behavior, location, business travel signals, and financial data.

- Observability for pricing correctness, recommendation quality, stale data, broken surfaces, unusual conversion changes, and marketplace anomalies.

- Rollout strategy, including phased launches, validation, experimentation readiness, dashboards, alerting, and rollback criteria.

- Product trade-offs between instrumentation depth, engineering complexity, data freshness, cost, and long-term maintainability.

The goal is to demonstrate how you would design instrumentation that gives Airbnb teams trustworthy, actionable visibility into Pricing Tools at global scale while supporting experimentation, operational resilience, marketplace quality, and safe product evolution.