Behavioral questions

Workday

Tell me about the project on your résumé you're most satisfied with.

BehavioralLast seen Nov 8, 2026 · Software engineer
Technical impactOwnershipTeamwork

Follow-ups they asked

  • Which part of that project did you own, and how did you work with the product manager and other teammates?
  • How often did that project ship, and what did its release process look like?

What they're looking for

In a hiring manager screen this question usually opens a project deep dive. The interviewer wants to see whether you can explain a project clearly: the problem, why it mattered, what you built and what changed because of it. Follow-up questions about the part you owned, how you worked with product and teammates, and how the project shipped test whether your role was real and whether you understand how software reaches users. A strong answer picks one project, states your own part plainly and holds up under detailed questions.

What works

  • Pick a project you know well enough to explain small design choices, since deep dives often go into detail.
  • Open with one or two sentences on the problem and who it was for before any technical detail.
  • Name the piece you owned and say I for your own decisions and we only for shared work.
  • Prepare for the reported follow-ups: how you worked with the product manager and teammates, and how often the project shipped and how a release reached production.
  • End with a result you can measure and one thing you would do differently.

What hurts

  • Describing the whole team's work so the interviewer can't tell what you did yourself.
  • Choosing a project you only touched briefly and then struggling with detail questions.
  • Getting lost in implementation detail before explaining why the project mattered.

Sample answer

Think of your own story first, then compare.