Behavioral questions

Airbnb

Tell me about your projects.

BehavioralLast seen May 30, 2023 · Software engineer
Technical impactOwnership

What they're looking for

Whether you can explain what you built, why you built it and what your own part was, clearly and in enough depth for an engineer to follow. In one report it came up in the same round as a design problem, so be ready for technical follow-up questions about your choices.

What works

  • Prepare two projects you can explain at two depths: a one-minute summary and a ten-minute deep dive.
  • For each project, know the problem and who it was for, what you built, your own part, the hardest technical choice and the result.
  • Describe the main pieces (for example the app, the server and the data) in simple words before going into details.
  • Know why you chose your database, framework or algorithm, what else you considered, and what you would change now.
  • Have one concrete outcome ready: number of users, a speed or accuracy figure, or what happened at a demo.
  • In team projects, say clearly which parts were yours.

What hurts

  • Reading your resume line back without adding anything.
  • Choosing a project you cannot explain below the surface, such as one copied mostly from a tutorial.
  • Saying "we" for everything so your own work is unclear.
  • Talking for many minutes without checking whether the interviewer wants more detail or a different project.

Sample answer

Think of your own story first, then compare.