Is Airbnb still migrating off the Rails monolith?

Largely complete per public Airbnb engineering writing. The migration ran 2017-2020 and is publicly documented; the current architecture has hundreds of Java / Kotlin services with explicit ownership boundaries. Some legacy Rails code persists in less-critical paths, but new backend development is on the SOA platform. Senior+ candidates should be familiar with the migration arc as cited in Newman's Building Microservices.

Do I need Airflow experience to interview at Airbnb?

Helpful for data-platform-team roles, not required for marketplace / search / payments teams. Airflow is now industry-standard, so most engineers have at least worked with it; deep Airflow internals knowledge is only required for the data-platform team itself. The Airflow origin post on the Airbnb engineering blog is helpful context for the cultural conversation.

What's the on-call expectation at Airbnb?

Required at all levels for service-owning teams. Public candidate reports describe weekly rotations with primary and secondary; on-call burden varies materially by team (search and payments teams have heavier on-call; back-office teams have lighter). The bar at hire is articulating a real production incident you debugged and the postmortem you wrote.

Is Airbnb hiring backend engineers in 2026?

Yes per public job postings at careers.airbnb.com. Airbnb has continued hiring through the 2022-2024 reductions; the company's positioning around AI-augmented hosting tools and the Experiences product expansion drive sustained backend hiring. Senior+ backend with marketplace / search-ranking / payments depth is the dominant hiring profile.

Can I work remotely at Airbnb?

Yes — Airbnb explicitly went 'live and work anywhere' in 2022. The careers page lists per-role remote availability; many backend engineering roles are remote within the US (and some globally). The engineering culture is async-friendly with structured sync time per team. Brian Chesky's 2022 letter on remote work is the public reference.

What stack does Airbnb use for new backend services?

Java and Kotlin on the JVM, on top of an internal RPC framework. Public engineering writing describes the migration from Rails to this stack. Some teams use Scala in adjacent services. Senior+ candidates with JVM-tuning fluency and prior microservices-architecture experience pre-screen well.

How LeetCode-heavy is the Airbnb interview?

Moderately heavy per public candidate retrospectives. The phone screen and both onsite coding rounds run medium-to-hard algorithm problems. Comparable to Google's bar; lighter than top-tier HFT; heavier than Stripe or Cloudflare. Engineers should expect to invest 4-8 weeks of LeetCode preparation for the loop.

How much marketplace-domain knowledge is expected before joining?

Helpful but not required. Most Airbnb backend engineers don't come from marketplace backgrounds. The hiring profile weights distributed-systems judgment, JVM fluency, and cross-functional partnership; marketplace-domain knowledge (auctions, two-sided pricing, calendar / availability semantics) is something Airbnb invests in onboarding. Engineers from ride-sharing or large e-commerce companies transfer cleanly.

Backend Engineer Hub

Backend Engineer at Airbnb: Levels, Comp, Interview, and SOA Migration (2026)

By Blake Crosley · Last verified 2026-04-30

In short

Airbnb is the trips-and-experiences marketplace that publicly migrated from a Rails monolith to a service-oriented architecture between 2017 and 2020 — one of the most-cited monolith-to-microservices case studies in the industry. Backend engineers work on the SOA platform (Java / Kotlin services), search and ranking infrastructure, payments, the Airflow-based data platform (Airbnb authored Airflow), and the marketplace-trust systems. Levels run SWE I through Distinguished with senior+ comp commonly clearing $390,000-$1,300,000+ per levels.fyi 2026. The interview is FAANG-shaped with a heavy systems-design and data-platform component.

Key takeaways

Airbnb authored Apache Airflow. The 2015 Airbnb Engineering post (medium.com/airbnb-engineering/airflow-a-workflow-management-platform-46318b977fd8) is the canonical origin reference. Airflow is now the dominant data-pipeline orchestrator industry-wide; backend engineers at Airbnb still work on Airflow-adjacent infrastructure plus the proprietary data platform built on top.
Airbnb's SOA migration (Rails monolith to Java / Kotlin microservices) is publicly documented through the Airbnb engineering blog. The migration ran 2017-2020 and is the canonical case study for incremental decomposition of a large monolith. Newman's Building Microservices 2nd ed cites Airbnb as a reference implementation.
Levels at Airbnb: SWE I through SWE II, IC3 (senior), IC4, IC5 (staff), IC6 (senior staff), IC7 (principal), IC8 (distinguished). Total comp at IC4 commonly $390k-$580k, IC5 commonly $560k-$840k, IC7 commonly $880k-$1.3M+ per levels.fyi 2026 (levels.fyi/companies/airbnb/salaries/software-engineer).
The Airbnb engineering blog (medium.com/airbnb-engineering) is the canonical engineering-culture reference. Topics covered in depth: SOA migration mechanics, search-ranking ML systems, the Airflow origin and evolution, the design system (DLS), and the data-platform infrastructure.
The interview is FAANG-shaped: 4-5 onsite rounds with two coding, one systems design, one behavioral / cross-functional. Senior+ rounds test SOA-migration judgment, search-ranking infrastructure, and the trade-offs between monolith and microservices articulated in Newman's book.
Airbnb's backend hiring bar in 2026 emphasizes large-scale-marketplace experience, search / ranking depth, JVM (Java / Kotlin) fluency, and data-platform judgment. Engineers from large e-commerce, ride-sharing, or similar marketplace companies transfer cleanly.

