Behavioral questions

Airbnb

How would you add different features to your project?

BehavioralLast seen Sep 23, 2022 · Software engineer
Technical impactPrioritization

What they're looking for

Whether you understand a project you built well enough to grow it. This question follows on from a project you have already described: the interviewer wants to hear which features you would add, why those, and what would have to change in the design, the data and the tests to support them. They listen for clear reasoning about trade-offs and for whether you think about the people who would use the new features.

What works

  • Talk about a project you know end to end, including the parts a teammate built, because the discussion can go into any layer.
  • Before naming features, say who uses the project and what they are missing today; let that choose the features.
  • Offer two or three ideas, then go deep on one: what changes in the data model, the interface or API, and the storage.
  • Name the costs: what gets slower, harder to test or more expensive, and how you would keep existing behavior working.
  • Say how you would ship it in small steps and how you would know it worked: tests, a number to watch, or feedback from users.
  • Treat it as a conversation: think out loud and adjust when the interviewer adds a new requirement or constraint.

What hurts

  • Listing many features with no reason for them and no design behind them.
  • Proposing to rewrite the whole project instead of building on what exists.
  • Naming a popular technology as the feature without saying what problem it solves for the user.
  • Not knowing how the current version works, so the new feature has nothing to stand on.

Sample answer

Think of your own story first, then compare.