Removing features is a product skill. Show how you used data to identify unused features and communicated the sunset to affected users.
Strong answers distinguish product debt from technical debt: outdated features that confuse users, redundant functionality, accumulated complexity. Best candidates discuss audit practices, usage data to identify debt, sunset processes, and the courage to remove features. They should mention migration paths for existing users.
Senior PM question. Most PMs only add features. The best ones also remove. Ask: "What feature have you sunset and how did you handle user pushback?"