What's the difference between DS-Analytics and DS-ML at Airbnb?

DS-Analytics owns the metric layer, A/B test analysis, causal-inference studies, and executive-facing product analytics; the day-to-day is SQL-heavy and cross-functional with PM. DS-ML owns ranking, pricing, and trust models; the day-to-day is model training, eval design, and offline-online metric alignment. The interview loops share the SQL screen and the behavioral rounds; the technical-depth round differs. Candidates pick a track in the recruiter call and the loop is built accordingly. The Airbnb Engineering blog (medium.com/airbnb-engineering) has documented the split publicly.

How important is causal-inference fluency for the senior bar?

Load-bearing at IC4+. Airbnb's marketplace structure violates SUTVA (the Stable Unit Treatment Value Assumption from the Rubin causal-inference framework); when a guest is treated, the host they book is implicitly treated. Senior DS articulates this on the marketplace case study and picks the appropriate method: geo-banded randomization for cleaner experiments, difference-in-differences for staged rollouts, synthetic control for one-off interventions. Candidates who default to a clean A/B test framing on a two-sided question without flagging the SUTVA risk get downleveled. The Microsoft Experimentation Platform body of work (exp-platform.com) and Imbens-Rubin causal-inference foundations are canonical prep.

What is the SQL phone screen actually testing?

Reading-comprehension under time pressure, plus correctness. The screen has two to four problems escalating in difficulty; the hardest reaches window functions, multi-step CTEs, and a deliberately-ambiguous business metric the candidate has to disambiguate before writing. The bar is reportedly higher than the FAANG mean per Hello Interview and r/datascience candidate retrospectives. A pattern that fails: candidates who start writing SQL before clarifying the metric definition. A pattern that passes: candidates who restate the question, name the assumption, then write a query that runs.

How does Airbnb compensation compare to FAANG?

Comparable at base; equity volatility is the differentiator. Per levels.fyi/companies/airbnb, IC4 senior DS clusters $380k-$580k total comp, IC5 staff $520k-$780k, IC6 principal $700k-$1.1M. Mix is base + bonus + ABNB RSUs vesting over four years with a one-year cliff. ABNB is public on NASDAQ since December 10, 2020; the comp band is exposed to share-price movement, which means the same nominal RSU grant is worth materially more or less depending on the vesting-day price. FAANG peer comp is comparable in nominal range but lower variance (the equity tickers are larger-cap and historically less volatile than ABNB).

Should I read the Airbnb Engineering blog before the onsite?

Yes, this is one of the strongest preparation moves a candidate can make. The blog (medium.com/airbnb-engineering) publishes substantial DS methodology work; the experiment-sensitivity post on in-experiment-data variance reduction, the experimentation-platform architecture series, and the Trust-and-Safety modeling posts are all directly referenced by interviewers. Candidates who walk into the technical-depth round having read the relevant posts can ground the discussion in real Airbnb work rather than generic methodology. Candidates who have not read the blog tend to lose the round to candidates who have.

Has Founder Mode actually changed the day-to-day for senior DS?

Yes, per candidate retrospectives and current-employee public commentary. The shift summarized in Paul Graham's September 2024 essay (paulgraham.com/foundermode) describes tighter founder-IC loops and less middle-management translation. The practical consequence for senior DS: exec-facing readouts happen earlier in the seniority arc, metric definitions are more politically loaded, and the speed of decision-making is materially faster than in the 2018-2022 era. The skill that gets rewarded is direct argument-construction and metric-defense; the skill that gets compressed is the explainer role between the data team and the PM team.

What teams should I target if I want the highest-impact DS work?

Pricing and Search are the most ML-heavy and the most quantitatively-load-bearing; both have published substantial work on medium.com/airbnb-engineering. Trust and Safety is the most causal-inference-heavy and has been a senior-DS career-accelerator over the past three years (the team has to defend policy-rollout lift on metrics like party-incident-rate where clean randomization is structurally infeasible). AirCover and Co-Hosting are newer surfaces with more open metric definition and therefore more room for a senior DS to define a new metric framework. Host Experience and Long-Term Stays are stable and well-defined; less new-metric room, more execution work.

