Should we build social features?
Last updated: February 5, 2026
Quick Overview
Your team is considering building push notifications. How would you evaluate this decision?
Supabase
February 5, 2026548
6
4,194 solved
Your team is considering building push notifications. How would you evaluate this decision?
This product question from Supabase's Onsite goes beyond feature brainstorming. The interviewer expects a framework-driven approach that considers market dynamics, user segmentation, and data-informed decision making.
What the Interviewer Expects
- Identify the target user and their core problem
- Propose reasonable solutions with basic prioritization
- Define 2-3 key success metrics
- Consider basic trade-offs and risks
Key Topics to Cover
How to Approach This
- Start with the user. Who are they, what problem do they have, and what is their current workaround?
- Use a prioritization framework: impact vs effort, RICE scoring, or ICE scoring.
- Define success metrics using the AARRR framework: Acquisition, Activation, Retention, Revenue, Referral.
- Consider second-order effects. A feature might boost short-term engagement but hurt long-term retention.
Possible Follow-up Questions
- How would you decide to kill this feature if it's not working?
- What competitive response would you expect and how would you prepare?
- How would you validate this idea before committing engineering resources?
Sharpen Your Skills on Codemia
Practice similar problems with our interactive workspace, get AI feedback, and track your progress.
Browse Product QuestionsSample Answer
Problem Framing
To evaluate the decision to build social features, specifically push notifications, we first need to define the core problem: **How can Supabase enhance user engagement and retention through social fe...
User & Market Context
The primary users for Supabase are developers and teams building applications, primarily in the startup and small business segments. What matters to them is efficient communication, real-time updates,...
Submit Your Answer