What backend engineering at Airbnb actually looks like

Airbnb's backend organization is structured around marketplace and platform surfaces:

SOA platform. Java / Kotlin services on top of an internal RPC framework. The migration from the Rails monolith ran 2017-2020 and is publicly documented at medium.com/airbnb-engineering. The current architecture has hundreds of services with explicit ownership boundaries; the bar emphasizes service-design judgment.
Search and ranking. The most production-critical backend surface at Airbnb. Search infrastructure runs on Elasticsearch-derived stores plus proprietary inverted-index work; ranking is a substantial ML-platform investment. Backend engineers here partner with applied scientists on feature pipelines and online-inference systems.
Payments and trust. Multi-currency payments, regulatory compliance, fraud detection. The bar mirrors Stripe's — money-movement-criticality, idempotency, regulatory-driven engineering.
Data platform. Airbnb authored Apache Airflow; the data platform team continues to ship Airflow-adjacent infrastructure plus the proprietary tooling around feature stores, experimentation, and analytics. The Airflow origin post (medium.com/airbnb-engineering/airflow-a-workflow-management-platform-46318b977fd8) is the canonical reference.
Marketplace systems. Listings, calendar / availability, reservations, host onboarding. Each surface is its own service or service cluster post-SOA-migration; engineers here own substantial cross-functional partnership with PM and design.

The engineering org is large (~6,000+ engineers as of 2026 per public Airbnb disclosures, distributed across San Francisco, Seattle, New York, Beijing, and remote regions). The 2022-2023 layoffs and culture shift under CEO Brian Chesky are publicly documented; the backend hiring bar held through the reduction.

The interview at Airbnb: format and what's tested

The Airbnb interview format per public Glassdoor reports, Reddit r/cscareerquestions retrospectives, and the careers page (careers.airbnb.com):

Recruiter screen. 30 minutes. Background, motivation, role alignment.
Technical phone screen. 60 minutes. Live coding on a medium-difficulty algorithm problem. The bar is FAANG-shaped — fluent code in your language of choice with explicit complexity discussion.
Onsite — two coding rounds. 60 minutes each. Medium-to-hard algorithm problems. Public candidate reports describe Airbnb as moderately LeetCode-heavy — comparable to Google, lighter than top-tier HFT but heavier than Stripe.
Onsite — systems-design round. 60-75 minutes. A marketplace-flavored design problem (design Airbnb search, design the calendar / availability system, design a multi-currency payments router, design the reservation-write path with conflict detection). The bar is articulating trade-offs at the SOA-architecture level — service boundaries, data ownership, eventual vs strong consistency.
Onsite — domain / experience round. 60 minutes. Conversation about your past work with a deep technical drill-down on the most relevant project. The interviewer probes scope, decisions, trade-offs, and what you would change.
Onsite — cross-functional / behavioral round. 45-60 minutes. Past work with PM, design, support, finance. Airbnb weights cross-functional partnership highly given the marketplace-PM-density culture.

Senior+ rounds add an extra systems-design or architecture-deep-dive round. The bar at IC5+ is articulating the SOA-vs-monolith trade-offs from Newman's Building Microservices in your own words and citing your own production experience.

Compensation: real bands at Airbnb (levels.fyi 2026)

Total comp at Airbnb for backend SWE (US, per levels.fyi 2026 self-reports — Airbnb is public, so equity is RSU-based at the public-market price plus per-level refresh grants):

Level	Base	Total comp
SWE I (junior)	$145k-$185k	$200k-$290k
SWE II (mid)	$175k-$225k	$280k-$420k
IC3 (senior)	$210k-$275k	$370k-$540k
IC4 (senior+)	$235k-$300k	$390k-$580k
IC5 (staff)	$280k-$355k	$560k-$840k
IC6 (senior staff)	$315k-$400k	$700k-$1.05M
IC7 (principal)	$340k-$430k	$880k-$1.3M+

