Airbnb Campus and Full-Time SWE OA / Interviews: 9 Experiences
- Company
- Airbnb
- Level
- Unknown
- Stages
- OA → Phone screen
Airbnb OA and interview reports from campus candidates with no stated level (2015 to 2023), plus three 2026 full-time multi-level coding assessments.
At a glance
- Process: Campus candidates (2015–2023): an OA, then two back-to-back 45-minute phone interviews (H03, H04). H01 had a technical round, a projects-and-design round and an HR round after the OA. Full-time candidates (2026): one coding assessment in levels, with all three reaching or naming a level 4 (OA 01–OA 03). OA 03 said there were four, each harder than the one before.
- Asked in these reports: Campus: Assigned Parking (H02), Pour Water (H04), Pacific Atlantic Water Flow and a vending machine design (H01), and three recruiter questions (H06). Full-time: none of the three named a task.
- Difficulty: H04 found the coding challenge fairly hard, and its last test case ran too slowly. H05 found the task unusual and not easy, and did not pass. H01's OA was one medium string question that had to pass every test. In 2026, none of the full-time candidates finished every level, and OA 03 found the levels long to read but simple to code.
- Practise first: Assigned Parking, Pour Water, Pacific Atlantic Water Flow and the snack vending machine design.
Coverage: Nine software engineering candidates in two groups, counted separately. Six university candidates who never said whether they were applying as interns or new grads, from September 2015 to May 2023: two in Seattle, one in Berkeley, one elsewhere in the United States, one at an on-campus drive in India and one with no location. Four of them got no offer (H03–H06); H01 and H02 did not say. Three full-time candidates from July and October 2026: one applied for a senior role, and two gave only the Software Engineer title, with no level. None gave a location or a result.
In this article
- Campus candidates, level not reported: six reports, H01–H06, all older than three years.
- Full-Time (2026): three online assessment reports, OA 01–OA 03; one for a senior role, two with no level given.
Candidates who said they were interns are in the Airbnb SWE intern OA / interviews series. Other reports on Airbnb's CodeSignal OA are in the CodeSignal OA roundup.
Campus candidates, level not reported
What came up
No task repeats across these six reports. Four named something; H03 and H05 named nothing. Counts are out of 6.
| Task | Reports | Last seen |
|---|---|---|
| Pacific Atlantic Water Flow (LeetCode 417) | 1 of 6 | May 2023 (report date) |
| Vending machine design | 1 of 6 | May 2023 (report date) |
| An unnamed medium string task | 1 of 6 | May 2023 (report date) |
| Assigned Parking | 1 of 6 | Aug 2022 (report date) |
| Pour Water (LeetCode 755) | 1 of 6 | Nov 2018 |
| Recruiter questions on internships and interests | 1 of 6 | Sep 2015 |
History (before late 2023): 6 campus reports
H01: On-campus OA, two rounds, then HR
Report date: May 2023 · Role: Not stated (on-campus hiring)
OA
- One string question of medium difficulty. The report gives no name or statement. Only candidates whose code passed every test case were shortlisted.
Round 1: technical
- Introductions, then Pacific Atlantic Water Flow (LeetCode 417): in a grid of heights, find every cell from which rain can run off to both the Pacific edge and the Atlantic edge.
- The candidate had to write the complete code, walk through it and state the time complexity.
Round 2: projects and design
- It opened with questions about the candidate's projects (Tell me about your projects.).
- Then a vending machine to design. A buyer picks a product, pays in cash and gets change back, and the machine also has to handle each product's expiry date. The candidate called this system design, but the asks are about classes and behaviour inside one machine: Design a Snack Vending Machine: Cash, Change, and Expiring Stock.
HR round
- The last round was with HR. No questions were given, and neither was the result.
H02: Assigned Parking, question 2 of a campus OA
Report date: Aug 2022 · Role: Not stated · Location: India (on-campus drive)
- The report has no text at all, only pictures of a live HackerRank-style test with a C editor open. They show question 2, Assigned Parking. Question 1, the time limit and the result never appear.
- The task: n cars stand at integer points (x[i], y[i]). Move them so they end up side by side in one horizontal row, in neighbouring cells with no gaps. A car's fuel cost is the distance it travels across plus the distance it travels up or down, |dx| + |dy|. Return the smallest total fuel. n is at most 10^5, and each coordinate lies between -10^9 and 10^9.
- The first example has cars at (1, 1) and (4, 4), for a total of 5: the first car drives right to (3, 1) for 2, and the second drops straight down to (4, 1) for 3.
- Two more samples were on screen. x = [1, 5], y = [1, 5] gives 7. Five cars with x = [4, 6, 4, -4, 1] and y = [-1, 1, -5, -4, 5] give 23.
- The text said the function returns an int, but the C starter code returns a long. With coordinates this large, the total needs 64 bits.
- Readers suggested afterwards putting the row at the median y and then searching over where the row starts on the x axis. One pointed to LeetCode 296 (Best Meeting Point) as a relative.
H03: HackerRank, then two phone interviews under NDA
Interview date: Jan 2019 · Role: Software Engineer · Location: Seattle, Washington · Result: No offer
- Applied on the campus careers page, and a HackerRank test followed.
- Next came two technical phone interviews, back to back, 45 minutes each, in any language the candidate liked. There were two technical questions in all, and the candidate kept them private, citing an NDA (non-disclosure agreement).
- An onsite was meant to come next, but the rejection arrived right after the phone interviews. The candidate still called the experience positive.
H04: A slow last test case, then Pour Water
Interview date: Nov 2018 · Role: Software Development Engineer · Location: United States · Result: No offer
- It started with an Airbnb info session at the candidate's university, mostly about the company's culture and mission.
- The coding challenge was fairly hard. The candidate's solution was too slow on the last test case, yet they still moved on.
- Then came two back-to-back calls with engineers, by phone or Skype. They were told that "success" meant code that ran before the 45 minutes were up. The candidate found that tough and felt the format favoured fast coders.
- The one question listed was Pour Water (LeetCode 755): pour water at a given spot on terrain of uneven heights. The report does not say whether it came in the challenge or in one of the calls.
H05: A non-standard coding challenge, not passed
Interview date: Oct 2018 · Role: Software Engineer · Location: Seattle, Washington · Result: Did not pass the OA
- Applied online as a university student, and a recruiter sent a coding challenge soon after.
- The candidate called the problem unusual and harder than easy, without giving its content. They did not reach the next round.
H06: A 20-minute university recruiting call
Interview date: Sep 2015 · Role: Software Engineer · Location: Berkeley, California · Result: No offer
- A university recruiting coordinator called the candidate. The call took about 20 minutes, and she also introduced some of Airbnb's teams.
- Her general questions covered the candidate's previous internship (Tell me about your previous internship.) and their interests (What are your interests?).
- The one question the candidate wrote down word for word: What is the one thing you don't want from your last internship?
Patterns across the campus reports
- Two 45-minute calls after the OA. H03 (Jan 2019) and H04 (Nov 2018) both had two back-to-back technical calls of 45 minutes once the OA was done. H01's later rounds looked different: one coding round, one projects-and-design round, then HR.
Full-Time (2026)
What came up
None of the three 2026 candidates named a task or even its subject. What they did share is the format, so there is no topic table here.
Online assessments (OA)
OA 01: Into level 4, then waiting
Report date: Oct 2026 · Role: Software Engineer · Platform: Industry Coding Assessment · Status: Waiting to hear back when posted
- The candidate reached level 4 of Airbnb's Industry Coding Assessment, started it and did not finish.
- A few days after submitting, there was no interview call yet. No task details.
OA 02: Three levels done, no time for the fourth
Report date: Oct 2026 · Role: Software Engineer · Platform: Industry Coding Assessment
- Levels 1 to 3 were completed. Time ran out before the candidate could try level 4.
- No task details and no result.
OA 03: Method stubs over four levels, for a senior role
Report date: Jul 2026 · Role: Senior Software Engineer
- The assessment had four levels. At each one the candidate filled in methods in a given code skeleton to match written requirements, and each level was harder than the one before. The report does not name the platform.
- The requirements were long, but the coding itself was simple. The candidate finished two levels and half of the third, and the score shown was 400/600.
- One point held them up for over 20 minutes, until they saw that a new method could call the ones written in earlier levels. They also noted that a failing test for the current method can trace back to data handled by an earlier method.
- Their own lessons: go through every requirement slowly, and expect the clock to be the real limit.
Patterns across the full-time reports
- Four levels, and nobody finished them all. All three reached or named a level 4, and OA 03 said there were four (OA 01–OA 03). OA 01 stopped partway into level 4, OA 02 after level 3, and OA 03 halfway through level 3.
Common questions
How many levels does the Airbnb Industry Coding Assessment have?
Four, by OA 03's count; OA 01 reached level 4 and OA 02 ran out of time before it. None of the three finished every level.
What platform does Airbnb use for its online assessment?
The 2026 full-time candidates named Airbnb's Industry Coding Assessment (OA 01, OA 02); OA 03 described the same leveled format without naming it. Among the older campus reports, H03 named HackerRank and H02 showed a HackerRank-style test.
What comes after the Airbnb OA for university candidates?
Two back-to-back 45-minute phone interviews in H03 and H04 (2018–2019). H01, reported in 2023, had a technical round, a projects-and-design round and an HR round.
Do Airbnb phone interviews need working code?
One candidate was told that a call counted as a success only if the code ran before time was up (H04).
Keep practicing
- Assigned Parking: the car-row fuel task from H02's OA.
- Pour Water: LeetCode 755, the one question in H04.
- Pacific Atlantic Water Flow: LeetCode 417, from H01's first technical round.
- Design a Snack Vending Machine: Cash, Change, and Expiring Stock: the design task from H01's second round.
- Tell me about your projects.: the warm-up in H01's second round.
- What is the one thing you don't want from your last internship?, Tell me about your previous internship. and What are your interests?: the recruiter call in H06.
- Airbnb coding question bank: every Airbnb algorithm problem on FastPrep. Sign-in needed.
- Airbnb behavioral question bank: the recruiter and values questions reported for Airbnb. Sign-in needed.
- Airbnb interview guide: the company overview page.
- Airbnb hiring insights: hiring data for Airbnb.
- Experience feed: roundups for other companies.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.