Behavioral: Taking a New Product From Concept to First Launch

Tell the interviewer about a time you built a product or feature from scratch, starting from an idea or a loose mandate rather than an existing product to improve. Walk through how you worked out which problem to solve, decided what the first version would include, got it built and launched, and what happened after launch. ```hint Show the blank page Pick a story where you, not someone before you, defined the problem and the first version. Be ready to explain what you deliberately left out of that first version, and why. ``` ### Clarifying Questions - Does a new feature or internal tool inside an existing product count, or should it be a completely new product? - Should the story come from a product management role, or is a startup, side project or different job acceptable? - Do you want the focus on my own decisions or on how I led the team through the build? - How far past launch should I go: the launch itself, or the results over the following months? ### What a Strong Answer Covers - A starting point that was genuinely blank, with the stakes and the candidate's own role made explicit. - How the problem and target users were found and validated before anything was built. - How the first version was scoped: what was cut, the riskiest assumption, and how it was tested cheaply. - How engineering, design and other stakeholders were aligned without an existing plan or process. - Measured results, including what went wrong, and a specific lesson the candidate still applies. ### Follow-up Questions - What did you leave out of the first version, and in hindsight was that the right call? - What result would have made you stop or change direction, and did you ever come close? - What was the biggest disagreement during the build, and how was it settled?