Public preview and process notes

Airbnb Frontend Interview Practice

Airbnb’s careers FAQ gives only the general shape of its process, so the loop here comes from people who interviewed for frontend, front-end-heavy and full-stack roles between 2019 and 2025: a recruiter call, a technical screen that changes from one account to the next, then UI and JavaScript coding, a frontend design round and a deep dive into a past project. The questions they reported follow the rounds, and the first, a card game to build and style, is open to every reader.

13 reported questionsFrontendAtlas practice set: Coding 2 · Concepts 2 · System 1Full practice set requires Premium

Editorial practice groupings, not verified official interview questions or endorsements.

The careers FAQ, linked below, says the process depends on the position and may involve a test, a video or an event, that meeting several people on the current team is a priority, and that Airbnb aims to answer applications within three to four weeks; it also warns about recruiting scams. The rest comes from candidates: anonymous reviews re-posted on Taro from 2022 to 2025, Blind threads from 2021 to 2024, LeetCode posts from 2019 and 2025, and two PracHub pages about 2025 software engineer loops, edited by PracHub and published in August 2026. Several accounts carry a software engineer or full-stack title but describe frontend rounds.

What public interview reports describe

A screen that changes, then coding, design and one project in depth

After the recruiter call, short in a 2025 account, the technical screen is where accounts differ most: a UI build followed by product questions, a LeetCode-hard problem for a candidate whose prep material promised frontend concepts, and, in one poster’s later edit, a common UI component or a design question. The later rounds, a virtual onsite in a 2022 account, are drawn from one or two UI coding rounds in React or plain DOM code, a JavaScript round, a frontend design discussion, a deep dive into a past project and a core values interview or behavioural questions. Most accounts list tasks without naming their round, so the table groups them by type.

  • The card game, styled in the 2025 version, comes from a 2025 staff loop and a 2022 loop and opens the question list; the other builds the accounts name are listed after it. See the UI coding stage
  • Algorithms divide the accounts: none for a 2024 front-end developer in Mexico, not much for a 2022 commenter joining as a senior front end engineer, and a LeetCode-hard problem for two 2025 candidates. See the algorithms stage
  • Slow recruiting comes up in several accounts: almost two weeks to hear back after a 2022 onsite, a final round months after the first in a 2024 senior account, and months of recruiter silence after team matching in another.

Round decoder

The Airbnb UI coding round: what candidates built and how it went

In the UI coding round you build an interface live, in React or with plain DOM code. A 2025 staff frontend candidate and a 2022 front-end engineer were both asked for a card game, and the 2025 prompt asked for styling as well; that question opens the list below and is open to every reader.

The 2025 staff loop had two coding challenges, which the candidate found unrelated to the job. In 2024 a frontend candidate whose loop had a DOM or React round and a separate JavaScript round finished neither before time ran out, and a software engineer who found the loop not difficult advised studying vanilla JavaScript.

Position in the loop
One or two rounds after the technical screen. The rest of the loop can hold a JavaScript round, a design round and a project deep dive, in no order the accounts agree on.
What you build
A card game in a 2025 and a 2022 account, styled as well in the 2025 one. The other builds that accounts name are in the question list, under this round or with no round stated.
Framework
React or plain DOM code in the round list of a 2024 frontend loop. A 2021 onsite had an HTML, CSS and JavaScript round, and a 2022 commenter joining as a senior front end engineer found the interviews mostly JavaScript and CSS with some React.
Length
No account gives this round a length. The 2024 candidate who ran out of time did so in both coding rounds.
Sources
Taro reviews from 2022, 2024 and 2025 and Blind posts from 2021, 2022 and 2024, each listed in the sources at the foot of this page.

Reported interview process

Airbnb frontend interview process

Airbnb's careers FAQ says the process depends on the position, can involve a test, a video or an event, and makes it a priority that candidates meet several people on the current team. Frontend accounts from 2024 and 2025 describe a recruiter call and a technical screen, then UI and JavaScript coding, frontend system design and a deep dive into a past project, with core values or behavioural questions in some loops.

Accounts disagree on algorithms: a 2024 front-end developer had none, while two 2025 candidates got a LeetCode-hard problem. Most accounts list tasks without naming the round, so the rows group them by type and give no order. Several accounts carry a software engineer or full-stack title but describe frontend rounds, and no account of a 2026 frontend interview was found. Sources last checked Nov 2026.

Frontend engineers, mostly 2024 to 2025