Do I need a graduate degree for Airbnb DS?

Strongly preferred for DS-Analytics at IC4+, less weighted for DS-ML. The DS-Analytics track values stats-heavy graduate work (MS or PhD in statistics, economics, or quantitative social science) because the senior bar is causal-inference methodology fluency, which is graduate-level material. The DS-ML track values shipping experience over credentialing; strong portfolios with deployed ML systems or substantive open-source contributions clear the bar without a graduate degree. The recruiter call is the right place to ask about credential weighting for the target team.

Data Scientist / ML Engineer Hub

Data Scientist at Airbnb (2026): The Analytics vs ML Split, Two-Sided Marketplace Causal Inference, IC Comp

By Blake Crosley · Last verified 2026-05-28

In short

Airbnb is the canonical two-sided-marketplace DS company in 2026; the senior bar is causal-inference-fluent because randomization across guests is contaminated by host-side effects (the textbook SUTVA violation). Airbnb runs two separate DS tracks (DS-Analytics, which owns metrics and experimentation, and DS-ML, which owns models and ranking); the split is documented on the Airbnb Engineering blog (medium.com/airbnb-engineering) and shapes the hiring loop, the leveling rubric, and the day-to-day. Reported total comp at the IC4 / Senior DS tier clusters $380k-$580k; IC5 staff $520k-$780k; IC6 principal $700k-$1.1M (levels.fyi/companies/airbnb). Equity is in public-company ABNB stock (listed on NASDAQ since December 10, 2020), which means the comp band is exposed to share-price movement; refresh grants matter materially across a multi-year tenure.

Key takeaways

