Airbnb Dynamic Pricing And Host Supply Elasticity

What's being tested

Interviewers are checking your ability to design credible causal estimates and experiments that measure how a dynamic pricing intervention changes host behaviour (supply) and guest demand. Expect to justify randomization unit, metrics, power, and identification strategy while accounting for endogeneity, spillovers, and delayed supplier responses. Airbnb cares because pricing changes can shift short-run bookings and long-run host participation — mismeasuring either leads to wrong product decisions or marketplace instability.

Core knowledge

Host supply elasticity formula: elasticity = percent change in supplied nights (or active hosts) / percent change in price; compute short-run vs long-run by varying measurement windows and lag structure.
Primary metrics: bookings_per_host, nights_booked, host_activation_rate, host_deactivation_rate, revenue_per_host; define denominators and aggregation level (per-host-week is common).
Randomization unit tradeoffs: randomize at listing, host, or market level. Listing-level needs many samples but risks within-host contamination; market-level reduces spillovers but requires fewer clusters and larger sample sizes.
Clustered randomization & inference: when randomizing clusters, use cluster-robust standard errors or randomization inference; adjust power for intra-cluster correlation (ICC). Simple formula: effective N ≈ N / (1 + (m−1)ICC).
Power & MDE: compute minimum detectable effect (MDE) on elasticity by simulating variance of logged outcomes: with outcome $y = \log(nights)$ and treatment shift $\Delta\log(price)$ , elasticity ≈ $\Delta y / \Delta\log(price)$ . Convert desired elasticity to absolute change in log-outcome for power input.
Identification threats: endogeneity (prices respond to demand), anticipation (hosts change behaviour before full rollout), and spillovers (treatment affects nearby untreated listings). Pre-specify exclusion windows and spatial buffers.
Causal methods when RCT infeasible: difference-in-differences (DiD) with parallel trends and multiple pre-period checks, instrumental variables (IV) using exogenous variation (e.g., randomized price-suggestion rollout or algorithm A/B), and synthetic control for single-market rollouts.
Modeling dynamics: use distributed-lag models or panel regressions with host fixed effects to separate immediate vs delayed supply responses; estimate half-life of adjustment.
Heterogeneity & segmentation: expect elasticity to vary by property_type, occupancy_rate, urban vs rural, and host professionalization; pre-specify subgroup analyses and correct for multiple comparisons (e.g., family-wise error or Benjamini–Hochberg).
Metric contamination & monotonicity: dynamic pricing may optimize revenue, increasing price while decreasing nights; always report both volume and revenue metrics and compute welfare-relevant aggregates (e.g., marketplace revenue, guest spend).
Diagnostic checks: balance tests on pre-period outcomes, temporal placebo tests, and falsification checks using unaffected metric (e.g., unrelated category bookings).

Tip: pre-register primary metric, randomization unit, and analysis window; simulate power under realistic ICC and sparse-event hosts.

Worked example — "Design an experiment to measure host supply elasticity to price changes"

First 30s framing: clarify the treatment (algorithmic price suggestion vs enforced price change?), randomization unit (listing, host, or market), outcome definition (nights_booked per host-week vs active host count), and desired horizon (short-run 4 weeks vs long-run 6 months). Ask whether pricing is applied to suggestions only or forced — this affects compliance.

Skeleton of answer (3–5 pillars): (1) Treatment design and unit: choose host-level randomization if hosts manage multiple listings to avoid within-host contamination; (2) Sample and power: estimate ICC from historical nights_booked and compute MDE for an elasticity target (e.g., −0.2); (3) Measurement: primary outcome log(nights_booked+1) and secondary host_activation_rate; (4) Analysis: intention-to-treat (ITT) using clustered regression with host fixed effects and time dummies, estimate elasticity as coefficient on treatment scaled by average percent price change; (5) Robustness: check compliance (price acceptance), heterogeneity, and spillovers.

Tradeoff to flag: randomizing at market reduces spillovers but increases required sample (fewer clusters → lower power); justify choice by estimated ICC and operational constraints.

Close: if more time, propose an IV for imperfect compliance (use assignment as instrument for realized price change), simulate long-run equilibria with a structural model, and plan an adaptive rollout to refine MDE.

A second angle — "Estimate short-run and long-run host supply elasticity using observational data"

Framing change: no RCT; instead you must rely on quasi-experimental variation. Use a staggered rollout or an exogenous shock (e.g., platform algorithm change A/B assignment or a local demand shock unrelated to supply) as an instrument. Approach: (1) build panel of listings with host fixed effects and time controls; (2) implement DiD around rollout with event-study for parallel trends; (3) if price is endogenous, use assignment-to-algorithm (or randomized suggestion probability) as an instrumental variable — first stage: price change ~ assignment; second stage: supply outcome ~ predicted price. Estimate short-run elasticity on weeks 0–4 and long-run on 3–12 months, using distributed-lag IV to capture persistence. Emphasize strong robustness: placebo runs, sensitivity to control set, and bounding (e.g., Oster bounds) for omitted variable bias.

Common pitfalls

Pitfall: Ignoring endogeneity — naive OLS of supply on price will typically be biased because price changes respond to unobserved demand shocks; always discuss identification and consider IV or RCT.

Pitfall: Choosing the wrong randomization unit — randomizing listings when hosts manage many listings invites interference; interviewers expect you to describe and justify unit-level contamination strategies.

Pitfall: Underpowered design — failing to account for ICC or sparse-event hosts leads to MDEs too large to be useful; always simulate power with realistic variance and cluster structure.

Connections

Interviewers may pivot to marketplace equilibrium modeling (structural supply/demand estimation) or to model evaluation for the dynamic pricing algorithm (offline A/B metrics, regret analysis). They may also ask about long-term welfare or policy implications (platform fees, fairness).