Behavioral questions

Adobe

For a project on your resume, why did you choose its architecture, what were the trade-offs, and how would you scale it further?

BehavioralLast seen Jul 28, 2026 · Software engineer
Technical impactOwnership

Also asked as

  • Why did you choose your current architecture, what are its trade-offs, and how would it behave at scale?

What they're looking for

The interviewer is checking that you understand the projects on your resume deeply, not just the parts you touched. They want the reasons behind the main design choices, the options you rejected and why, the costs you accepted, and a realistic plan for the next order of magnitude. Expect follow-up questions on every claim, so pick a project you know well.

What works

  • Open with a two-sentence summary: what the system does, its load and your role.
  • For each big choice (storage, communication, data model), give the alternative you considered and why you did not pick it.
  • Name the trade-off honestly, such as weaker consistency or higher cost, and how you lived with it.
  • For scaling, say which part breaks first and what you would change, with rough numbers.

What hurts

  • Listing technologies without explaining why they were chosen.
  • Claiming the design has no downsides.
  • Answering 'add more servers' without saying what the real bottleneck is.

Sample answer

Think of your own story first, then compare.