PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/Notion

Design a Shared Calendar Service

Last updated: Jun 5, 2026

Quick Overview

This question evaluates a candidate's competency in large-scale system architecture, data modeling, distributed systems, consistency models, event scheduling semantics (recurrence, time zones), and real-time notifications and indexing for low-latency reads.

  • medium
  • Notion
  • System Design
  • Software Engineer

Design a Shared Calendar Service

Company: Notion

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Onsite

Design a shared calendar service similar to a modern online calendar product. Users can create calendars, create and edit events, invite attendees, accept or decline invitations, view their own agenda, view free or busy availability for other users, configure reminders, create recurring events, and share calendars with different permission levels. Assume the service has tens of millions of daily active users, stores billions of events, and must provide low-latency reads for daily and weekly calendar views. Discuss requirements, APIs, data model, architecture, storage, indexing, consistency, recurring events, reminders, notifications, time zones, scalability, and failure handling.

Quick Answer: This question evaluates a candidate's competency in large-scale system architecture, data modeling, distributed systems, consistency models, event scheduling semantics (recurrence, time zones), and real-time notifications and indexing for low-latency reads.

Related Interview Questions

  • Design an event analytics platform - Notion (medium)
Notion logo
Notion
Jun 1, 2026, 12:00 AM
Software Engineer
Onsite
System Design
1
0

Design a shared calendar service similar to a modern online calendar product. Users can create calendars, create and edit events, invite attendees, accept or decline invitations, view their own agenda, view free or busy availability for other users, configure reminders, create recurring events, and share calendars with different permission levels. Assume the service has tens of millions of daily active users, stores billions of events, and must provide low-latency reads for daily and weekly calendar views. Discuss requirements, APIs, data model, architecture, storage, indexing, consistency, recurring events, reminders, notifications, time zones, scalability, and failure handling.

Solution

Show

Submit Your Answer

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Notion•More Software Engineer•Notion Software Engineer•Notion System Design•Software Engineer System Design
PracHub

Master your tech interviews with 8,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.