Airbnb Intern Phone Interviews: 21 Experiences (Part 7 of 7)

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

Airbnb SWE intern interviews from 2013 to 2021 with no OA mentioned: often two technical rounds; Alien Dictionary, flights and Pour Water repeat.

At a glance

  • Process: Nine had two technical interviews, mostly back-to-back. Seven had a culture or cross-functional round. Three had a single phone interview (H112, H113, H115).
  • Asked in these reports: Alien Dictionary and flight routes three times each; Pour Water and the menu combination sum twice. Five said the code had to compile, pass tests or fully work.
  • Difficulty: LeetCode medium to hard (H97); the hardest interview ever (H101); more original thinking than common problems (H105); not that hard (H107); easy (H112).
  • Practise first: Pour Water, Alien Dictionary and Cheapest Flight with Its Path.

Coverage: 21 software engineer intern candidates whose interview reports mention no OA, from 2013 (H117) to 2021 (H97); seven are from 2018 (H102–H108) and five from 2017. Most were in the United States; H97 was in Beijing, H112 in South Korea, and H102 and H106 gave no place. Eleven got offers (H110 and H112 declined), eight did not, H109 withdrew, and H106 did not say.

In this series

What came up

Fall 2018 is the busiest season, and Pour Water and Alien Dictionary both repeat within it. Counts are out of the 21 reports here.

Task Reports Last seen
Alien Dictionary (LeetCode 269) 3 of 21 Oct 2018 (report date)
Pour Water (LeetCode 755) 2 of 21 Oct 2018
Cheapest Flight with Its Path (LeetCode 787 family) 2 of 21 Nov 2017
Menu Combination Sum (LeetCode 39) 2 of 21 Jan 2017

Asked once each: Texas Hold'em Winners and Minimum Variance Sum Split (H97), Fastest Flight Route and Maze with Keys and Doors (H99), Flatten 2D Vector (H100), Mastermind Solver (H105), Boggle Game (H106), the file system (H107), Palindrome Pairs (H109), Find Lakes (H111), Find the Duplicate Values (H115) and Spiral Matrix Order (H117).

Topics only: graphs (H98), "Zookeeper" (H103), ordering listings (H110), iOS (H116). Values questions: H104, H112.

History (before 2023): 21 interview reports with no OA mentioned

H97: Beijing, poker hands and a variance split

Interview date: May 2021 · Role: Software Engineer (Internship) · Location: Beijing, China · Result: Offer

  1. Technical rounds: two, about LeetCode medium to hard: Texas Poker, Texas Hold'em Winners, and splitting an array for the minimum variance sum, Minimum Variance Sum Split. Names only.
  2. Culture fit: a final round.

H98: Graphs, with code that must run

Interview date: Oct 2020 · Role: Software Development Engineer (SDE) Intern · Location: United States · Result: Offer

  1. Technical interviews: back-to-back, intermediate graph questions; the code had to compile and run. Both interviewers were kind and guided the candidate toward the answer.
  2. Cross-functional: with an interviewer from another team.

H99: Fastest flight and a maze with keys

Interview date: Oct 2019 · Role: Software Engineer (Internship) · Location: Atlanta, Georgia · Result: No offer

  1. Video interviews: two questions in about two hours, one good interviewer and one bad. From a list of airports and flights, get to a destination in the least time: Fastest Flight Route Between Airports. Then a grid maze given as strings, with lowercase keys, uppercase doors and # walls; find the quickest way through: Maze with Keys and Doors.

H100: Career fair, interview the next day

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

  1. A resume left at a career fair led to an interview the next day, in a language of the candidate's choice: an iterator over a 2D array with rows of different lengths, Flatten 2D Vector (LeetCode 251). Nice interviewers; the candidate felt it went badly.

H101: A silent interviewer

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

  1. Technical interview: a question the candidate had never seen on LeetCode, not named. The interviewer stayed silent and gave no hints; the candidate called it the hardest interview they had ever had.

H102: An extra values round, then an offer

Report date: Dec 2018 · Role: SWE intern (bachelor's student) · Result: Offer (posted later)

  1. Applied online. Back-to-back interviews, then a cross-functional round; half a week later HR asked for one more such round, and the candidate wondered whether the first had gone badly. About ten days later they posted the offer. No questions named.

H103: "Zookeeper"

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

  1. The only question listed was the word "Zookeeper", with no round or prompt. The process was organized, with clear next steps and quick replies.

H104: Championing someone else's work

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

  1. Technical interviews: two back-to-back, one question each, not named.
  2. Cross-functional: with an interviewer who could hold any role: When have you championed the mission for someone else?, a time you spoke up for a colleague's work (one of Airbnb's core values).

