Tell me about a feature that did not perform as expected. What did you do?
What the interviewer wants to hear
- Describe the goal and what happened honestly
- Investigate with data and user feedback
- Decide to iterate, pivot or remove
- Share lessons and change the process
Model answer
In a previous role we launched a wishlist feature in a shopping app, expecting it to increase repeat purchases. After a month, only four percent of users had used it and there was no change in repeat purchase rate. I took ownership and investigated. Analytics showed most users never noticed the heart icon, and interviews showed people already used their cart as a wishlist. Instead of adding more features, we tested a simpler change: price-drop alerts for items left in the cart. That increased return visits and purchases noticeably. We kept a light wishlist but stopped investing in it. My main lessons were to validate the user behaviour before building, and to define a small test first. I shared these lessons in a short review with the team.
Can you answer it under time pressure?
Take a timed medium round and get scored on every answer.
More medium Product Manager questions
- How would you define success metrics for a new feature?
- How do you say no to a stakeholder request?
- How do you run customer discovery for a new problem area?
- How do you write a product spec or PRD that engineers find useful?
- Leadership wants to change your product's pricing. How would you approach it?
- Walk me through how you plan a major product launch.
- Your A/B test finished and the result is not statistically significant. What do you do next?
- How would you set OKRs for your product team for next quarter?
- How would you tell whether a new product has product-market fit?