Airbnb Intern OA and Phone Screens: 17 Experiences (Part 6 of 7)

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

Airbnb SWE intern reports from fall 2017 to fall 2018: an OA, sometimes a short call about the OA code, then two technical interviews, often back-to-back.

At a glance

  • Process: An OA (HackerRank in 9 of 17; 45 to 60 minutes in H81–H83), then usually two technical interviews (12 reports; 45 minutes where timed) and a culture round in H82, H84, H93, H96.
  • The OA call: Four were quizzed on their own OA code, its running time and how to improve it (H85, H88, H94, H95).
  • Asked in these reports: Listing pagination (H93, H96, likely H88), a huge-collection median (H86, H95), unnamed graph questions (H92, H94, H95).
  • Difficulty: The OA felt easy to medium (H83, H92, H94, H95), or medium on a tight clock (H90). Interviews felt medium to hard (H82, H90, H92).
  • Practise first: Paginate Search Results by Unique Host, Median of a Large Integer Collection and Pour Water.

Coverage: 17 software engineer intern candidates who took the OA and reported what came next. Seven are from January to November 2018 (H80–H86) and ten from September to December 2017 (H87–H96). Fourteen were in the United States, one in the United Kingdom (H83), and H80 and H88 gave no place. Two got offers (H82, H84), H88 passed the OA, and 14 got no offer.

In this series

What came up

Few named their OA task; most named tasks were from interviews. Counts are out of the 17 reports here.

Task or topic Reports Last seen
Graph questions, no task named 3 of 17 Nov 2017
Median of a Large Integer Collection 2 of 17 Jan 2018
Paginate Search Results by Unique Host (plus H88, likely) 2 of 17 Nov 2017

Asked once each: Round Prices to Match Target, Pour Water and the file system (H80; Pour Water likely H84 too), cheapest flights (H83), a board-game winner (H81), tree traversal (H84), dynamic programming (H92), Longest Common Subsequence (H89), Folder Snapshot Diff (H91), the retweet graph (H93), Palindrome Pairs and IP to CIDR (H96).

Behavioral: H87 ("why Airbnb") and H93 (three values questions).

History (before 2023): 17 OA-then-interview reports

H80: Rounding prices, then Pour Water and a file system

