Strategy question

How would you decide whether to build a feature or fix a bug (assuming both take the same engineering effort)?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

Start a mock interview on this question · Mock interview from a job description

What this question tests

Tests prioritization judgment: building a decision framework for feature versus bug when effort is held equal, naming what actually differentiates the two.

How to approach it

  1. Note effort is equal, so the call rests on impact and risk alone.
  2. Compare on three axes: user impact (how many, how severely), business impact (revenue, trust, retention), and urgency/reversibility.
  3. Size the bug: how many users hit it, whether it blocks a core action like posting or checkout, and whether it's worsening.
  4. Size the feature: expected impact from data (competitive gap, user requests, an engagement estimate) and time-sensitivity of the opportunity.
  5. Apply a default rule: a bug breaking a core flow or trust usually beats a feature, since it actively subtracts value.
  6. If roughly equal, break the tie with compounding risk: unfixed bugs often worsen, delayed features usually don't.

What a strong answer includes

Common mistakes

Likely follow-up questions

More strategy questions

More questions from Meta

Learn the skill behind it

Chapters of the AI PM course that teach what this question tests.

Preparing for a specific role?

Book summaries for this kind of question

Browse all 4,000+ questions in the bank