The reference is levels.fyi (levels.fyi/companies/airbnb/salaries/software-engineer). Airbnb pays at the upper FAANG-adjacent band; equity is RSU-based with quarterly refresh grants per level.

What's load-bearing at Airbnb: the cultural and technical signals

Three signals to demonstrate at the Airbnb interview, drawn from the Airbnb engineering blog and the SOA-migration writing:

SOA / microservices judgment. Airbnb hires for the ability to articulate when monoliths are right and when microservices help. The reference is Newman's Building Microservices 2nd ed (which explicitly recommends "monolith-first" for most companies). Senior+ candidates should be able to walk through Airbnb's actual migration arc and articulate why incremental decomposition worked.
Marketplace and search-ranking depth. Search and ranking are Airbnb's most production-critical backend surface. Engineers from large e-commerce search teams, ride-sharing dispatch / matching teams, or ad-tech ranking infrastructure transfer cleanly. The interview probes ranking-feature-pipeline and online-inference judgment.
Cross-functional partnership. Airbnb has an unusually PM-heavy product culture; backend engineers partner closely with PM and design. The cross-functional round is real; engineers without strong cross-functional examples in their past work struggle to advance.

What's NOT load-bearing at Airbnb: deep ML-research depth (separate org), pure frontend craft (separate org), startup-velocity-over-rigor patterns (the bar emphasizes correctness and scale).

Frequently asked questions

Is Airbnb still migrating off the Rails monolith?: Largely complete per public Airbnb engineering writing. The migration ran 2017-2020 and is publicly documented; the current architecture has hundreds of Java / Kotlin services with explicit ownership boundaries. Some legacy Rails code persists in less-critical paths, but new backend development is on the SOA platform. Senior+ candidates should be familiar with the migration arc as cited in Newman's Building Microservices.
Do I need Airflow experience to interview at Airbnb?: Helpful for data-platform-team roles, not required for marketplace / search / payments teams. Airflow is now industry-standard, so most engineers have at least worked with it; deep Airflow internals knowledge is only required for the data-platform team itself. The Airflow origin post on the Airbnb engineering blog is helpful context for the cultural conversation.
What's the on-call expectation at Airbnb?: Required at all levels for service-owning teams. Public candidate reports describe weekly rotations with primary and secondary; on-call burden varies materially by team (search and payments teams have heavier on-call; back-office teams have lighter). The bar at hire is articulating a real production incident you debugged and the postmortem you wrote.
Is Airbnb hiring backend engineers in 2026?: Yes per public job postings at careers.airbnb.com. Airbnb has continued hiring through the 2022-2024 reductions; the company's positioning around AI-augmented hosting tools and the Experiences product expansion drive sustained backend hiring. Senior+ backend with marketplace / search-ranking / payments depth is the dominant hiring profile.
Can I work remotely at Airbnb?: Yes — Airbnb explicitly went 'live and work anywhere' in 2022. The careers page lists per-role remote availability; many backend engineering roles are remote within the US (and some globally). The engineering culture is async-friendly with structured sync time per team. Brian Chesky's 2022 letter on remote work is the public reference.
What stack does Airbnb use for new backend services?: Java and Kotlin on the JVM, on top of an internal RPC framework. Public engineering writing describes the migration from Rails to this stack. Some teams use Scala in adjacent services. Senior+ candidates with JVM-tuning fluency and prior microservices-architecture experience pre-screen well.
How LeetCode-heavy is the Airbnb interview?: Moderately heavy per public candidate retrospectives. The phone screen and both onsite coding rounds run medium-to-hard algorithm problems. Comparable to Google's bar; lighter than top-tier HFT; heavier than Stripe or Cloudflare. Engineers should expect to invest 4-8 weeks of LeetCode preparation for the loop.
How much marketplace-domain knowledge is expected before joining?: Helpful but not required. Most Airbnb backend engineers don't come from marketplace backgrounds. The hiring profile weights distributed-systems judgment, JVM fluency, and cross-functional partnership; marketplace-domain knowledge (auctions, two-sided pricing, calendar / availability semantics) is something Airbnb invests in onboarding. Engineers from ride-sharing or large e-commerce companies transfer cleanly.

Sources

About the author. Blake Crosley founded ResumeGeni and writes about backend engineering, hiring technology, and ATS optimization. More writing at blakecrosley.com.