← Back to Directory

Airbnb

Large Enterprises

Most of these Airbnb write-ups come from Software Engineers (58), then Machine Learning Engineers (16) and Backend Engineers (2). The most reported rounds are the technical phone screen (37), the system design round (24), the behavioral / leadership round (6) and the onsite coding round (6).

76 interview notes · updated Jun 2026

Airbnb·Software Engineer·Technical Phone Screen

Jun 2026
Airbnb SWE interview, one coding question the whole time. The interviewer skipped pleasantries and jumped straight in, which set a pretty tense pace. Ran out of time before finishing the test cases, which stings in retrospect.
  • Given a set of properties in a neighborhood, each with a certain capacity, find the optimal combination of properties that can accommodate a specified group size. Minimize total capacity first; if there's a tie on capacity, prefer the combination with fewer properties.

“The priority ordering tripped me up more than I expected.”

View Post

Airbnb·Machine Learning Engineer·Online Assessment (OA)

Jun 2026
Coding round for an MLE role at Airbnb. You get handed a few files and have to manually implement fit and transform methods, then debug and optimize under separate time blocks. Nothing exotic if you write production ML code regularly.
  • Given a set of provided files (including a run script and evaluation script), manually implement the fit and transform methods of an ML transformer so the pipeline runs correctly, then optimize it within a fixed time limit.

“Two phases: 25 minutes to get it working, 35 minutes to make it faster.”

View Post

Airbnb·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Airbnb coding round, one problem that builds on a previous terrain simulation. The water-pouring piece is the harder extension and it's where most people seem to get stuck.
  • Given a terrain heights array, a pour column, and a volume, simulate pouring that many units of water at the given column. Each unit flows to the lowest adjacent available spot (left preferred over right), accumulates realistically, and at the end you print the grid showing terrain, water, and air.

“This was the second part of a two-part problem so I came in thinking I had momentum.”

View Post

Airbnb·Machine Learning Engineer·Onsite - Coding / Algorithms

Jun 2026
Coding round for an MLE role at Airbnb. One algorithmic problem, but the float precision angle made it messier than a standard coin change question.
  • Given a set of coin denominations expressed as floats (e.g. 0.25, 0.5, 1.0), determine whether a target value can be made up exactly, or find the minimum number of coins needed.

“Jumped straight into DP with floats and it blew up in my face.”

View Post

Airbnb·Software Engineer·Technical Phone Screen

Jun 2026
Airbnb coding round, one meaty problem about finding valid listing pairs that together cover a requested date range. The problem sounds straightforward until you actually try to make it efficient.
  • Given n listings each with a set of available dates, and a requested range [start_date, end_date], find all distinct ordered pairs (A, B) where you can stay at A for a contiguous prefix of the range and then move to B for the rest, with no gaps or overlaps. How do you represent availability and efficiently scan for valid split points?

“My first instinct was to just iterate over every pair and every possible split point k, which is obviously O(n^2 * days) and they were not impressed.”

View Post

Airbnb·Software Engineer·Technical Phone Screen

Jun 2026
Airbnb SWE interview with a box traversal problem that required OOD thinking, not just a working solution. Passed all test cases and still got rejected, which honestly says a lot about how subjective these rounds can be.
  • You start with one box in a house. Each box can contain keys, sub-boxes, and candies. Keys unlock boxes that are otherwise locked. Some boxes are already open. Find the maximum number of candies you can collect.

“They wanted a full Box class before touching any traversal logic.”

View Post

Airbnb·Software Engineer·Technical Phone Screen

Jun 2026
Airbnb software engineer interview with a tricky permutation problem that looks deceptively clean on the surface but has enough edge cases to really trip you up if you go in without a clear plan.
  • Given a multiset of digits and a lower bound integer, return the smallest number you can form by permuting those digits that is still greater than or equal to the lower bound. Return -1 if no valid permutation exists.

“The greedy approach clicked for me pretty fast: walk left to right through the lower bound's digits, at each position try to slot in the smallest available digit that's at least as large as the corresponding bound digit.”

View Post

Airbnb·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Airbnb system design round, calendar service question. Pretty dense scope and I kept second-guessing how deep to go on each component before they nudged me to keep moving.
  • Design a calendar service similar to Google Calendar. Walk through your approach to the full system including storage, recurring events, notifications, and sharing.

“This question is deceptively wide.”

View Post

Airbnb·Backend Engineer·Onsite - Coding / Algorithms

Jun 2026
Code review round at Airbnb for a backend role. Three PRs of increasing difficulty, and they wanted you to go deep on architecture, correctness, concurrency, and whether you'd actually merge the thing.
  • Given a pull request, how would you critique its architecture and design at a high level, focusing on separation of concerns, layering, and API contracts?
  • Looking at the same PR, identify any correctness issues: silent failures, swallowed exceptions, null returns where errors should propagate, or off-by-one bugs.
  • In the context of the PR, what concurrency issues can you identify? Think race conditions, missing locks, non-atomic check-then-act sequences, and shared mutable state.
  • Would you accept, request changes on, or reject this PR? Justify your decision with reference to testability and long-term maintainability.

“This was the part I felt most comfortable with, but I still fumbled a bit by jumping straight into line-level stuff before stepping back.”

View Post

Airbnb·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Airbnb ML engineer interview with a coding problem that's basically coin change dressed up in a travel scenario. Cute theming, but the float arithmetic gotcha is what separates people who've seen this before from people who haven't.
  • You have an X-hour layover in Paris and want to fill it exactly with Airbnb experiences. Given a list of experience durations (in hours, one decimal place), and the ability to book the same experience multiple times, find the minimum number of bookings that sum to exactly X hours. Return -1 if it's impossible.

“So it's unbounded coin change, minimum coins, but with decimal values instead of integers.”

View Post

Airbnb interview FAQ

What rounds are in the Airbnb interview?

Candidates most often report a technical phone screen (37 write-ups), a system design round (24), a behavioral / leadership round (6) and an onsite coding round (6).

What does the Airbnb technical phone screen cover?

Across 37 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (37 questions), Technical Trade-offs (29) and System Design (9).

What is asked in the Airbnb system design round?

Across 24 system design write-ups, the most tagged question topics are System Design (58 questions), Technical Trade-offs (54) and Data Modeling (21).

Airbnb interview guides by role

58 notes

Airbnb Software Engineer interview questions

16 notes

Airbnb Machine Learning Engineer interview questions