Product design question
Design WhatsApp's status feature.
- Meta
- Product design
- Medium
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Product design replicating (or critiquing) an existing well known feature, testing whether the candidate reasons from first principles about ephemeral sharing.
How to approach it
- Identify the user: WhatsApp users who want to share moments with close contacts without the permanence or public reach of a social feed post.
- Name the underlying need: casual, low-stakes sharing (similar to what Instagram or Snapchat stories solve) but within a private, contact-based messaging app.
- Design the core mechanic: photo, video, or text updates visible to the user's contacts for 24 hours, viewable from a dedicated status tab, with visibility controls (all contacts, except specific contacts, or only specific contacts).
- Add a privacy-first design choice appropriate to WhatsApp's brand: default to a narrower default audience given WhatsApp's privacy-focused positioning versus a broadly public default.
- Prioritize simple visibility controls and reliable read-receipt-style view tracking (who viewed your status) since that reciprocity drives repeat posting.
- Define success as daily active status posters and status view completion rate.
What a strong answer includes
- Grounds the design in WhatsApp's actual brand positioning, privacy-first, and lets that shape a key decision like default audience visibility.
- Names the reciprocity mechanic, seeing who viewed your status, as the retention driver, consistent with why similar features succeed elsewhere.
- Distinguishes this from Instagram Stories by anchoring it to WhatsApp's contact-based, non-public graph rather than treating it as an identical clone.
Common mistakes
- Designing this as a direct copy of Instagram Stories without considering WhatsApp's different privacy expectations and contact-based graph.
- Ignoring visibility controls, which matter more on a primarily one-to-one messaging app than on a public social network.
Likely follow-up questions
- How would you handle a user who wants to post but never wants specific contacts to see it?
- How would this feature affect WhatsApp's core one-to-one messaging usage?
More product design questions
- You’ve just joined Meta and have been tasked with launching a new product to help people at home during emergencies. What would you build?Meta · Product design · Medium
- How would you improve the Facebook Timeline?Meta · Product design · Easy
- Build a volunteer product for Facebook.Meta · Product design · Medium
- Design an application launching in the US marketplace that enables patients to find doctors.Meta · Product design · Hard
- Design a washing machine for Google.Google · Product design · Hard
- How would you make WhatsApp more user-friendly for the elderly to use?Meta · Product design · Medium
More questions from Meta
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 7: AI UX and human oversight: design for a system that is wrong sometimes
- Chapter 14: Get the job: the AI PM interview loop