Is Airbnb really fully remote with the Live and Work Anywhere policy?

Yes for most US SWE roles, with quarterly in-person collaboration weeks at hubs (San Francisco HQ, NYC, Seattle) for team alignment. Specific roles requiring on-site (some hardware, some operations) explicitly note this. Per news.airbnb.com/live-and-work-anywhere/, employees can work internationally up to 90 days/year without HR friction; longer requires more coordination. The policy has been stable since 2022.

What languages do Airbnb engineers actually use day-to-day?

Front-end: TypeScript + React (with Airbnb's published style guide). Backend services: Kotlin (primary in 2026, migrated from Java/Ruby/Scala over the past few years), with some Java legacy and some Python for ML. Data: Python + Scala + Spark + Airflow (Airbnb's open-sourced workflow scheduler). Mobile: Swift (iOS), Kotlin (Android), native (post-2018 deprecation of React Native). Engineers from JavaScript / Python / Java backgrounds ramp easily.

How does Airbnb's design-engineering interview differ from a normal front-end interview?

Three differences: (1) the coding round often involves building a small UI component with attention to accessibility, animation, and state management — not just algorithmic correctness; (2) the cross-functional round explicitly probes collaboration with designers; (3) the system-design round for senior front-end candidates focuses more on design-system architecture and component-library scaling than pure backend distributed systems. References to specific Figma usage, motion design, and design-token systems are positive signals.

Why did Airbnb deprecate React Native?

Documented in five blog posts at react.airbnbeng.com (2018). Summary: React Native added complexity to mobile-engineering team structure (cross-platform team + per-platform team coordination), didn't deliver as much code-share as projected (~30%, not 80%), and made platform-specific feature work harder. Engineers shipping iOS-specific or Android-specific features needed to know native anyway. Net trade-off favored returning to native. The decision is a frequent topic in mobile-SWE interviews; Airbnb expects candidates to have an opinion on cross-platform vs native trade-offs.

What's Airbnb's bonus and equity refresher cycle like?

Annual performance reviews drive bonus and refresher equity. Top performers ('Significantly Exceeds') receive materially larger refreshers. Bonus targets are typically 10-20% of base for SWE roles, varying by level. Refresher equity stacks year-over-year, so total annual comp grows with tenure even without promotion.

Does Airbnb sponsor visas?

Yes. Airbnb sponsors H-1B, O-1, TN, STEM OPT and EU equivalents. Per careers.airbnb.com immigration FAQ, sponsorship is available for most SWE roles. Specific role/country combinations vary; ask the recruiter.

Is the cross-functional round just behavioral or is there real evaluation?

Real evaluation. Interviewers are typically the design and PM partners the candidate would work with; they grade for collaboration skill, communication clarity, and design-thinking. The signal is 'will this engineer be a productive partner', not just 'do they have good vibes'. Bring concrete examples with specific cross-functional names and outcomes.

How does Airbnb handle the design-engineering vs traditional front-end track?

Both tracks exist; design-engineering is somewhat smaller and more specialized. Design-engineers focus on the visual/interaction layer (motion, accessibility, design-system architecture); traditional front-end focuses on application-layer logic and data fetching. Both can reach L5+. The interview path is similar but with weight differences in the coding round (design-engineering coding emphasizes craft; front-end coding emphasizes correctness + performance).

Software Engineer Hub

Software Engineer at Airbnb (2026)

By Blake Crosley · Last verified 2026-04-29

In short

Airbnb is unusual among large tech companies for its design-engineering culture: front-end engineers are expected to ship at craft level on UX/visual fidelity, and the design-systems org has more weight than at peer companies. The primary stack is TypeScript + React with Airbnb's open-sourced JavaScript style guide (github.com/airbnb/javascript), Kotlin/Java for backend services, Python and Scala for data, Swift / Kotlin for mobile. Senior (L5) total comp clusters $360k-$510k per levels.fyi/companies/airbnb. Airbnb operates a unique 'Live and Work Anywhere' policy with hybrid hub-based defaults.

Key takeaways

