Airbnb Intern OA and Onsite Rounds: 16 Experiences (Part 5 of 7)

Shared by janebeingjane ·
Company
Airbnb
Level
Internship
Stages
OA → Phone screen → Onsite

Airbnb SWE intern reports from 2018 to 2022 that went past the OA: usually two technical interviews, often back to back, sometimes then a culture round.

At a glance

  • Process: OA → two technical interviews (11 of 16 reports, back to back in nine) → in five, a last non-coding round (H68, H70, H71, H77, H78). The two 2022 India loops had three rounds after the OA, ending with a managerial or HR round (H64, H65).
  • Asked in these reports: Nine named interview tasks, no two alike, from Pour Water and the 8-puzzle (H76) to Russian Doll Envelopes (H64). Only three reports named an OA task (H64, H65, H67).
  • Difficulty: Opinions on the OA ranged from "pretty easy" (H73) and straightforward (H71) to "pretty difficult" (H68). Interviews were LeetCode medium to hard where rated (H66, H68, H70, H71, H73, H79).
  • Practise first: Pour Water, Alien Dictionary and Design a File System with Paths, each asked again in older interviews in Parts 6 and 7, and Russian Doll Envelopes from a 2022 offer loop.

Coverage: 16 software engineer intern candidates who reported the OA and what came after it (H67: the OA and a practice set). Two are from India in July and August 2022 (H64, H65), two from fall 2021 (H66, H67), nine from 2019 (H68–H76) and three from November 2018 (H77–H79). Thirteen were in the United States, five with a city: San Francisco (H70, H73, H78), Stanford (H76) and Seattle (H79). Six got offers (H64, H65, H68, H70, H77, H78), nine did not (H66, H69, H71–H76, H79), and H67 did not say.

In this series

What came up

No task repeats inside these 16 reports, so each item below is one candidate's (1 of 16). One technique does repeat: ordering by dependencies (H72, H74, H79).

  • OA: Count Palindromic Substrings with extra conditions (H64, Aug 2022), LeetCode 340 (H65, Jul 2022) and LeetCode 166 (H67, Oct 2021 report date; its practice set is not counted).
  • Interview coding: Russian Doll Envelopes (H64, Aug 2022), All O(1) Data Structure (H65, Jul 2022), Merge Event Preferences (H72, Nov 2019), Alien Dictionary and a file system (H74, Oct 2019), brackets and a flight route (H75, Sep 2019), the 8-puzzle and Pour Water (H76, Jan 2019).
  • Design and behavioral: a call-history manager and two project questions (H64); "tell me about a time" questions (H71).

History (before 2023): 16 reports with an OA and later rounds

H64: India on campus, a LeetCode hard onsite, offer

Interview date: Aug 2022 · Role: Software intern (six months) · Location: India, on campus · Result: Offer

  1. OA: two questions the candidate rated medium to hard. One was built on binary search, not described further, and solved fully. The other, solved in part, counted the palindromic substrings of a string under extra conditions that were not given: Count Palindromic Substrings.
  2. Onsite coding: one LeetCode hard, Russian Doll Envelopes (LeetCode 354). The candidate coded an O(n²) dynamic programming answer against two interviewer tests, which had to pass; the larger one needed code changes that took a while. O(n log n) was asked for next, with no time left to write it.
  3. Problem solving: pseudocode and complexity only. Design a call history in time order that keeps just the latest entry per caller (name and phone number), with get and put: Call History Manager. With hints the candidate reached the LRU cache idea.
  4. Managerial: questions on their projects (Tell me about your projects.) and on how they would extend one (How would you add different features to your project?), then database (DBMS) and HR questions.

H65: India off campus, offer within about ten days

Interview date: Jul 2022 · Role: SDE intern (winter internship) · Location: India (work from anywhere) · Result: Offer

  1. OA (14 July, after a referral): 60 minutes, two medium questions. The first, solved fully, was Longest Substring with At Most K Distinct Characters (LeetCode 340): given a string and K, return the length, using a sliding window. The second, a 2-D matrix task done with prefix sums and binary search, was solved in part.
  2. Coding, 45 minutes (16 July): two medium questions, with weight on working code. One used a priority queue and binary search on the answer. The other was a simulation, solved with greedy steps and breadth-first search after a hint.
  3. Technical, 45 minutes (19 July): one hard question, pseudocode preferred: All O(1) Data Structure (LeetCode 432). Keep counts for strings, raise or lower them, and return a string with the lowest or highest count. The first answer ran in O(log n); a hint led to O(1).
  4. Experience and HR, 45 minutes (23 July): projects, core computer science subjects and standard HR questions. The offer followed.

H66: Two coding rounds, then no reply

Interview date: Nov 2021 · Role: Software Engineer Intern · Location: United States · Result: No offer

  1. An OA, not described, then two coding interviews at LeetCode medium level with follow-up questions.
  2. The report lists a culture-fit round the candidate did not take, and the process ended with no reply.

H67: LeetCode 166 in the OA, plus a practice set

