Social calendar inside Facebook: segments, scheduling pain points, MVP and metrics

Quick Overview

A Meta product design prompt that asks you to build a calendar experience inside Facebook. It tests whether you can justify why a calendar belongs in a social app, build on Events and birthdays, pick a segment and its scheduling pain points, set privacy defaults for availability, and define engagement metrics with guardrails.

Social calendar inside Facebook: segments, scheduling pain points, MVP and metrics

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager at Meta and have been asked to build a calendar experience inside Facebook. Decide what the calendar should do and whom it serves, identify the problems it solves for those people, choose what the first version includes, and explain how you would measure whether it succeeds. ```hint Ask why Facebook, not why a calendar People already keep calendars on their phones and at work. Look for scheduling needs that come from their social lives on Facebook (friends, Groups, Events, birthdays) that those calendars handle badly. ``` ### Clarifying Questions - Is this for the Facebook app and website only, or should it also reach Messenger, Instagram and WhatsApp? - Is the aim to deepen engagement among existing users, or to create a new source of revenue? - How should it relate to features that already revolve around dates, such as Events, Group events and birthday reminders: absorb them, or sit alongside them? - Should it connect to the calendars people already keep on their phones or at work, or stand on its own? ### What a Strong Answer Covers - A goal tied to Facebook's mission and to engagement, with a convincing reason a calendar belongs inside Facebook rather than in a standalone calendar app. - Building on what Facebook already has (Events, birthdays, Groups, Messenger) instead of duplicating it. - A segmentation of users (for example organizers versus invitees, or by life stage and social habits) with a reasoned primary segment and its specific scheduling pain points. - Prioritized solutions and a focused first version, with explicit privacy defaults for sharing plans and availability. - Success metrics with guardrails such as notification fatigue, privacy complaints and cannibalization of Events. ### Follow-up Questions - If people keep using their phone or work calendar as their main calendar, how does your product stay useful, and would you sync with those calendars? - Showing friends when you are free can make planning easier but can also feel invasive. What would friends see, and what would the default be? - How would you tell whether the calendar helped people spend more real time together, rather than just sending more notifications?

Overview: A Meta product design prompt that asks you to build a calendar experience inside Facebook. It tests whether you can justify why a calendar belongs in a social app, build on Events and birthdays, pick a segment and its scheduling pain points, set privacy defaults for availability, and define engagement metrics with guardrails.

Meta logo
Meta
Sep 11, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager at Meta and have been asked to build a calendar experience inside Facebook. Decide what the calendar should do and whom it serves, identify the problems it solves for those people, choose what the first version includes, and explain how you would measure whether it succeeds.

Clarifying Questions Guidance

  • Is this for the Facebook app and website only, or should it also reach Messenger, Instagram and WhatsApp?
  • Is the aim to deepen engagement among existing users, or to create a new source of revenue?
  • How should it relate to features that already revolve around dates, such as Events, Group events and birthday reminders: absorb them, or sit alongside them?
  • Should it connect to the calendars people already keep on their phones or at work, or stand on its own?

What a Strong Answer Covers Guidance

  • A goal tied to Facebook's mission and to engagement, with a convincing reason a calendar belongs inside Facebook rather than in a standalone calendar app.
  • Building on what Facebook already has (Events, birthdays, Groups, Messenger) instead of duplicating it.
  • A segmentation of users (for example organizers versus invitees, or by life stage and social habits) with a reasoned primary segment and its specific scheduling pain points.
  • Prioritized solutions and a focused first version, with explicit privacy defaults for sharing plans and availability.
  • Success metrics with guardrails such as notification fatigue, privacy complaints and cannibalization of Events.

Follow-up Questions Guidance

  • If people keep using their phone or work calendar as their main calendar, how does your product stay useful, and would you sync with those calendars?
  • Showing friends when you are free can make planning easier but can also feel invasive. What would friends see, and what would the default be?
  • How would you tell whether the calendar helped people spend more real time together, rather than just sending more notifications?