Choose One Feature to Build and Explain Your Plan From Discovery to Launch

Pick one feature you would want to build and explain how you would take it from an idea to something shipped and measured. The prompt does not name a product, so deciding where the feature lives is part of the answer. Make the case for your feature, then walk through the steps you would follow to get it built and launched. ```hint Prove the problem, then plan the path Anchor the idea in one specific user and a problem you could show evidence for. Then treat the "how" as the path from confirming that problem to judging the launched result, not as a list of screens. ``` ### Clarifying Questions - Should the feature be for this company's own product, or may I choose any product I know well? - Does the interviewer want more depth on the feature idea itself or on the process of getting it built and shipped? - Is it a feature for an existing product, or may I propose something that would stand as a new product? - Should I plan against a particular team size or timeline, or set my own assumptions? ### What a Strong Answer Covers - A concrete feature tied to a named user segment and problem, with a reason it matters to that product's business now - How the problem would be validated and sized before building, including what result would stop the work - A scoped first version, what was cut and why, and how the work would be sequenced with engineering, design and other teams - A primary success metric with guardrails, and a launch and evaluation plan - Risks and trade-offs, including how the plan changes if validation or early results disappoint ### Follow-up Questions - Discovery shows the problem is real but much smaller than you expected. Do you still build the feature? - Engineering says the first version will take far longer than you planned. What do you cut, and what must stay? - A month after launch, how do you decide whether to keep investing in the feature?