Report date: Oct 2021 · Role: SWE intern (bachelor's student)

  1. Applied online. The candidate's own OA was LeetCode 166, Fraction to Recurring Decimal (H12 in Part 2 has the task). Rated average.
  2. With the OA came a timed HackerRank practice set, which the candidate saved as the 2019–2020 bank. As practice, these seven are not counted:

H68: A hard HackerRank OA, then an offer

Interview date: Nov 2019 · Role: Software Engineer (Internship) · Location: United States · Result: Accepted the offer

  1. A resume screen with a recruiter, then a HackerRank OA the candidate found pretty difficult.
  2. Two back-to-back technical questions, LeetCode medium to hard. The report also calls this "the technical screen", so it may have been one call. Then a phone call with someone who was not an engineer. No questions named.

H69: A medium challenge and one coding interview

Interview date: Nov 2019 · Role: Software Engineer (Internship) · Location: United States · Result: No offer

  1. A recruiter sent a coding challenge of medium difficulty within a week. A coding interview followed.
  2. The only question written down was the interviewer's closing "Do you have any questions for me?"

H70: San Francisco, a quick process, offer

Interview date: Nov 2019 · Role: Software Engineer (Internship) · Location: San Francisco, California · Result: Accepted the offer

  1. A HackerRank OA, two technical interviews back to back at about LeetCode medium, then a culture-fit round of standard behavioral questions. The candidate said things moved fast after the OA. No questions named.

H71: A disengaged second interviewer

Interview date: Nov 2019 · Role: Software Engineer (Internship) · Location: United States · Result: No offer

  1. A straightforward HackerRank OA, then two technical phone interviews, LeetCode medium to hard. The candidate felt the second interviewer was disengaged and condescending.
  2. A cross-functional round of many "tell me about a time" questions; no full prompt recorded.

H72: Merge Event Preferences

Interview date: Nov 2019 · Role: Software Engineer (Internship) · Location: United States · Result: No offer

  1. A recruiter call, a HackerRank OA, and two technical interviews back to back a week later. The rejection came three business days after.
  2. The one named task, most likely from the interviews (round not given), was Merge Event Preferences. Given a map from each person to their ordered list of preferred events, return one ordering of the events that keeps everyone's order, or an empty list if the preferences conflict. It has the shape of a topological sort.

H73: An easy OA, then two hard interviews

Interview date: Oct 2019 · Role: Software Engineer (Internship) · Location: San Francisco, California · Result: No offer

  1. A HackerRank OA the candidate found pretty easy.
  2. Two 45-minute technical interviews back to back: a graph problem and a list problem, one LeetCode hard and one medium to hard (which was which is not said). Few hints and no behavioral questions. The first went well; on the second the candidate took a wrong turn.

H74: Alien Dictionary and a file system

Interview date: Oct 2019 · Role: Software Engineer (Internship) · Location: United States · Result: No offer

  1. The OA arrived the day after applying, and the interview invite the day it was done.
  2. Two 45-minute technical interviews back to back: Alien Dictionary (LeetCode 269) and "file systems", Design a File System with Paths. Only names were given, not the order or the file-system operations.

H75: Brackets and a flight route over video

Interview date: Sep 2019 · Role: Software Engineer (Internship) · Location: United States · Result: No offer

  1. The coding challenge came within two weeks of applying; its task was not described.
  2. Two 45-minute video interviews, back to back, in a shared code editor: Balanced Brackets (LeetCode 20 style) and a shortest flight path, Fastest Flight Route Between Airports. Only names were given; "shortest" could mean fewest flights or lowest cost.
  3. The first interviewer came late and counted his intro against the candidate's time.

H76: The 8-puzzle and Pour Water

Interview date: Jan 2019 · Role: Software Engineer (Internship) · Location: Stanford, California · Result: No offer

  1. OA: HackerRank, two questions: a quick easy opener, then a far longer one that called for hash maps. Neither was named.
  2. Phone screen 1 (the two screens ran back to back): build the 8-puzzle "from scratch", the 3 × 3 sliding-tile puzzle: 8-Puzzle Solver. LeetCode 773 is a 2 × 3 version. Whether "from scratch" meant the solver or the game is not said.
  3. Phone screen 2: Pour Water (LeetCode 755). Print a terrain from an array of heights, then pour water at one position and print it again with the water.

H77: Five weeks from OA to offer

Interview date: Nov 2018 · Role: Software Engineer (Internship) · Location: United States · Result: Accepted the offer

  1. A HackerRank coding question on 9 November, two back-to-back technical interviews on 19 November, and two cross-functional rounds on 28 November and 6 December. The offer came on 14 December. No questions named.

H78: Recursion and a quicksort twist, offer

Interview date: Nov 2018 · Role: Software Engineer (Internship) · Location: San Francisco, California · Result: Accepted the offer

  1. A coding challenge, two technical interviews back to back, then a cultural interview.
  2. Two problems were named only by type, from the challenge or the interviews (not said): a medium recursion problem, and a hard quicksort variant that the candidate rated very tough to reason about and unlike any textbook version.

H79: One medium HackerRank question, then Skype

Interview date: Nov 2018 · Role: Software Engineer (Internship) · Location: Seattle, Washington · Result: No offer

  1. The application went in via a university recruiter. A week later came one medium HackerRank question.
  2. Two back-to-back technical interviews over Skype, medium and then hard. The report lists one graph question solved with a topological sort, without saying whether it was the OA or an interview.

Patterns across the reports

  1. Two technical interviews after the OA. Eleven reports had them (H66, H70–H79), back to back in nine (H70, H72–H79). H69 had one, and H68 reported two back-to-back technical questions. Where a length was given it was 45 minutes (H73–H75, and the H65 rounds).
  2. A non-coding round came last, and most who reached it got offers. Five US reports ended with one: culture fit or cross-functional in H70, H71, H77 and H78, and a call with a non-engineer in H68. Four of the five accepted offers; H71 did not get one.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesAirbnb Intern OA and Phone Screens: 17 Experiences (Part 6 of 7)
0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.