Airbnb's open-sourced JavaScript style guide (github.com/airbnb/javascript, ~145k stars) and React style guide are widely adopted industry standards — written by Airbnb engineers, reflecting their actual conventions.
Front-end engineering at Airbnb has higher craft expectations than at peer FAANG — design-systems work, Figma fluency, and motion/animation skill are explicit hiring signals (per Airbnb design-engineering posts at airbnb.design).
Airbnb operates 'Live and Work Anywhere' (announced 2022): employees can work from anywhere in their employed country with no salary cut; hub-based offices in San Francisco (HQ), NYC, and Seattle for collaboration weeks.
Senior (L5) total comp $360k-$510k per levels.fyi/companies/airbnb/salaries/software-engineer/levels/l5; staff (L6) $530k-$760k.
Airbnb's interview process includes a cross-functional partner round emphasizing design-engineering collaboration — front-end candidates should expect to discuss past work with PM/design partners specifically.
Airbnb's React Native investment (and 2018 deprecation, react.airbnbeng.com '5 epic things we learned') is engineering-blog canon — useful pre-interview reading for mobile candidates.

Where Airbnb SWEs work — products and infrastructure

From careers.airbnb.com (verified 2026-04-27):

Guest experience. Search, listings, booking flow, payments. The historical core; large engineering footprint.
Host tools. Listing management, calendar, pricing, automation, reviews. Ships on web + mobile.
Trust & Safety. Identity verification, fraud detection, dispute resolution, content moderation. ML-heavy.
Mobile (iOS / Android). Native apps with substantial engineering investment; Airbnb famously deprecated React Native in 2018 (react.airbnbeng.com) and returned to native, citing developer experience and platform-specific feature parity.
Payments & Money Movement. Multi-currency, payouts, regulatory compliance across 100+ countries. Heavy engineering complexity.
Data Infrastructure. Spark, Hadoop, Airflow (which Airbnb invented at airbnb.io and donated to Apache), Druid for OLAP. The data stack at Airbnb is documented heavily.
Search & Discovery. Search ranking, recommendations, ML platform. Large team; ML-heavy.
Experiences (offerings beyond stays). Activities, services. Smaller team but distinct engineering surface.
Internal Tools / DevPlatform. Build infrastructure, deploy systems, observability tooling, internal IDE. Documented in airbnb.io.

Airbnb's engineering blog (medium.com/airbnb-engineering and airbnb.io) is one of the more substantive in tech — posts on Apache Airflow, Apache Superset (which Airbnb open-sourced), and the design-systems work are required pre-interview reading.

The design-engineering culture (what makes Airbnb unusual)

Airbnb is the most design-driven of major tech companies. The CEO, Brian Chesky, came from RISD design background; the company has historically structured itself with design as a peer to engineering and product (rather than reporting into product). The implications for SWE candidates:

Front-end engineers are expected to ship at craft level. Pixel-perfect implementation, motion/animation fluency, and Figma-to-code translation are explicit interview signals. Reference: airbnb.design/dls (the Airbnb Design Language System) is the published artifact.
The 'design-engineering' role exists. A dedicated track for engineers who specialize in the design-implementation interface. More common at Airbnb than at peer FAANG.
Design reviews are weight-bearing. Engineers participate in design reviews as full partners; pushback on design decisions is expected and respected.
Cross-functional partner round in interviews. Front-end candidates have an explicit round where they discuss collaboration with designers and PMs; this is a real signal, not a checkbox.

For backend / infrastructure SWEs, the design-engineering culture is less load-bearing day-to-day, but the cross-functional ethos still applies. Engineers are expected to articulate trade-offs to non-technical partners.

Interview process from public sources

Airbnb's process per careers.airbnb.com and candidate reports on Glassdoor / interviewing.io:

Recruiter screen (30 min). Background, motivation, role-fit.
Technical phone screen (45-60 min). Coding problem; for front-end roles, often a small UI implementation challenge in CodeSandbox or a similar tool.
On-site (4-5 rounds, ~5 hours):

Coding rounds (1-2). Standard algorithmic problems plus, for front-end candidates, a UI-focused coding round (build a small component, handle state, accessibility).
System design round (L5+). Standard format. Airbnb's interviewers tend to emphasize practical scaling questions and trade-offs over theoretical depth.
Cross-functional partner round. The Airbnb-specific round. Discuss past projects with focus on collaboration — how did you work with design? PM? other engineers? what conflicts did you resolve? Star/SAR framing helps.
Culture-fit round (sometimes called the 'core values' round). Behavioral, with focus on alignment to Airbnb's published values (be a host, champion the mission, embrace adventure, etc.). Reference: airbnb.com/careers values page.

Front-end-specific signals: craft-level implementation in the coding round, design-systems thinking in cross-functional, motion/animation fluency are graded. The 'I'm a backend engineer who can do front-end' framing is a weak signal at Airbnb; specialists outperform generalists in front-end interviews.

Compensation and the 'Live and Work Anywhere' model

Airbnb publishes US salary ranges per pay-transparency laws on individual postings. Aggregated levels.fyi:

