Inside-Out AI: Rebuilding Airbnb Behind the Scenes and Across the Guest Experience
https://www.latent.space/p/airbnb📌 從Meta到Airbnb:CTO揭露AI重塑內外體驗的做法
TL;DR:曾主導Meta Llama的Ahmad Al-Dahle空降Airbnb CTO,用「由內而外」策略把AI能力從內部開發線帶到客服與新服務。
60%的程式碼由AI寫成,功能交付量年增近八成,這不是新創的願景簡報,而是一家市值近千億美元上市公司的現況。
🤔 從打造前沿模型,到把模型部署到位
Ahmad Al-Dahle今年一月加入Airbnb擔任CTO之前,是Meta生成式AI部門負責人,主導了2023到2025年間Llama開源模型的發布。他向Latent Space解釋轉換跑道的原因:「我傾向追逐我認為最難的前沿所在」。在Meta,團隊已經摸清模型能力世代提升的飛輪該怎麼轉;他認為下一個挑戰是大規模部署模型,推動人們改變工作方式,並把這些系統真正落地到會為核心使用者體驗創造價值的生產環境。
🧩 先改流程,再談工具
Al-Dahle說,Airbnb的AI轉型首先是組織流程的改變:傳統上產品需求、Figma設計、工程實作、上線測試之間各自交接;現在產品、設計與工程團隊會直接共同處理原型(prototype)。他形容:「把這些交接的時間差打掉,正是許多傳統軟體公司要跨出這一步最大的節省來源。」這也讓團隊從過去「產出大量文件artifact」的模式,轉向以程式碼本身和原型作為討論依據。
📊 具體數字:程式碼、功能交付與客服
Al-Dahle提出幾個數據佐證轉型成效:目前Airbnb有60%的程式碼由AI撰寫,功能與改善項目年增近80%,一般工程師的PR(pull request)產出量提升約1.6倍。客服是Airbnb第一個導入AI的面對使用者場景,Al-Dahle形容這是「最難部署的問題」,因為出錯代價很高。做法是先用合成資料大量測試代理,確認可靠後才上線;目前約半數客服工單由AI獨立解決(與Airbnb第二季財報揭露的近45%數字相符),但團隊刻意保留涉及安全性等情境交由人工處理。另外兩個今年稍早推出的新服務,雜貨外送與機場接送,則受惠於一個名為Everest的內部組織情境圖(context graph),它運用LLM、embedding與AI檢索技術打造而成。根據Airbnb第二季財報,雜貨外送服務花了八、九個月開發,有了Everest累積的經驗後,機場接送只花了約六週。Al-Dahle指出,這個跨程式碼庫的情境圖讓「通才工程師也能跨入非常專精的程式碼領域工作」。
💡 多模型策略:每個場景選對的工具
Al-Dahle形容Airbnb是一家「多模型公司」,內部生產系統部署了至少10個客製化模型,並針對每個使用情境在成本、效能與延遲之間畫出帕雷托前緣,各自取捨。例如寫程式碼能容忍較高延遲但犯錯代價高,因此偏好使用最頂尖的前沿編碼模型;搜尋功能則對延遲極度敏感,偏好經過後訓練(post-train)的小型專用模型,他甚至表示,針對狹窄情境做後訓練的小模型,效能有時能超越前沿模型。Airbnb內部也有自己的代理AirChat,整合了組織所需的MCP情境。更進一步的方向,是讓非同步代理在容器中依事件觸發運作:例如監控系統(如Grafana)告警觸發時,代理會自動啟動進行事故分診與初步處理,人類工程師審查代理提出的PR,若代理判斷是誤報甚至可以自行結案。Al-Dahle的願景是用大量非同步代理去協助管理詐欺偵測、信任違規、市集品質與軟體缺陷等整個市集平臺的運作。
🎯 實務啟示
Airbnb的經驗提供一個清晰的框架:先把AI用在內部開發流程打穩地基,再把同樣的能力延伸到面對使用者的高風險場景(如客服),並且針對不同任務場景(編碼 vs. 搜尋)審慎選擇模型大小與後訓練策略,而非迷信單一前沿模型打天下。
🔗 來源
- 標題:Inside-Out AI: Rebuilding Airbnb Behind the Scenes and Across the Guest Experience
- 作者/機構:Latent Space
- 連結:https://www.latent.space/p/airbnb
#AirbnbAI #AINative #LLMOps #AIAgents #Llama #EnterpriseAI #AIinProduction #CustomerSupportAI #MultiModel #AsyncAgents
原始資料 Latent Space · 收集於 2026-10-02
摘要原文
Prior to joining Airbnb as CTO in January, Ahmad Al-Dahle was head of generative AI at Meta and led the launch of its open source Llama models over 2023-2025. Now Al-Dahle is in charge of turning Airbnb into an “AI-native company”. What that means in practice is using AI internally to speed up product development, then using those same capabilities to transform the customer experience . We’re calling this an “inside-out AI” approach and in this article we’ll dig into the details. Al-Dahle spoke with Latent Space about Airbnb’s AI transformation. We began by asking him why he made the shift from building frontier models at Meta to deploying them at Airbnb . “Fundamentally, I like to chase where I believe the hard frontiers live ,” he replied, pun perhaps intended. “We kind of knew [at Meta] what the flywheel looks like, we understood how to improve the model capabilities, generation on generation.” The next challenge, Al-Dahle thinks, is deploying models at scale. At Airbnb, his goals are to “ push people to work differently , because these tools are transforming how you work,” and to “ take these systems and deploy them in production , in creative ways that actually add value to a core user experience.” From its launch in 2008, Airbnb has been considered a technology company operating in the hospitality industry. The company went public in 2020 and now has a market capitalization of approximately $93 billion (at time of writing). So it’s a big operation to try and make “AI-native.” Al-Dahle reeled off a few statistics to show that Airbnb is AI-pilled now: 60% of its code is now AI-authored , it has shipped nearly 80% more features and improvements year over year, and pull-request throughput for the average engineer is up about 1.6x . But how exactly has Airbnb done all this? Firstly, he said it’s about changing the organizational process for software engineering . Traditionally, you might do product requirements, then design work in Figma, then engineering implementation, and eventually production testing. In the past, these would’ve required handoffs from one team to another. But now, Airbnb has its product, design and engineering teams move directly to working with prototypes . “Breaking that time down is actually one of the biggest savings that a lot of traditional software companies have to make the leap to do,” said Al-Dahle. “And so we made that leap and it actually ended up adding a ton of tailwind to our product development process.” A byproduct of this change is that teams deal directly with code , rather than dealing with “artifacts” like a product requirements document. “We moved away from excessive artifact generation to the code being the artifact that we reason upon, and prototypes ,” he said. Al-Dahle told us that customer support was the first user-facing area that it introduced AI into. He described it as “the hardest problem to deploy,” because “the stakes and the consequences of a mistake are really high.” Roughly half of Airbnb’s support tickets are now resolved purely by AI , said Al-Dahle (this is in line with the company’s Q2 results , which put the figure at nearly 45%). The key to this, he says, is using synthetic data to thoroughly test the system before taking it to production. “We start with: build a model, build the agent, and begin to generate a battery of synthetic data before you ever go into production.” He notes that although agents handle about half of customer support queries, they are careful about what requires human assistance — with safety issues, for example. “So while we solve 50% of the tickets, we’re actually deliberate about the tickets we don’t choose to solve yet [with agents].” Two Airbnb Services projects you may not be familiar with yet are grocery deliveries and airport pickups (the grocery service has just been expanded to more cities ). Both were launched earlier this year, thanks in part to Airbnb’s inside-out AI approach. It was an internal organizational context graph called Everest that helped bring these products to market quickly. Al-Dahle said that Everest uses technologies such as LLMs, embeddings and AI-based retrieval to build and query the graph. He explained that the grocery delivery and airport pickup services are “kind of similar services — API integrations with partner services [external companies] that integrated onto our platform.” The grocery service was built first, and learnings from it were made available in Everest. That enabled the airport pickup team to do its project much more quickly. In its Q2 earnings report , Airbnb states that “groceries took eight months, nine months and airport pickups took about six weeks to develop.” Additionally, using Everest means its developers don’t necessarily need specialist knowledge to work on projects. “Because of this context graph that exists across the codebase,” said Al-Dahle, “we’re able to have generalists work across very specialist parts of the code .” Both of the new services were highlighted by CEO Brian Chesky at Airbnb’s 2026 Summer Release in May. To give more of a sense of Airbnb’s internal AI usage, Al-Dahle described it as a “multi-model company” and says it deploys “a lot of different models” in its production systems. Airbnb uses a mixture of frontier and open models, but conducts most of its own post-training and reinforcement learning on open models . Al-Dahle said the company deploys at least 10 customized models for production use cases. It also evaluates models along a Pareto frontier for cost, performance and latency , selecting a different trade-off for each application. “We run evals specifically for each use case,” he explained. “So if we’re using a model for search, we have a set of search queries that are sampled from production that we measure against. If we’re doing customer support, we also sample all the production queries that we care most about — including edge cases.” “We try to use the right tool for the right job,” he added. For example, coding can tolerate more latency but mistakes are expensive. So they prefer to use the strongest available frontier model for coding tasks. “It makes sense to use the absolute most frontier coding model , because for every defect that a model produces, it could easily cost us a lot more.” On the other hand, search is used at scale by Airbnb’s users and so is very latency-sensitive. So for that job, they prefer smaller specialized models. Al-Dahle claimed that smaller, post-trained models sometimes out-perform frontier models. “For narrow use cases, we’ve been able to take really small, really nimble models that are very fast and cheap and post-train them beyond the frontier.” Like other AI-native companies , Airbnb has created an internal agent — in its case called AirChat . “We have our own internal agent that we call AirChat, which [includes] basically all the necessary MCP organizational context,” said Al-Dahle. But Airbnb is also starting to implement what Al-Dahle sees as the next development in agents: asynchronous agents running in containers and activated by events. “A lot of our teams are starting to basically automate their on-calls,” he explained. “So if something trips, if a Grafana limit or whatever monitoring system that you use trips, agents spin up to then triage and run your on-call , your initial on-call.” A human engineer can review a PR proposed by the agent, while the agent may close the incident itself if it determines that the alert was flaky. This process reminds us of how open source projects like Vercel’s AI SDK, Astro, Flue and tldraw use software factories — teams of agents — to apply fixes and features . Al-Dahle sees this approach eventually being used across its entire marketplace platform; for example to monitor fraud, “trust violations,” marketplace quality, and software defects. “My vision is large amounts of asynchronous agents that are helping automate and manage the marketplace.
由 claude-code/sonnet 自動生成