Behavioral questions

Figma

Walk me through one of your projects: its goal, its scope and its impact.

BehavioralLast seen Oct 26, 2026 · Software engineer
Technical impactOwnership

What they're looking for

The interviewer wants to understand one of your projects the way a manager would: what it was trying to achieve, how big it was, what you owned, and what changed because of it. They listen for whether you can explain the goal in plain words, keep the scope clear, and back up the impact with evidence. A strong answer is short and well organized, uses a project close to the role, and leaves room for questions.

What works

  • Open with the goal in one or two sentences that a non-engineer could follow.
  • Describe the scope: the team size, how long it took, what was in and what was out, and which part was yours.
  • Give impact as numbers or concrete user changes, and say how you measured them.
  • Pick a project close to the work of the team you are interviewing with, since that makes the discussion more useful.
  • Keep the first pass to about three minutes and let the interviewer choose where to go deeper.

What hurts

  • Spending most of the time on technical details and never stating the goal or the impact.
  • Being vague about your own part in a large team project.
  • Claiming impact you cannot explain or measure.

Sample answer

Think of your own story first, then compare.