L3 (junior): ~$155k base, $220k-$300k total.
L4 (mid): ~$190k base, $280k-$390k total.
L5 (senior): ~$220k base, $360k-$510k total per levels.fyi/companies/airbnb/salaries/software-engineer/levels/l5.
L6 (staff): ~$280k base, $530k-$760k total.
L7 (senior staff): ~$320k base, $700k-$1M+ total.

Live and Work Anywhere (announced April 2022, ongoing in 2026): Airbnb employees can live and work from anywhere in their employed country with no pay cut based on location. Employees can also work internationally up to 90 days per year without administrative friction. Reference: news.airbnb.com/live-and-work-anywhere/.

This is structurally different from most peer companies. Meta and Google adjust pay by location (a Salt Lake City SWE earns less than a SF SWE); Airbnb does not. The implications: Airbnb attracts engineers who prioritize geographic flexibility, and Airbnb's pay-band is consistent across US locations. Quarterly in-person 'collaboration weeks' (3-5 days) at hubs are expected; otherwise remote.

Equity: Airbnb went public December 2020 (NASDAQ: ABNB). RSUs vest 25/25/25/25 over 4 years. Stock has been volatile post-IPO; comp at vest can swing materially.

Frequently asked questions

Is Airbnb really fully remote with the Live and Work Anywhere policy?: Yes for most US SWE roles, with quarterly in-person collaboration weeks at hubs (San Francisco HQ, NYC, Seattle) for team alignment. Specific roles requiring on-site (some hardware, some operations) explicitly note this. Per news.airbnb.com/live-and-work-anywhere/, employees can work internationally up to 90 days/year without HR friction; longer requires more coordination. The policy has been stable since 2022.
What languages do Airbnb engineers actually use day-to-day?: Front-end: TypeScript + React (with Airbnb's published style guide). Backend services: Kotlin (primary in 2026, migrated from Java/Ruby/Scala over the past few years), with some Java legacy and some Python for ML. Data: Python + Scala + Spark + Airflow (Airbnb's open-sourced workflow scheduler). Mobile: Swift (iOS), Kotlin (Android), native (post-2018 deprecation of React Native). Engineers from JavaScript / Python / Java backgrounds ramp easily.
How does Airbnb's design-engineering interview differ from a normal front-end interview?: Three differences: (1) the coding round often involves building a small UI component with attention to accessibility, animation, and state management — not just algorithmic correctness; (2) the cross-functional round explicitly probes collaboration with designers; (3) the system-design round for senior front-end candidates focuses more on design-system architecture and component-library scaling than pure backend distributed systems. References to specific Figma usage, motion design, and design-token systems are positive signals.
Why did Airbnb deprecate React Native?: Documented in five blog posts at react.airbnbeng.com (2018). Summary: React Native added complexity to mobile-engineering team structure (cross-platform team + per-platform team coordination), didn't deliver as much code-share as projected (~30%, not 80%), and made platform-specific feature work harder. Engineers shipping iOS-specific or Android-specific features needed to know native anyway. Net trade-off favored returning to native. The decision is a frequent topic in mobile-SWE interviews; Airbnb expects candidates to have an opinion on cross-platform vs native trade-offs.
What's Airbnb's bonus and equity refresher cycle like?: Annual performance reviews drive bonus and refresher equity. Top performers ('Significantly Exceeds') receive materially larger refreshers. Bonus targets are typically 10-20% of base for SWE roles, varying by level. Refresher equity stacks year-over-year, so total annual comp grows with tenure even without promotion.
Does Airbnb sponsor visas?: Yes. Airbnb sponsors H-1B, O-1, TN, STEM OPT and EU equivalents. Per careers.airbnb.com immigration FAQ, sponsorship is available for most SWE roles. Specific role/country combinations vary; ask the recruiter.
Is the cross-functional round just behavioral or is there real evaluation?: Real evaluation. Interviewers are typically the design and PM partners the candidate would work with; they grade for collaboration skill, communication clarity, and design-thinking. The signal is 'will this engineer be a productive partner', not just 'do they have good vibes'. Bring concrete examples with specific cross-functional names and outcomes.
How does Airbnb handle the design-engineering vs traditional front-end track?: Both tracks exist; design-engineering is somewhat smaller and more specialized. Design-engineers focus on the visual/interaction layer (motion, accessibility, design-system architecture); traditional front-end focuses on application-layer logic and data fetching. Both can reach L5+. The interview path is similar but with weight differences in the coding round (design-engineering coding emphasizes craft; front-end coding emphasizes correctness + performance).

Sources

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