Product design question
How do you prioritize a customer facing feature with X impact on engagement vs a tech driven task like upgrading the libraries to eliminate legacy bugs which have no immediately visible impact?
- Meta
- Product design
- Hard
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 the classic tech-debt versus feature prioritization tradeoff, including how to make invisible risk visible to stakeholders.
How to approach it
- Quantify both sides: the feature's estimated engagement impact (X%) against the tech debt's risk, framed as probability and cost of a future incident, not just 'it's overdue'.
- Ask what's driving urgency on the library upgrade: security vulnerabilities, blocking future features, or team velocity drag, since that changes the priority.
- Propose a split rather than an all-or-nothing choice: ship a scoped version of the feature while allocating a fixed percentage of sprint capacity to the upgrade.
- If forced to choose fully, prioritize based on risk exposure: an unpatched security vulnerability outweighs a feature with engagement upside, but a purely nice-to-have refactor doesn't.
- Communicate the tradeoff explicitly to stakeholders in business terms, e.g. 'delaying this upgrade risks X', to make invisible technical risk visible.
What a strong answer includes
- Avoids the false binary and proposes splitting capacity, a realistic move most teams actually make instead of picking one extreme.
- Translates technical debt into business risk language (security exposure, future velocity cost) so it can be compared fairly against a feature's engagement number.
- Uses an illustrative number, e.g. assume the feature adds 3% engagement but the legacy library has a known unpatched CVE, tipping priority toward the upgrade.
- Recognizes that not all tech debt is equal, urgency depends on whether it's blocking, risky, or just stylistic cleanup.
Common mistakes
- Always defaulting to 'features first' without evaluating the actual risk the tech debt represents.
- Treating this as purely an engineering call instead of one the PM should actively weigh in on with business framing.
Likely follow-up questions
- How would you communicate a decision to delay the tech debt work to the engineering team?
- What would change your prioritization if the legacy library had a known security vulnerability?
More product design questions
- You’ve just joined Meta and have been tasked with launching a new product to help people at home during emergencies. What would you build?Meta · Product design · Medium
- How would you improve the Facebook Timeline?Meta · Product design · Easy
- Build a volunteer product for Facebook.Meta · Product design · Medium
- Design an application launching in the US marketplace that enables patients to find doctors.Meta · Product design · Hard
- Design a washing machine for Google.Google · Product design · Hard
- How would you make WhatsApp more user-friendly for the elderly to use?Meta · Product design · Medium
More questions from Meta
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 7: AI UX and human oversight: design for a system that is wrong sometimes
- Chapter 14: Get the job: the AI PM interview loop