Interview date: Oct 2018 (OA), Nov 2018 (phone rounds) · Role: SWE intern (master's student) · Result: No offer

  1. OA: referred 29 October; the "Code Challenge 12" link (the email subject names the set) came 31 October, done 3 November. The task, Round Prices to Match Target: round a list of decimal prices to whole numbers so they sum to a target, changing them as little as possible in total. Prices [1.2, 4.3, 5.8, 6.4] with target 18 give [1, 4, 6, 7]. Approach: round all down, see how many units short the sum is, and round up that many prices with the largest decimal parts.
  2. Phone screens: invited on 6 November; two back-to-back 45-minute video interviews on 13 November.
  3. Round 1: Pour Water (LeetCode 755). An array gives terrain heights; pour a given amount of water at a given spot, then print the terrain as + and the water as w. Example terrain: [3, 1, 3, 2, 4]. Idea: from the pour spot find a low point, fill one unit, repeat. It went badly.
  4. Round 2: Design a File System with Paths (LeetCode 1166 family): add_path(path, value), find_path(path), update_path(path, value). Adding /a/d/b fails if /a/d does not exist; finding or updating a missing path is an error. They used a trie of path parts with an end marker. Follow-up, discussed only: delete a path.
  5. Rejected the next day.

H81: A board-game winner over Skype

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

  1. OA: an online coding challenge of about an hour.
  2. Technical interview: about an hour over Skype, with two employees.
  3. Named, round not given: an algorithm to decide who wins a certain board game, not identified further.

H82: Campus resume drop to offer

Interview date: Oct 2018 · Role: Software Engineer (Internship) · Location: United States · Result: Offer

  1. OA: a resume left at a campus recruiting event brought a HackerRank challenge of about 45 minutes, a week later.
  2. Technical phone interviews: two 45-minute calls with engineers, rated LeetCode medium to hard. No question named.
  3. Culture fit: common behavioral questions plus some about Airbnb and travel, none quoted. HR phoned with the offer; the process felt fast.

H83: Cheapest flights, and an interviewer who kept cutting in

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

  1. OA: one straightforward HackerRank problem in an hour.
  2. Phone screens: two back-to-back, 45 minutes each. The first went well. In the harder second one the interviewer kept interrupting the coding, time ran out, and a rejection followed.
  3. Named, round not given: cheapest flight routes, Cheapest Flight with Its Path (LeetCode 787 family).

H84: Rainfall and a tree, offer sped up

Interview date: May 2018 · Role: Software Engineer (Internship) · Location: United States · Result: Offer

  1. Coding challenge, then two phone rounds and a cross-functional one. A competing offer sped things up.
  2. The named questions, rounds not given: a "rainfall question", most likely Pour Water (LeetCode 755) as in other intern reports then, and a tree traversal.

H85: Asked about OA code a month later

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

  1. OA: a HackerRank challenge, not described.
  2. Phone interview: a month later, on their own OA code: its time complexity and how to improve it. Not having seen it since, they felt unready, and struggled to hear the interviewer.

H86: Median with only an iterator

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

  1. OA: a coding challenge, sent several weeks after an online application.
  2. Follow-up call: 15 minutes, content not given.
  3. Phone interviews: two back-to-back, 45 minutes each. Named: Median of a Large Integer Collection, the median of a very large integer array readable only through an iterator.

H87: A questionnaire before the OA

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

  1. Email questionnaire: after an online application: Why do you want to work for Airbnb? and whether they had US work authorization.
  2. OA: a HackerRank link came next. Nothing more was reported.

H88: A detailed call about the OA solution

Report date: Nov 2017 · Role: SWE intern (master's student) · Result: Passed the OA

  1. OA: referral. Task not named; the follow-ups fit the pagination task (H93), so likely that one.
  2. Follow-up call: restate the problem (mostly forgotten by then) and explain the code. Then the best and worst running time: which input gives each, and how the worst case arises. Then how to improve it (the answer pointed to a linked list and an iterator), what to do if used records were not deleted from the list, and what deleting from an ArrayList costs, and why.
  3. Passed; a phone interview was being scheduled.

H89: Longest common subsequence

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

  1. An online coding test, then a phone interview with basic algorithm and data-structure questions.
  2. Named, round not given: the "infamous" Longest Common Subsequence (LeetCode 1143).

H90: Medium OA with a tight clock

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

  1. OA: one HackerRank problem, usually LeetCode medium in the candidate's view, on a tight clock.
  2. Technical interviews: two back-to-back over Skype and CoderPad, quite difficult. No question named.

H91: Folder diff with a late interviewer

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

  1. OA: soon after an online application.
  2. Technical call 1, one to two weeks later: solved with time to spare.
  3. Technical call 2: the interviewer joined about 15 minutes late and read the problem very fast. As roughly recalled: folders are given as arrays of files; find the files that changed and call a callback on each. That fits Folder Snapshot Diff. Time ran out just before they finished (they believe the late minutes were given back); a failure email came a week later.

H92: DP and graphs, then a surprise rejection

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

  1. OA: one HackerRank challenge at LeetCode easy to medium.
  2. Phone screens: two, at LeetCode medium, on dynamic programming and graphs. No task named.
  3. The interviews felt good and an engineering manager told them good news was coming; a stock rejection came a week on.

H93: Listing pages, a retweet graph and three values questions

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

  1. OA (probably; no rounds given): build pages of n listings from scored listings: higher scores go first, and no listing appears twice. That is the task behind Paginate Search Results by Unique Host (ours keeps one listing per host per page; this report said listings).
  2. Technical interviews: two back-to-back, online, one interviewer unfriendly. One task was Fewest Users to Reach Everyone: followers retweet everything they see, so find the smallest set of users whose tweets reach every user.
  3. Cross-functional: a quick run of personal questions: Describe your most memorable vacation., What is an organization you look up to for doing good? and Describe a time you stood up for something you believe in. Expecting a "why Airbnb" talk, the candidate found it uncomfortable.

H94: Code-review call, then graph traversal

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

  1. OA: HackerRank, not too hard.
  2. Call: 15 minutes going over the OA code and its running time.
  3. Technical calls: two back-to-back, 45 minutes each. Named, round not given: graph traversal.

H95: Graph search and a median you cannot sort

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

  1. OA: after a recruiter's invite to a campus networking event; the HackerRank challenge was straightforward.
  2. Call: 15 minutes with an engineer, walking through the OA code and what they would change.
  3. Technical phone interviews: two back-to-back, 45 minutes each, in CoderPad: graph search (no task named), and the median of an unsorted integer array you cannot index into, so cannot sort. Same task as H86, Median of a Large Integer Collection.

H96: Pagination, Palindrome Pairs and IP to CIDR

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

  1. HackerRank OA about a week after applying, then two 45-minute Skype technical interviews and a hard third that went badly.
  2. Behavioral: 30 minutes of culture-fit questions, none quoted.
  3. Three tasks, rounds not given: paging through entries, as in H93 (Paginate Search Results by Unique Host), likely the OA; Palindrome Pairs (LeetCode 336); and IP to CIDR, IP Range to CIDR Blocks (LeetCode 751).

Patterns across the reports

  1. A call about the OA code. Four had to explain their own OA solution (H85, H88, H94, H95); H94, H95 and H86 (content not given) said 15 minutes.
  2. Two technical interviews, often back-to-back. Twelve of the 17 had two (H80, H82–H84, H86, H90–H96), seven of them back-to-back (H80, H83, H86, H90, H93–H95). H96 got a third.
  3. Interviewer trouble came up in three rejections (H83, H85, H91).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesAirbnb Intern Phone Interviews: 21 Experiences (Part 7 of 7)
0 total reactions. Your reactions: none.

Comments

0

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