Core PM Skills, Knowledge Areas, and Methods for Understanding Users

An interviewer asks two linked questions about the product manager role: what a PM needs to be good at and needs to know, and how a PM learns about users. ### Clarifying Questions - Should the answer target a particular kind of PM role at Google, such as a consumer product with a very large user base or a cloud product sold to developers and businesses? - By "types of information", do you mean the knowledge a PM brings to the role (users, market, technology) or the signals a PM tracks day to day (metrics, feedback, delivery status)? - For understanding users, should the methods suit a product already in use, with usage data to analyze, or a new product with no users yet? - Would you like each point backed by an example from my own experience? ### Part 1 — Skills and knowledge a PM needs Name the skills that matter most for a PM and the types of information a PM should have, and explain why. ```hint Tie each item to a decision For every skill or piece of information, name a decision a PM makes that would go wrong without it. That keeps the list short and ranked. ``` #### What This Part Should Cover - A short, prioritized set of skills, each with the reason it matters. - The categories of information a PM needs and where each comes from. - Evidence, ideally from the candidate's own work, of these skills in use. ### Part 2 — Ways to understand users Describe the strategies you would use as a PM to understand your users. ```hint Match the method to the question Some methods reveal what users do, some reveal why, and some tell you how many users share a behavior. Decide which of these you need before picking a method. ``` #### What This Part Should Cover - A mix of qualitative and quantitative methods, and when each fits. - How findings from different methods are combined and turned into product decisions. - Common research mistakes and how to avoid them. ### What a Strong Answer Covers - Prioritization instead of a long, flat list of skills or methods. - Concrete examples that make each claim credible. - A link between the two parts: understanding users is one of the core kinds of information from Part 1. - How the approach adapts to a product with a very large, global user base and rich usage data. ### Follow-up Questions - Which of these skills is weakest for you today, and what are you doing about it? - Tell me about a time user research changed a decision your team had already made. - Usage data and what users tell you in interviews point in opposite directions. How do you decide?