Explain the Product Principles That Guide Your Decisions as a PM

An interviewer asks you to describe your core product principles. Explain the few principles that most shape what you decide to build and how you build it, why you hold each one, and how each has changed real decisions in your work. ```hint Principles show up in decisions A principle says something about you only if it changed a real choice, ideally one where following it cost you something. Pick a handful you can back with a specific story rather than listing values everyone would agree with. ``` ### Clarifying Questions - Does the interviewer want principles about what makes a product good, about how you work as a product manager (discovery, decisions, working with engineering and design), or a mix of both? - Should each principle come with an example from your own work right away, or would the interviewer prefer a short overview first and then pick one to explore? - Is there a kind of product the interviewer wants the principles related to, such as consumer products with a very large audience, or tools for businesses and developers? ### What a Strong Answer Covers - A short set of distinct principles, each phrased so it could settle a real decision rather than as a generic virtue. - The reasoning behind each principle and the trade-off it implies, including what you give up by following it. - Evidence: a concrete, STAR-shaped example for each principle in which it changed a decision, with a measurable result. - How you choose when two principles conflict, and how the principles adapt to context such as product stage or the size of the user base. - Self-awareness: a principle you added or revised after a mistake. ### Follow-up Questions - Tell me about a time two of your principles pointed in opposite directions. How did you decide? - Which of your principles would your engineering partners say you follow least consistently, and why? - How do you get a team to work by these principles when you have no formal authority over it?