Name the real tension
- Translate strategy into a ranked problem list
- Name the cost of waiting and the irreversible downside.
Meta · Product manager · Execution & Prioritization
A launch needs another month for polish but a competitor is moving quickly. Decide.
Build a defensible answer, then pressure-test it in the same workspace where you can save the attempt.
See this question in OfferHack Browse the question first. Premium opens the complete worked answer and coaching when you need them.This is a constructed rehearsal, not an official company answer or a prediction of what an interviewer will ask. A company-specific practice prompt synthesized from published interview guidance, candidate reports, official product material, role descriptions, and company values; it is not a claim that this exact question will be asked.
Start with a position
Give the interviewer your decision before the framework.
For “A launch needs another month for polish but a competitor is moving quickly. Decide.” at Meta, I would make the decision owner, non-negotiable user outcome, reversible scope, and review mechanism explicit, then use a shorter path to one successful outcome followed by a deliberate trigger for repeated value to create evidence without normalizing novelty usage, incentive-driven growth, support burden, or a retention lift isolated to the wrong cohort.
Preview the reasoning
Three moves to make the answer concrete.
Set decision principles
- Principles must eliminate options, not decorate the memo.
- Explain how the principle applies under pressure.
Make ownership explicit
- Use impact, confidence, and effort without false precision
- Escalate with a recommendation and consequence, not a status dump.
Measurement check
A metric is useful only when it changes the decision.
- North star
- retained successful outcomesMeasures the repeated user or customer outcome, not mere feature activity.
- Diagnostic
- time to first value and second-use rateExplains whether quality and the critical journey improved for the intended segment.
- Guardrail
- low-quality use, churn, support burden, and trustMakes the principal downside observable: novelty usage, incentive-driven growth, support burden, or a retention lift isolated to the wrong cohort.
Interviewer pressure test
Do not stop when the first answer sounds polished.
- Why prioritize a high-intent new or returning user trying to reach a first repeatable outcome, and who did you explicitly defer?
- How would your answer change with two weeks, three engineers, or a tenfold scale increase?
- What is the strongest rejected alternative and when would it win?
Turn reading into retrieval