Student-first video meeting product modeled on Zoom: needs, features and metrics
Company: Zoom
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
Design a product similar to Zoom but made for students. Decide what it should achieve and which students it serves, identify what those students need that a general video-meeting tool does not give them, propose and prioritize features, and explain how you would measure success.
```hint Map the study moments
Before naming any feature, list the situations in which students meet over video and the role they play in each; who sets up the call and who picks the tool differ sharply from one situation to the next.
```
### Clarifying Questions
- Is this a new mode inside Zoom or a separate app?
- Which students: children in school, university students, or learners preparing for exams outside school?
- Should success mean adoption and engagement, revenue from institutions or students, or better learning outcomes?
- Which market and devices should I assume, and should the product be mobile-first?
### What a Strong Answer Covers
- A goal and scope settled early, including whether the product lives inside Zoom
- Student segments and study situations compared, with one chosen and the reason
- Needs that a general meeting product leaves unmet for that segment, drawn from its journey and ranked
- Features prioritized with explicit criteria, with safety and privacy addressed for the chosen users
- Success metrics tied to the goal, the main risks, and a way to validate before scaling
### Follow-up Questions
- Who pays for this: students, parents, schools, or nobody? How does the answer change the design?
- How would the design change if many users were children under 13?
- How would you tell whether students are studying more effectively rather than just spending more time on calls?
Overview: A product design question asking how to build a Zoom-like video meeting product made for students. It tests choosing a student segment and study situation, finding needs a general meeting tool misses, prioritizing features, and defining success metrics, safety safeguards and risks.