Behavioral questions

Google

Walk me through a past project where you designed the technical solution: what made it hard, and how did you get past it?

BehavioralLast seen Nov 9, 2026 · Software engineer
Technical impactInfluenceOwnership

Follow-ups they asked

  • How did the problem come up in the first place?
  • How did you look for and settle on that technical approach, and what trade-offs did it involve?
  • How did you write the design document, and how did you get your manager and senior engineers to adopt and carry out your design?
  • What pushback did you run into while driving it forward?
  • Did the final result meet expectations?

What they're looking for

The interviewer uses one real project of yours to test two things at once: your technical judgment and how you win support for a design. The interviewer wants to see how you go from a messy problem to a chosen design, whether you can explain the trade-offs you weighed, and how you got other people to back your plan. Expect detailed follow-ups on where the problem came from, how you picked the approach, the design document, how you won over your manager and senior engineers, the pushback you hit and whether the result met the goal. A strong answer is one real project you know deeply, with clear numbers and clear credit for your own part.

What works

  • Pick a project where you personally proposed the design and saw it reach production, since every follow-up digs into that.
  • Prepare a one-minute version of how the problem started, with the signal that showed it, before you get to any solution.
  • List two or three options you seriously considered and why you dropped each one, because trade-offs are the core of this round.
  • Get ready for the reported follow-ups: how the design document was structured, who you had to convince and how, which objections came up, and how the outcome compared with the target.
  • Close with measured results and one thing you would design differently now.

What hurts

  • Treating it as a system design question and drawing a generic architecture instead of telling what you actually did.
  • Saying the team agreed with no friction, which sounds rehearsed and skips the pushback the interviewer will ask about.
  • Describing the whole team's work so it is unclear which decisions were yours.
  • Not knowing the numbers before and after, which makes the impact hard to believe.

Sample answer

Think of your own story first, then compare.