Behavioral questions

Workday

If you could rebuild your current product, what would you change?

BehavioralLast seen Nov 8, 2026 · Software engineer
Customer focusTechnical impact

What they're looking for

This question checks whether you think about your product as a whole, not just your own tickets. The interviewer wants to hear that you know where it falls short for users and for the team that builds it, and that you can rank changes by impact instead of listing everything you dislike. A strong answer names one or two concrete changes, explains why they matter and what they would cost, and stays fair to the people who made the original choices.

What works

  • Pick one or two changes with a clear reason, such as a user pain point or a design choice that slows every release.
  • Back each change with evidence you saw yourself, like support tickets, usage data, incidents or slow builds.
  • Say what you would keep as well, so the answer doesn't sound like a complaint.
  • Mention the cost of each change and how you would roll it out without hurting current users.

What hurts

  • Listing every flaw without saying which change matters most.
  • Blaming earlier engineers or managers for past decisions.
  • Proposing a full rewrite with no plan for moving users and data over.

Sample answer

Think of your own story first, then compare.