
What happened
Airbnb CTO Ahmad Al-Dahle said about half of support tickets are now resolved purely by AI, 60% of code is AI-authored, and features shipped are up nearly 80% year over year.
Why it matters
That means a large share of Airbnb's support work and code is now produced without a person doing it, though Al-Dahle said the company is deliberate about which tickets agents do not yet handle, such as safety issues.
What to watch
Al-Dahle's worry is whether junior engineers still build judgement when AI does so much work, so he is pushing every engineer to explain what an AI-generated pull request actually does; watch the 45% support figure from Airbnb's Q2 results.
WHO IT HITSEngineers and support staff at large software and marketplace companies are the ones feeling this first: Al-Dahle described coding as tolerant of latency but expensive when mistakes slip through, so teams may keep the strongest frontier model for code and smaller, cheaper post-trained models for high-volume tasks like search. Junior engineers in particular may see their training and review process change, since Al-Dahle said every engineer must be able to explain AI-generated work.
Summaries like this, in your inbox every morning.
Al-Dahle joined Airbnb as CTO in January after serving as head of generative AI at Meta, where he led the launch of its open source Llama models over 2023-2025. His stated reason for the move was to chase the next hard frontier: at Meta, he said, "we kind of knew what the flywheel looks like," while the open challenge now is deploying models at scale in ways that add value to a core user experience. Airbnb, founded in 2008 and public since 2020, carries a market capitalization of approximately $93 billion, so the scale of that deployment challenge is considerable.
The internal changes he described feed directly into the products guests see. Airbnb used an internal organizational context graph called Everest, which relies on technologies like LLMs, embeddings and AI-based retrieval, to build and query its graph. The grocery delivery service was built first, and the learnings from it were made available in Everest, which let the airport pickup team move much faster because the two services share a similar shape: API integrations with partner companies layered onto Airbnb's platform. Al-Dahle also said the context graph lets generalists work across very specialist parts of the codebase, which is a different answer to the handoff-heavy process of product requirements, design, engineering and testing that traditional software teams rely on.
The stakes appear to hinge less on whether the models are good enough than on how Airbnb keeps engineering judgement intact, especially among junior staff who now work alongside systems that produce so much of the output. Al-Dahle's answer is a rule that every engineer must be able to explain what was built, even when an AI generated the pull request; whether that rule holds as asynchronous agents spread from on-call triage to fraud, trust violations and marketplace quality is likely to be the thing worth watching.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Anthropic CEO Dario Amodei is reportedly targeting a pre-Thanksgiving IPO, even as Oura postpones its offering…
Huawei raised flagship prices by up to US$200, citing an average US$200 rise in per-unit manufacturing costs…

SpaceX stock rose 6.1% through 11 a.m

At Fortune's AIQ Summit, Booking Holdings CFO Ewout Steenbergen said hyperscalers spending hundreds of billion…

A Japanese edition of Machine Learning for High-Risk Applications (O'Reilly Japan, 2025) describes how Zillow'…

PwC Japan's spring 2026 six-country survey found only 9% of Japanese companies got effects that "greatly excee…
