Each question below includes what the interviewer is actually testing. That matters more than the answer itself — once you know what is being probed, you can answer from your own experience instead of reciting someone else’s script, which is obvious to everyone in the room.
Intellectual honesty and sunk-cost discipline. Almost every PM has shipped a dud; few will admit it.
Name the evidence threshold you set in advance, the moment it was crossed, and what you did with the freed capacity. Killing something on time is a stronger signal than shipping something mediocre.
Whether you have an actual framework or just absorb the loudest voice.
Anchor on a single metric the company agreed on, make the tradeoff visible rather than deciding privately, and give the losing party a date rather than a no. Name your framework but show the judgment where it broke down.
Whether you measure it or feel it.
Point at retention curves flattening, organic pull, and how customers react to it being taken away. Vanity signups are the classic false positive — say that.
None of this matters if your resume is filtered out first. The most common cause is not a weak background — it is a document that screening software cannot read correctly, or one that lists duties where it should show results.
Check your resume against product manager keywords or run a full scan. Both are free and take about three seconds.