Airbnb operates two separate DS tracks. DS-Analytics owns metrics, A/B tests, causal-inference studies, and product readouts; DS-ML owns ranking models, pricing models, and trust-and-safety models. The interview loops differ; candidates pick a track in the recruiter call.
Airbnb DS comp per levels.fyi/companies/airbnb 2026 self-reports: IC3 (entry) $190k-$280k, IC4 (senior) $380k-$580k, IC5 (staff) $520k-$780k, IC6 (principal) $700k-$1.1M. Equity is ABNB common stock on NASDAQ; comp is volatile with the share price.
Causal inference is the senior+ differentiator. Airbnb's marketplace structure violates the Stable Unit Treatment Value Assumption from the Rubin causal-inference framework (en.wikipedia.org/wiki/Rubin_causal_model points to the original Imbens-Rubin treatment); when a guest is treated, the host they book is implicitly treated. Senior DS articulates this and picks geo-banded randomization, difference-in-differences, or synthetic-control accordingly.
The Airbnb SQL bar is the load-bearing screen. Candidates who clear the SQL phone screen advance; the bar is reportedly higher than the FAANG mean per Hello Interview and r/datascience candidate retrospectives. Window functions, self-joins, and metric-definition fluency are assumed; the test is whether the candidate writes correct, readable SQL under time pressure.
Airbnb publishes substantial DS methodology work on medium.com/airbnb-engineering. The experiment-sensitivity post, the experimentation-platform architecture series, and the Trust-and-Safety modeling posts are required reading before the onsite; interviewers reference them.
Founder Mode (the 2024 Brian Chesky operating mode, summarized in Paul Graham's September 2024 essay at paulgraham.com/foundermode) reshaped what senior DS work looks like at Airbnb. Less middle-layer translation, more direct exec engagement on metric definitions and product-decision readouts; the politically-skilled senior DS gets disproportionate scope.

The DS-Analytics vs DS-ML split is the structural fact

The single most important thing a candidate can know before interviewing at Airbnb is that the company runs two functionally distinct DS tracks. The Airbnb Engineering blog has documented this publicly (medium.com/airbnb-engineering; At Airbnb, Data Science Belongs Everywhere); the practical implication for a candidate is that the interview loop, the day-to-day, and the leveling rubric differ between the two tracks.

DS-Analytics (also written DS, Analytics). Owns the experimentation platform readouts, the metric layer, the executive-facing product analytics, and the causal-inference studies that inform large product decisions. Day-to-day: SQL-heavy metric definition, A/B test analysis, opinion-shaping cross-functional partnership with PM and engineering. Strong DS-Analytics work shows up as a metric framework that the company adopts; weak DS-Analytics work shows up as a chart in a doc no one reads.
DS-ML (also written DS, Algorithms or DS, ML). Owns the ranking and pricing and risk models. Day-to-day: model training and evaluation, offline-online metric alignment, eval design, production model rollout. The line between DS-ML and a FAANG-style MLE is thin at Airbnb; the formal distinction is that DS-ML retains DS-style cross-functional partnership and metric-defense responsibility.

What this means for the interview: the SQL phone screen is shared, the behavioral and cross-functional rounds are shared, and the technical deep-dive is track-specific. DS-Analytics candidates get a case study (typically two-sided-marketplace economics or a causal-inference design question) and a stats round (experimentation methodology). DS-ML candidates get an ML system design round and a modeling deep-dive. The recruiter call is when the track gets named; candidates who walk in unsure which track they want lose the recruiter's confidence early.

The teams that ladder up off this split are visible on the Airbnb careers site (careers.airbnb.com/teams/data-science): Search and Discovery, Pricing, Trust and Safety, Host Experience, Growth, AirCover, Co-Hosting, Experiences, Long-Term Stays. Search ranking and Pricing are the most ML-heavy surfaces; Trust and Safety is one of the most causal-inference-heavy (the team has to defend the lift of a policy change on a metric like party-incident-rate without being able to randomize cleanly).

Causal inference at marketplace scale is the senior+ tell

The Airbnb-distinctive interview signal at the senior+ tier is causal-inference fluency. The mechanical reason: Airbnb is a two-sided marketplace, and the standard A/B test machinery from Kohavi-style controlled-experimentation methodology assumes the Stable Unit Treatment Value Assumption (SUTVA). SUTVA holds when treating one unit does not affect any other unit. In a two-sided marketplace it does not hold; if you treat a guest (showing them a different search ranking, or a different cancellation policy), you change which host they book, and you change the availability the host has for the next guest. The Imbens-Rubin causal-inference framework formalizes this; the foundational treatment is the 2015 Imbens and Rubin textbook on causal inference for statistics, social, and biomedical sciences, and the Rubin causal model is documented across the methodological literature on arxiv.org/list/stat.ME (Statistics, Methodology).

What a senior+ DS at Airbnb does about this in practice:

Geo-banded randomization (cluster-randomized experiments). Randomize whole cities or metro areas into treatment and control rather than individual guests. Trades statistical power (n is cities, not users) for SUTVA cleanliness. The pattern is documented on medium.com/airbnb-engineering and in the Microsoft Experimentation Platform body of work (exp-platform.com/Documents/2014 experimentersRulesOfThumb.pdf).
Difference-in-differences for staged rollouts. When a policy is rolled out to one geography first (AirCover's expansion, the Anti-Party Tech tooling), DiD lets you estimate the effect by comparing the treatment region's pre-vs-post change to a comparable control region's pre-vs-post change. The technique handles time-varying confounders that affect both regions equally; it fails when the regions trend differently (the parallel-trends assumption).
Synthetic control for one-off interventions. When only one unit gets treated (a single city, a single host segment), synthetic control builds a weighted combination of untreated units that matches the pre-period of the treated unit; the post-period difference estimates the effect. Originally Abadie-Diamond-Hainmueller; widely deployed at Uber, Lyft, and Airbnb-style marketplaces.
CUPED-style variance reduction. When randomization is clean (geo-banded or single-sided), CUPED (exp-platform.com 2013 paper) reduces metric variance by 30-50 percent on activity metrics by using pre-experiment behavior as a covariate. Airbnb's experimentation-sensitivity work (medium.com/airbnb-engineering) extends this with in-experiment-data variance reduction.

The interview signal: at the IC4 (senior) round and above, candidates are expected to volunteer the SUTVA framing on the marketplace case study. Candidates who default to a clean A/B test framing on a two-sided-marketplace question without flagging the SUTVA risk get downleveled. Candidates who articulate the violation and pick the right method (geo-banded vs DiD vs synthetic control) score the round.

Leveling, comp, and the public-company ABNB equity volatility

Airbnb DS uses an IC2 through IC6 ladder; IC2 is junior (rare external hire), IC3 is mid, IC4 is senior, IC5 is staff, IC6 is principal. Reported total comp per levels.fyi (levels.fyi/companies/airbnb/salaries/data-scientist, 2026 self-reports; sample sparseness is the standard caveat):

IC3 (mid; entry external hire bar). Total comp $190k-$280k. Mix: base $150k-$185k, target bonus 10-15 percent, RSU vesting roughly $30k-$80k/yr.
IC4 (senior; the most common external hire level). Total comp $380k-$580k. Mix: base $200k-$245k, target bonus 15 percent, RSU vesting roughly $150k-$320k/yr.
IC5 (staff). Total comp $520k-$780k. Mix: base $230k-$280k, target bonus 20 percent, RSU vesting $250k-$470k/yr.
IC6 (principal; rare). Total comp $700k-$1.1M. Mix: base $260k-$320k, target bonus 25 percent, RSU vesting $400k-$700k/yr (levels.fyi/companies/airbnb; thin sample at this tier).

The volatility caveat is structural. Airbnb went public on NASDAQ on December 10, 2020 under ticker ABNB. Equity grants are denominated in ABNB shares at the grant-date price, vesting over four years with a one-year cliff (standard public-company structure). Total comp at any tier is therefore the base + bonus (predictable) plus the vesting RSU value at current share price (volatile). ABNB has traded across a wide band since IPO; a candidate with a $400k RSU grant at a $150 grant-day price is worth materially more or less depending on where the stock is when each tranche vests. Refresh grants happen at the annual review cycle for strong performers; these are smaller than the initial grant but compound across a multi-year tenure.

Negotiation tactics that work at Airbnb (per Hello Interview and Reddit r/datascience candidate retrospectives): competing offers from Meta, Stripe, Uber, or DoorDash are taken seriously and frequently produce sign-on or RSU bumps; competing offers from earlier-stage marketplaces are taken less seriously. The base salary band is narrower than the equity band; most of the negotiating room is on the RSU number.

The interview loop, end to end

The Airbnb DS interview is reasonably standardized across both tracks. The version below describes the senior-IC (IC4) loop, which is the most commonly-targeted level for external hires; the more-junior and more-senior loops are calibrated versions of the same shape.

Recruiter call. 30 minutes. Tracks: behavioral fit, motivation, the DS-Analytics vs DS-ML decision, target team if known. The recruiter writes the loop based on this call; candidates who articulate a clear track preference get a coherent loop.
SQL phone screen. 60 minutes, live coding on a shared editor. Two to four problems escalating in difficulty; the hardest reaches window functions, multi-step CTEs, and a deliberately-ambiguous business metric the candidate has to disambiguate before writing the query. Airbnb's bar on this screen is one of the higher ones in industry; candidates who pass the screen advance, candidates who do not are rejected at this gate.
Onsite (virtual; usually 5 rounds). The track determines two of the five rounds.
Case study / product sense (shared). A two-sided-marketplace product question. Common framings: pricing-policy change, search-ranking change, refund-policy change, host-onboarding change. The signal at IC4+ is volunteering the SUTVA / two-sided-effects framing and proposing the right causal-inference method.
Behavioral and cross-functional partnership (shared). Worked examples of cross-functional collaboration; navigating a metric disagreement with a PM, defending a readout to an executive, managing the trade-off between speed of decision and rigor of method.
Technical depth (track-specific). DS-Analytics: experimentation methodology deep-dive (CUPED, SRM detection per exp-platform.com SRM paper, sequential testing per evanmiller.org). DS-ML: ML system design (a ranking system, a pricing model, a fraud-detection pipeline), modeling deep-dive (feature engineering, eval methodology, offline-online alignment).
Cross-functional partnership round (shared). A second behavioral round with the cross-functional partner team (PM, eng manager, or sibling DS). Tests whether the candidate can be partnered with credibly.

Calibration is reportedly tight. Per public Glassdoor reviews and r/datascience candidate retrospectives, the Airbnb DS hiring committee aggregates round scores and pattern-matches against the published leveling rubric; downleveling at offer time is more common than at peer companies (a candidate who interviews at IC4 but scores IC3 will often get an IC3 offer rather than a rejection). The implication: negotiating level is easier with strong cross-functional and stats rounds than with strong technical-depth rounds alone.

What changed under Founder Mode, and what the senior+ work looks like now

In September 2024 Paul Graham published the essay Founder Mode (paulgraham.com/foundermode) describing Brian Chesky's operating shift at Airbnb: tighter founder-IC communication loops, less middle-management translation, more direct exec engagement on product decisions. The essay was widely-read in tech and shaped how candidates and current employees describe the Airbnb operating environment in 2026.

The practical implications for senior+ DS work:

Exec-facing work happens earlier in the seniority arc. A strong IC4 DS at Airbnb in 2026 will present a readout to a VP or to Chesky directly within the first year; that was an IC5+ pattern at FAANG peers. The skill that gets rewarded is the ability to make a metric argument clearly in a 10-minute presentation, not the ability to write a 30-page doc.
Metric definition is more politically loaded. When the founder is reading the metric, the framing of the metric matters. Senior DS who can defend the metric definition (why this metric and not the obvious alternative, what the metric obscures, what its boundary conditions are) earn disproportionate scope.
The middle-translation skill matters less. Senior DS who built their career on being the explainer between the data team and the PM team find that role compressed; the founder talks to the IC directly. The skill that replaces it is direct argument-construction.
Speed of readout matters more. The cadence of decision-making is faster post-2024 than it was in the Airbnb-classic 2018-2022 era. A senior DS who can ship a defensible-enough readout in 2 weeks beats one who ships a rigorous readout in 8 weeks; rigor still matters at the senior bar, but the elasticity of decisions to speed went up.

The honest empty space: exact team headcounts inside Airbnb DS are not public. The names of the internal IC ladders for DS-Analytics versus DS-ML at the very-senior tier (IC5 and IC6) are sparser in public reporting than the more-junior tiers; candidates targeting principal-DS should expect the recruiter to be the source of truth on the leveling rubric at that band.

Frequently asked questions

What's the difference between DS-Analytics and DS-ML at Airbnb?: DS-Analytics owns the metric layer, A/B test analysis, causal-inference studies, and executive-facing product analytics; the day-to-day is SQL-heavy and cross-functional with PM. DS-ML owns ranking, pricing, and trust models; the day-to-day is model training, eval design, and offline-online metric alignment. The interview loops share the SQL screen and the behavioral rounds; the technical-depth round differs. Candidates pick a track in the recruiter call and the loop is built accordingly. The Airbnb Engineering blog (medium.com/airbnb-engineering) has documented the split publicly.
How important is causal-inference fluency for the senior bar?: Load-bearing at IC4+. Airbnb's marketplace structure violates SUTVA (the Stable Unit Treatment Value Assumption from the Rubin causal-inference framework); when a guest is treated, the host they book is implicitly treated. Senior DS articulates this on the marketplace case study and picks the appropriate method: geo-banded randomization for cleaner experiments, difference-in-differences for staged rollouts, synthetic control for one-off interventions. Candidates who default to a clean A/B test framing on a two-sided question without flagging the SUTVA risk get downleveled. The Microsoft Experimentation Platform body of work (exp-platform.com) and Imbens-Rubin causal-inference foundations are canonical prep.
What is the SQL phone screen actually testing?: Reading-comprehension under time pressure, plus correctness. The screen has two to four problems escalating in difficulty; the hardest reaches window functions, multi-step CTEs, and a deliberately-ambiguous business metric the candidate has to disambiguate before writing. The bar is reportedly higher than the FAANG mean per Hello Interview and r/datascience candidate retrospectives. A pattern that fails: candidates who start writing SQL before clarifying the metric definition. A pattern that passes: candidates who restate the question, name the assumption, then write a query that runs.
How does Airbnb compensation compare to FAANG?: Comparable at base; equity volatility is the differentiator. Per levels.fyi/companies/airbnb, IC4 senior DS clusters $380k-$580k total comp, IC5 staff $520k-$780k, IC6 principal $700k-$1.1M. Mix is base + bonus + ABNB RSUs vesting over four years with a one-year cliff. ABNB is public on NASDAQ since December 10, 2020; the comp band is exposed to share-price movement, which means the same nominal RSU grant is worth materially more or less depending on the vesting-day price. FAANG peer comp is comparable in nominal range but lower variance (the equity tickers are larger-cap and historically less volatile than ABNB).
Should I read the Airbnb Engineering blog before the onsite?: Yes, this is one of the strongest preparation moves a candidate can make. The blog (medium.com/airbnb-engineering) publishes substantial DS methodology work; the experiment-sensitivity post on in-experiment-data variance reduction, the experimentation-platform architecture series, and the Trust-and-Safety modeling posts are all directly referenced by interviewers. Candidates who walk into the technical-depth round having read the relevant posts can ground the discussion in real Airbnb work rather than generic methodology. Candidates who have not read the blog tend to lose the round to candidates who have.
Has Founder Mode actually changed the day-to-day for senior DS?: Yes, per candidate retrospectives and current-employee public commentary. The shift summarized in Paul Graham's September 2024 essay (paulgraham.com/foundermode) describes tighter founder-IC loops and less middle-management translation. The practical consequence for senior DS: exec-facing readouts happen earlier in the seniority arc, metric definitions are more politically loaded, and the speed of decision-making is materially faster than in the 2018-2022 era. The skill that gets rewarded is direct argument-construction and metric-defense; the skill that gets compressed is the explainer role between the data team and the PM team.
What teams should I target if I want the highest-impact DS work?: Pricing and Search are the most ML-heavy and the most quantitatively-load-bearing; both have published substantial work on medium.com/airbnb-engineering. Trust and Safety is the most causal-inference-heavy and has been a senior-DS career-accelerator over the past three years (the team has to defend policy-rollout lift on metrics like party-incident-rate where clean randomization is structurally infeasible). AirCover and Co-Hosting are newer surfaces with more open metric definition and therefore more room for a senior DS to define a new metric framework. Host Experience and Long-Term Stays are stable and well-defined; less new-metric room, more execution work.
Do I need a graduate degree for Airbnb DS?: Strongly preferred for DS-Analytics at IC4+, less weighted for DS-ML. The DS-Analytics track values stats-heavy graduate work (MS or PhD in statistics, economics, or quantitative social science) because the senior bar is causal-inference methodology fluency, which is graduate-level material. The DS-ML track values shipping experience over credentialing; strong portfolios with deployed ML systems or substantive open-source contributions clear the bar without a graduate degree. The recruiter call is the right place to ask about credential weighting for the target team.

Sources

About the author. Blake Crosley founded ResumeGeni and writes about data science, machine learning, hiring technology, and ATS optimization. More writing at blakecrosley.com.