← Airbnb Interview Insights

Airbnb·Software Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
Jul 2026

Summary

Airbnb system design round focused entirely on building a dynamic pricing engine for hosts. One very long question that kept branching into new sub-problems every time I thought I'd wrapped up a section.

Questions Asked (1)

Q1

Design an ML-powered system that recommends nightly rental prices to hosts. Walk through the full stack: problem formulation, data sources, feature engineering, modeling approach, training pipeline, inference architecture, and rollout strategy.

System DesignA/B Testing & ExperimentationPricing & Monetization
Author's notes

This question kept expanding.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the business objective and constraints, then walk through the ML system design in a structured manner covering problem formulation, data, features, modeling, training, inference, and rollout. Emphasize how the system balances host autonomy with algorithmic recommendations and how you would measure success through experiments.

Pro tip: Focus on the human-in-the-loop aspect: hosts can override recommendations, so design the system to provide explainable suggestions and measure host acceptance rate as a key metric. Also, discuss how you would handle cold-start for new listings by leveraging similar listings and geographic data.

1. Clarify Requirements and Problem Formulation

Ask questions to understand the goal: increase bookings, host revenue, or occupancy? Define the ML problem as a regression or ranking task, and specify the prediction target (e.g., optimal price per night) and constraints (e.g., host-set minimums).

2. Data Sources and Feature Engineering

Identify data sources: listing attributes, host behavior, booking history, search logs, competitor prices, seasonality, local events. Engineer features like location embeddings, amenity scores, demand indices, and host responsiveness.

3. Modeling Approach and Training Pipeline

Choose models (e.g., gradient boosted trees for tabular data, deep learning for text/images) and design a training pipeline with periodic retraining, validation, and hyperparameter tuning. Consider multi-task learning to predict both price and demand.

4. Inference Architecture and Serving

Design a low-latency inference service that can handle real-time requests from hosts, with caching for frequent queries. Use a feature store to ensure consistency between training and serving.

5. Rollout Strategy and Experimentation

Plan a phased rollout: start with a small percentage of hosts, run A/B tests to measure impact on bookings and revenue, and iterate based on feedback. Include guardrail metrics to avoid negative host experiences.

Key Points to Mention

  • Problem formulation: predicting optimal price to maximize bookings or revenue, considering host constraints and market dynamics.
  • Data sources: internal booking data, search logs, host preferences, external data like events and holidays.
  • Feature engineering: location-based features, seasonality, demand elasticity, competitor pricing, and host quality metrics.
  • Modeling: use of gradient boosted trees or deep learning, with techniques like quantile regression to provide price ranges.
  • Training pipeline: automated retraining, monitoring for data drift, and versioning of models.
  • Inference: real-time API with low latency, feature store integration, and fallback strategies.
  • Rollout: A/B testing with metrics like booking conversion, host acceptance rate, and revenue lift, and guardrails for host satisfaction.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.