Behavioral questions

Millennium

Walk me through a project you worked on.

BehavioralLast seen Nov 20, 2026 · Software engineer
Technical impactOwnership

Follow-ups they asked

  • How does your project's service talk to the client side, and over which protocols?
  • How would that design scale as usage grows?

What they're looking for

The interviewer uses your project to judge how deep your technical understanding goes and how clearly you explain it. They want the problem, your own part, the main design choices and the result, in an order a stranger can follow. Expect them to pick one piece and dig in, for example how the browser or mobile client talks to your services and what happens when traffic grows, so know the reasons behind each choice, not just the names of the tools.

What works

  • Open with one sentence on the problem and who used the result, then describe the main parts and how a request moves between them.
  • Make your own work clear: say which parts you built and which decisions you made.
  • Know why you picked each protocol, for example plain HTTP calls for normal requests and WebSockets or server-sent events for live updates, and what you would change now.
  • Prepare a scaling story: where the first bottleneck appears and what you would do about it, with rough numbers.

What hurts

  • Listing technologies without explaining what problem each one solved.
  • Saying we for everything, so the interviewer cannot tell what you did.
  • Claiming the system scales without naming what would break first.

Sample answer

Think of your own story first, then compare.