StageWhat happensWhoReported by
Recruiter call A short call about your experience, in a 2025 front-end engineer account. Two 2025 candidates were then sent prep material, one of them told to expect frontend concepts and best practices; in 2024 a frontend candidate who asked the recruiter what to expect heard anything in JavaScript, with LeetCode problems as the practice examples. Frontend engineers3 public reports, 2024–2025Newest: Software engineer, United States · Sep 2025
Technical screen 3 reported questions A live coding screen whose content differs from one account to the next. In 2024 the code had to pass every test case, and one interviewer said he would keep adding questions until time ran out. A 2025 full-stack screen gave 40 of its 60 minutes to building UI and the rest to product questions, and a 2025 front-end candidate sent frontend prep material got a LeetCode-hard algorithm problem instead. A 2025 poster's later edit says the screen is a common UI component or a design question, and a 2021 account had two screens in HTML, CSS and JavaScript. Practice: React autocomplete searchFrontend engineers6 public reports, 2021–2025Newest: Software engineer (full-stack), United States · Aug 2025
Coding: UI or React 3 reported questions UI built live, in React or with plain DOM code. A 2025 staff loop and a 2022 front-end loop both built a card game, styled in the 2025 version, and the staff candidate found both of that loop's coding challenges unrelated to the job. A 2024 frontend candidate finished neither the DOM or React round nor the JavaScript round before time ran out, and a 2024 software engineer who found the loop not difficult advised studying vanilla JavaScript. A 2021 onsite had one HTML, CSS and JavaScript round, and a 2022 commenter joining as a senior front end engineer found the interviews mostly JavaScript and CSS with some React. Practice: React tic-tac-toePremium task for this roundFrontend engineers7 public reports, 2021–2025Newest: Staff frontend engineer, United States · Feb 2025
Coding: JavaScript 1 reported question JavaScript coding without a framework. A 2024 frontend loop listed it as a round of its own beside the DOM or React one, a 2024 software engineer had some vanilla JavaScript questions, and a 2024 commenter whose rounds were very frontend-focused was asked about JavaScript fundamentals. In a 2024 senior loop the interviewer gave no feedback and ended the session 15 minutes early. Practice: Frontend fundamentals quizFrontend engineers4 public reports, 2024Newest: Software engineer, United States · Dec 2024
Frontend system design 1 reported question A spoken design of a frontend app or component. A 2024 frontend candidate describes state, data, APIs, trade-offs and optimisations, and in 2022 an Airbnb-badged commenter wrote that you architect a project, one of your own or one the interviewer picks, depending on level. In 2025 a staff candidate felt the design round did not fit the role, and another candidate found the question closer to a devops role than to the front-end-heavy job and its prep packet. Practice: Frontend system design blueprintFrontend engineers6 public reports, 2022–2025Newest: Software engineer, United States · Sep 2025
Experience deep dive One past project discussed in depth, in one account a project the candidate led. A 2025 staff loop had a deep dive into a past project, and in 2024 an Airbnb-badged commenter called it the technical experience interview and believed every engineer gets one. Two 2022 commenters also had an experience round, one of them recalling six interviews in all. Practice: Behavioural storiesFrontend engineers5 public reports, 2022–2025Newest: Staff frontend engineer, United States · Feb 2025
Core values or behavioural A core values interview besides the onsite, in a 2024 account from Mexico. A 2024 senior account lists behavioural questions without giving them, and a 2022 commenter recalled one behavioural interview among six. Practice: Behavioral interview guideSome loops3 public reports, 2022–2024Newest: Front-end developer, Mexico · Dec 2024
Algorithms 1 reported question Accounts disagree. A 2024 front-end developer in Mexico had no algorithms and a 2022 commenter joining as a senior front end engineer not much, while a 2021 onsite had one array problem and an Airbnb-badged commenter listed one LeetCode-medium problem among the frontend interviews in 2022. In 2025 two candidates got a LeetCode-hard problem, one in the technical screen and one as a 45-minute onsite puzzle. Practice: DSA for frontend loopsSome loops6 public reports, 2021–2025Newest: Software engineer, United States · Sep 2025
Team matching Conversations with a few hiring managers after the interviews, in one 2024 senior account. The recruiter then went silent for months despite follow-ups. The one accountOne public report, 2024Newest: Senior software engineer, United States · Dec 2024

4 more reported questions come from sources that do not name the round.

Technical screen: try React autocomplete search now, a free task we picked for this round.

Start the free task

Questions from Airbnb reports

13 questions candidates reported

