I spent too long trying to define the problem space and the interviewer had to nudge me to actually start designing.
Start by clarifying the ambiguous prompt—define what 'help' means and which user segment you're targeting—then frame the problem with a clear user need and Meta's strategic context. Structure your answer around a specific product concept, walking through user value, key features, and success metrics, while showing how you'd iterate based on feedback.
Pro tip: Anchor your design in Meta's existing ecosystem (e.g., Groups, Messenger, or Community Help) to show strategic thinking, but don't be afraid to propose a bold new direction that leverages Meta's scale and social graph. Demonstrate adaptability by acknowledging trade-offs and how you'd pivot if initial assumptions prove wrong.
Ask clarifying questions to narrow the ambiguous prompt: define 'help' (e.g., time, skills, resources), choose a target user segment (e.g., local communities, busy professionals), and set constraints (e.g., mobile-first, within Meta's family of apps).
Articulate a specific, high-value problem for your chosen segment, supported by insights about user behavior and gaps in existing solutions. Connect it to Meta's mission and strengths (e.g., social connections, groups).
Describe your app idea in one sentence, then outline the core user experience and key features that enable helping behavior. Focus on how it leverages Meta's platform (e.g., social graph, messaging, groups) to create seamless interactions.
Specify metrics for success (e.g., daily active helpers, help requests fulfilled, retention) and explain how you'd test, learn, and iterate. Mention potential risks and how you'd adapt based on user feedback.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.