H105: Mastermind against a server, and pouring water

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

  1. Technical rounds: several, all coding but not plain algorithm drills, and working code was expected, not pseudocode. One: Mastermind Solver, where your solver sends peg guesses to a server that answers with Mastermind's feedback. Another: Pour Water (LeetCode 755), terrain as a 1-D list of heights; find where the water settles.
  2. Cross-functional: with a non-engineer, on culture fit.

H106: Alien Dictionary and a word board

Report date: Oct 2018 · Role: Software Engineer Intern

  1. Phone interviews, back-to-back. First: Alien Dictionary (LeetCode 269). Second: on an n × n letter board, fit the most words from a list at once, no tile used twice: Boggle Game.
  2. Test cases ran at the end, and working code was expected. The candidate believed both had to be solved to pass.

H107: No HashMap for the file system

Interview date: Sep 2018 · Role: Software Engineer (Internship) · Location: Los Angeles, California · Result: No offer

  1. Technical interviews: two back-to-back: Alien Dictionary (H106), then a file system, Design a File System with Paths (LeetCode 1166 family; more detail in Part 6, H80). A HashMap was ruled out as wasteful of space, so the paths went in a tree.
  2. Not that hard, the candidate said, but nerves kept them from finding a bug.

H108: Drop water over Skype

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

  1. Technical: back-to-back over Skype, 50 minutes, a 10-minute break, then 50 more; the code had to compile. One question was "drop water", Pour Water (H105); the other was forgotten.
  2. Culture interview: background and fit. Some recruiters were slow to reply.

H109: Palindrome Pairs, onsite declined

Interview date: Dec 2017 · Role: Software Engineer (Internship) · Location: New York, New York · Result: Withdrew (took another job)

  1. Applied through a recruiter. A week later an email set up a technical interview, on Palindrome Pairs (LeetCode 336), then an onsite invite, skipped for another job.

H110: Ordering listings, out of time

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

  1. A "challenge" at an unnamed stage: sort the listings shown to customers, under constraints not spelled out. Likely the listing pagination task (Part 6, H93), but too little is given to link it. Hard but fun; the candidate ran out of time.

H111: Ticket path with stops, and lakes

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

  1. Technical interviews: two together, about 45 minutes each, one problem plus follow-ups: "stop tickets path", Cheapest Flight with Its Path (LeetCode 787 family), and "find lake", Find Lakes.

H112: South Korea, an easy phone call

Interview date: Sep 2017 · Role: Software Engineer (Internship) · Location: South Korea · Result: Offer (declined)

  1. Applied online; a coordinator set up a basic, fairly easy phone call. The only question listed was "the favorite gift", most likely What is your favorite gift?.

H113: Menu combinations, out in round one

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

  1. Technical phone interview as the first round, with no HR intro call: combination sum told as picking restaurant menu items to hit a total, Menu Combination Sum (LeetCode 39). They did not pass.

H114: Menu, cheapest flight, alien order

Interview date: Dec 2016 · Role: Software engineering intern · Location: San Francisco, California · Result: No offer

  1. Initial round: one 45-minute CoderPad call, code had to compile: all combinations of menu items and prices that sum to K, Menu Combination Sum (H113).
  2. "Onsite" round: two remote 45-minute calls, which started almost 10 and, after Skype trouble, over 20 minutes late. Tasks: the cheapest path through flights given as start, destination and price, Cheapest Flight with Its Path (H111); and the alphabet order behind words sorted in an alien language, Alien Dictionary (H106), which the candidate saw as a topological sort.

H115: Find duplicates on a referral call

Interview date: Oct 2016 · Role: Software Engineer (intern role, per the report) · Location: Berkeley, California · Result: No offer

  1. Phone interview, after a referral by an employee: "find duplicates", most likely Find the Duplicate Values (LeetCode 442 style). It seemed to go well, but no second call came.

H116: An iOS-leaning loop

Interview date: Oct 2016 · Role: Software Engineer (Internship) · Location: San Francisco, California · Result: Offer

  1. Four technical rounds (a phone screen, then three over Skype: two on mobile, one general), then a cross-functional interview. The questions tested iOS knowledge; no task named.

H117: Spiral order, 2013

Interview date: Jan 2013 · Role: Software Engineer Intern · Location: United States · Result: No offer

  1. A recruiter reached out after the resume went in. Print a 2D array in spiral order, top left to top right, down to bottom right, across to bottom left, then inward: Spiral Matrix Order (LeetCode 54).

Patterns across the reports

  1. Code had to run. Five said the code had to compile, pass tests or fully work (H98, H105, H106, H108, H114).
  2. Flights differ in the goal. Fastest route (H99), a ticket path with stops (H111), cheapest path (H114).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

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