The first question is open to read; its answer outline opens with a free account. The others show their topic and what is behind the lock; Premium opens all 12 still locked.

Newest account Sep 2025

Locked questions are Premium, but you can open one free with an account: one per account, across all company guides.

  1. 1

    Card game UI

    Open

    Write a simple card game with its interface, and style it as well as making it work. A 2025 staff frontend candidate had it as one of two coding challenges and found both unrelated to the job; a 2022 front-end engineer had to build the interface of a simple card game.

    Coding: UI or ReactUI buildStaff frontend engineer, United States · Reported in 2 accounts · Feb 2025

    Practice: React tic-tac-toePremium task

  2. 2

    Chat app design

    Premium

    Frontend system designFrontend system designStaff frontend engineer, United States · Reported in 2 accounts · Feb 2025

    Behind the lock: the question and a Premium practice task.

  3. 3

    Listing booking widget

    Premium

    Technical screenUI buildSoftware engineer (full-stack), United States · Reported in 1 account · Aug 2025

    Behind the lock: the question and a Premium practice task.

  4. 5

    Form inputs with validators

    Premium

    Coding: UI or ReactUI buildSoftware engineer · Reported in 1 account · Sep 2025

    Behind the lock: the question only. Its practice task is free for everyone.

  5. 6

    Star rating

    Premium

    Round not statedUI buildSenior software engineer, United States · Reported in 1 account · Jun 2024

    Behind the lock: the question and a Premium practice task.

  6. 7

    Currying, callbacks and prototypes

    Premium

    Coding: JavaScriptJavaScriptFrontend engineer · Reported in 1 account · Oct 2024

    Behind the lock: the accounts' description (they do not share the prompt) and a Premium practice task.

  7. 8

    Event loop and closures

    Premium

    Round not statedJavaScriptRole not stated · Reported in 1 account · May 2024

    Behind the lock: the accounts' description (they do not share the prompt) only. Its practice task is free for everyone.

  8. 9

    Class storing a data object

    Premium

    Round not statedJavaScriptSenior software engineer, United States · Reported in 1 account · Jul 2024

    Behind the lock: the question only.

  9. 10

    Data store with change listeners

    Premium

    Technical screenJavaScriptSenior front end engineer · Reported in 1 account · Aug 2019

    Behind the lock: the question and a Premium practice task.

  10. 11

    Backbone model

    Premium

    Round not statedJavaScriptSenior software engineer, United States · Reported in 1 account · Jun 2024

    Behind the lock: the accounts' description (they do not share the prompt) only.

  11. 12

    Retry higher-order function

    Premium

    AlgorithmsJavaScriptSoftware engineer · Reported in 1 account · Sep 2025

    Behind the lock: the question only. Its practice task is free for everyone.

  12. 13

    Sum tree node values

    Premium

    Technical screenAlgorithmSoftware engineer · Reported in 1 account · Sep 2025

    Behind the lock: the question only.

Behavioural questions candidates were asked

Open to everyone: 1 question from 2 public sources.

  • Talk through a past project in depth; in a 2024 frontend loop, a project you led.Reported in 2 accounts · Feb 2025

How to prepare with this grouping

One item for each reported round

Free items first, for the rounds a free task fits; then two Premium items, a small game for the UI coding round, where the open card game sits, and a design case built from a mock.

  1. Free now
    React autocomplete search

    A common UI component, the kind a 2025 poster says the screen can ask for. A 2024 screen counted only code that passed every test case.

  2. Free now
    Frontend fundamentals quiz

    Fifteen minutes on browser rendering, CSS layout, JavaScript and HTTP caching, for the JavaScript round a 2024 frontend loop listed beside its DOM or React round.

  3. Free now
    Frontend system design blueprint

    For the design round, which a 2024 frontend candidate describes as state, data, APIs, trade-offs and optimisations.

  4. Free now
    Behavioural stories

    For the deep dive into one past project, which an Airbnb-badged commenter called the technical experience interview.

  5. Free now
    DSA for frontend loops

    Accounts disagree on algorithms, and two 2025 candidates got a LeetCode-hard problem.

  6. Premium
    React tic-tac-toe

    A turn-based game kept in React state, the nearest task in our library to the card game; our pick, not a reported Airbnb task.

  7. Premium
    UI component and state design from a mock

    Components, state and data worked out from a given screen, for a design round on a frontend app or component.

Published by Airbnb

Official preparation pages from Airbnb

Airbnb publishes these pages itself. They describe the process and expectations in the company's own words; they are not a list of the questions you will be asked, and FrontendAtlas is not affiliated with Airbnb.

