search-ranking

2 posts

airbnb

Academic Publications & Airbnb Tech: 2025 Year in Review (opens in new tab)

Airbnb’s 2025 research program expanded across major academic venues, with a focus on applying AI, machine learning, and data science to search, ranking, personalization, and marketplace optimization. The company strengthened its presence at KDD and CIKM while broadening into NLP, optimization, and measurement science. Its research emphasized practical systems that improve experimentation, retrieval, recommendations, ranking quality, and booking conversion. ## Research Expansion in 2025 - Airbnb presented research at established conferences including KDD and CIKM, while expanding into venues such as COLING, LION, and VLDB. - Researchers used these conferences to: - Share production-scale findings with academic and industry peers. - Develop new collaborations. - Learn about emerging methods. - Mentor early-career researchers. - The work was organized around themes including applied machine learning for search and personalization, and NLP and LLM systems in production. ## Search Ranking and Marketplace Retrieval at KDD KDD is a leading conference for data mining, knowledge discovery, and large-scale analytics. Airbnb has presented there since 2018, and its 2025 contributions focused on improving search experimentation and location retrieval. - **Interleaving and counterfactual evaluation** - Airbnb introduced techniques for evaluating search-ranking ideas before launching full A/B tests. - These methods help teams identify promising experiments more quickly. - They are especially useful for accommodation booking, where long conversion cycles can make statistical significance slow to achieve. - The goal is to accelerate experimentation without compromising evaluation accuracy. - **Extreme classification for audience expansion** - Airbnb presented a high-precision approach to retrieving relevant geographic areas in its two-sided marketplace. - The system uses categorical location cells to identify areas containing listings a guest might realistically book. - This helps balance Airbnb’s diverse global inventory with users’ preferences for location, amenities, style, and price. - Airbnb also presented work on **TSMO**, or Two-sided Marketplace Optimization, and indicated that some technologies might eventually be open-sourced. ## Search and Recommendation Advances at CIKM At CIKM 2025, Airbnb’s Relevance and Personalization team had five peer-reviewed papers accepted. The work addressed search, recommendations, ranking metrics, multimodal representations, and user comparison behavior. - **Recommendations for overly narrow searches** - Airbnb developed a system that suggests alternatives when a guest’s search returns too few accommodations. - Suggestions may include different dates, broader amenity requirements, or adjusted price ranges. - The system aims to reduce search frustration and increase booking rates. - **Map-specific ranking optimization** - Maps account for approximately 80% of Airbnb search interactions. - Traditional feed-ranking assumptions do not accurately represent how users view and interact with map results. - Airbnb introduced a map-specific version of NDCG, a ranking-quality metric. - Experiments showed that optimizing for this metric improved bookings. - **BiListing multimodal embeddings** - BiListing combines listing text and photos into unified embedding representations. - It uses large language models and pretrained language-image models as ranking signals. - The approach produced a reported 0.425% improvement in normalized discounted booking gain and generated tens of millions of dollars in incremental revenue. - **Beyond pairwise learning-to-rank** - Airbnb proposed a learning-to-rank method that models interactions between items during pairwise comparisons. - This provides a more realistic view of what users prefer when evaluating search results. - The paper also describes efficient implementation techniques and online and offline evaluation results. - **Learning to Comparison-Shop** - The LTCS system models how users compare multiple listings rather than evaluating each listing independently. - It produced statistically significant improvements of 1.7% in NDCG and 0.6% in booking conversion rate. - The work reflects Airbnb’s broader effort to make ranking models sensitive to the context of an entire results page. ## NLP and Production LLM Systems - Airbnb also highlighted NLP and production LLM research, including participation in EMNLP. - Relevant application areas include: - Customer support. - Search and discovery. - Trust and safety. - EMNLP covers language-model architectures, training strategies, safety, evaluation, datasets, and open-source tooling. Airbnb’s 2025 publications show a strong emphasis on research that translates directly into marketplace performance. The most practical opportunities involve faster experimentation, context-aware ranking, multimodal listing understanding, and recommendation systems that help guests recover from overly restrictive searches.

dropbox

Inside the feature store powering real-time AI in Dropbox Dash (opens in new tab)

Dropbox Dash’s ranking system depends on a hybrid feature store that can combine real-time user behavior with large-scale historical data. Because Dropbox operates across on-premises and cloud environments, and because each query can trigger thousands of feature lookups, off-the-shelf systems could not meet its latency, scale, and integration requirements. The resulting architecture uses Feast for orchestration, Spark for computation, Dynovault for low-latency storage, and a custom Go serving layer, achieving roughly 25–35 ms p95 latency while keeping features fresh. ## Goals and Requirements - Dash ranks documents, images, and conversations using behavioral, contextual, and real-time signals. - A single query can fan out into thousands of feature lookups across many candidate files. - The feature store needed to: - Support sub-100 ms search latency. - Reflect user actions within seconds or minutes. - Bridge Dropbox’s on-premises services and Spark-based cloud infrastructure. - Handle both streaming-style updates and batch computations. - Let engineers develop features without managing serving and orchestration details. ## Choosing a Hybrid Architecture - Dropbox evaluated Feast, Hopsworks, Featureform, Feathr, Databricks, and Tecton. - Feast was selected because: - It separates feature definitions from infrastructure concerns. - Engineers can focus on PySpark transformations. - Its modular adapter system supports existing Dropbox infrastructure. - Feast’s DynamoDB adapter enabled integration with Dynovault, Dropbox’s DynamoDB-compatible storage system. - The architecture combines: - Feast for orchestration and serving APIs. - Spark jobs for feature computation and ingestion. - Cloud storage for offline indexing and data management. - Dynovault for online, low-latency lookups. - A custom Go service replacing Feast’s Python online serving path. - Dynovault is colocated with inference workloads and provides approximately 20 ms client-side latency. - Monitoring covers job failures, feature freshness, and data lineage. ## Replacing Python with Go for Low Latency - The initial Feast-based Python service struggled under heavy concurrency. - CPU-bound JSON parsing and Python’s Global Interpreter Lock became bottlenecks. - A multi-process design helped temporarily but introduced coordination overhead. - The serving layer was rewritten in Go using: - Lightweight goroutines. - Shared memory. - Faster JSON parsing. - The Go service now handles thousands of requests per second. - It adds only about 5–10 ms beyond Dynovault latency and achieves roughly 25–35 ms p95 latency. ## Keeping Features Fresh - Fresh signals are essential for ranking quality; actions such as opening a document should influence subsequent searches quickly. - Fully real-time computation is impractical for features requiring large joins, aggregations, and historical context. - Dropbox therefore built a three-part ingestion strategy. - Batch ingestion handles complex, high-volume transformations using a medallion architecture. - Intelligent change detection updates only modified records rather than rewriting every feature. - This reduced online-store writes from hundreds of millions to fewer than one million per run and significantly shortened update time. ## Practical Takeaway The system demonstrates that a feature store does not need to be entirely off-the-shelf or entirely real-time. Combining a modular framework with custom serving, colocated storage, batch optimization, and freshness monitoring allowed Dropbox to meet demanding latency and scale requirements while keeping feature development manageable.