PageWhat it coversChecked
Careers FAQWhat the interview process can involve (a test, a video or an event), meeting multiple members of the team, response times and the recruiting-scam warning.Oct 2026

Preparation FAQ

Common questions about Airbnb frontend interviews

Do Airbnb frontend interviews include algorithm questions?

Accounts disagree. A 2024 front-end developer in Mexico had none and a 2022 commenter joining as a senior front end engineer had not much, while a 2021 onsite had one array problem. In 2025 two candidates got a LeetCode-hard problem, one in a technical screen they had been told would cover frontend concepts and one as a 45-minute onsite puzzle. Ask your recruiter which rounds your loop has.

How recent are these accounts?

The newest interviews described took place in 2025, the latest around September. Two PracHub pages about 2025 software engineer loops came out in August 2026, and no account of a 2026 frontend interview was found, so check the current format with your recruiter.

Where do the reported questions come from?

From anonymous reviews re-posted on Taro, Blind threads, LeetCode posts and two PracHub pages edited by PracHub, about interviews from 2019 to 2025. Each question is paraphrased, none is confirmed by Airbnb, and several come from software engineer and full-stack loops, kept because their content is frontend, JavaScript or algorithms.

Try free challenge View pricing

Sources (19)

The links open with a free account. Create a free accountSign in

Each candidate's account describes one loop, not a fixed format.

  • Taro account, May 2025

    Front-end engineer, United States · May 2025

    A public account read for the process table, where it describes the Recruiter call, Technical screen and Algorithms.

  • Taro account, around September 2025

    Software engineer, United States · Sep 2025

    A public account read for the process table, where it describes the Recruiter call, Frontend system design and Algorithms.

  • Blind account, February 2024

    Frontend engineer · Feb 2024

    A public account read for the process table, where it describes the Recruiter call, Technical screen and Coding: JavaScript.

  • PracHub (curated) account, August 2025

    Software engineer (full-stack), United States · Aug 2025

    A public account read for the process table, where it describes the Technical screen.

  • LeetCode account, August 2025

    Frontend engineer · Aug 2025

    A public account read for the process table, where it describes the Technical screen.

  • Blind account, October 2024

    Frontend engineer · Oct 2024

    A public account read for the process table, where it describes the Technical screen, Coding: UI or React, Coding: JavaScript, Frontend system design and Experience deep dive.

  • Blind account, October 2021

    Frontend engineer · Oct 2021

    A public account read for the process table, where it describes the Technical screen, Coding: UI or React and Algorithms.

  • Taro account, February 2025

    Staff frontend engineer, United States · Feb 2025

    A public account read for the process table, where it describes the Coding: UI or React, Frontend system design and Experience deep dive.

  • Taro account, around June 2022

    Front-end engineer, United States · Jun 2022

    A public account read for the process table, where it describes the Coding: UI or React and Frontend system design.

  • Taro account, around December 2024

    Software engineer, United States · Dec 2024

    A public account read for the process table, where it describes the Coding: UI or React and Coding: JavaScript.

  • Taro account, around June 2024

    Senior software engineer, United States · Jun 2024

    A public account read for the process table, where it describes the Coding: UI or React.

  • Blind comment account, April 2022

    Senior front end engineer · Apr 2022

    A public account read for the process table, where it describes the Coding: UI or React, Experience deep dive, Core values or behavioural and Algorithms.

  • Taro account, around July 2024

    Senior software engineer, United States · Jul 2024

    A public account read for the process table, where it describes the Coding: JavaScript.

  • Taro account, December 2024

    Front-end developer, Mexico · Dec 2024

    A public account read for the process table, where it describes the Frontend system design, Core values or behavioural and Algorithms.

  • Blind comment account, February 2022

    Role not stated · Feb 2022

    A public account read for the process table, where it describes the Frontend system design, Experience deep dive and Algorithms.

  • Blind comment account, March 2024

    Role not stated · Mar 2024

    A public account read for the process table, where it describes the Experience deep dive.

  • Taro account, around December 2024

    Senior software engineer, United States · Dec 2024

    A public account read for the process table, where it describes the Core values or behavioural and Team matching.

  • PracHub (curated) account, September 2025

    Software engineer · Sep 2025

    A public account read for three reported questions from the coding: ui or react, algorithms and technical screen.

  • LeetCode account, August 2019

    Senior front end engineer · Aug 2019

    A public account read for one reported question from the technical screen.