PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/LinkedIn

Design a Global Calendar Service

Last updated: Apr 22, 2026

Quick Overview

This question evaluates competence in designing scalable, time-zone aware calendaring systems, covering API and data model design, recurrence representation, daylight saving semantics, conflict detection, storage strategy, and consistency trade-offs.

  • medium
  • LinkedIn
  • System Design
  • Software Engineer

Design a Global Calendar Service

Company: LinkedIn

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Onsite

Design a calendar system for users in multiple time zones. The system should support: - creating, updating, deleting, and viewing calendar events - one-time and recurring events - querying a user's schedule for a time range - scheduling events without losing correctness across time zones - handling daylight saving time changes correctly Discuss the API design, data model, recurrence representation, storage strategy, timezone handling, conflict detection, scaling approach, and consistency model. Pay special attention to how recurring events should behave when the organizer's local timezone observes daylight saving time.

Quick Answer: This question evaluates competence in designing scalable, time-zone aware calendaring systems, covering API and data model design, recurrence representation, daylight saving semantics, conflict detection, storage strategy, and consistency trade-offs.

Related Interview Questions

  • Review a Web Application Architecture - LinkedIn (easy)
  • Scale a Distributed Randomized Multiset - LinkedIn (medium)
  • Design a Top-K Ranking Service - LinkedIn (easy)
  • Design a malicious-URL checking service using an isMalicious API - LinkedIn (medium)
  • Design a metrics platform without alerting - LinkedIn (medium)
LinkedIn logo
LinkedIn
Feb 16, 2026, 12:00 AM
Software Engineer
Onsite
System Design
4
0

Design a calendar system for users in multiple time zones.

The system should support:

  • creating, updating, deleting, and viewing calendar events
  • one-time and recurring events
  • querying a user's schedule for a time range
  • scheduling events without losing correctness across time zones
  • handling daylight saving time changes correctly

Discuss the API design, data model, recurrence representation, storage strategy, timezone handling, conflict detection, scaling approach, and consistency model. Pay special attention to how recurring events should behave when the organizer's local timezone observes daylight saving time.

Solution

Show

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More LinkedIn•More Software Engineer•LinkedIn Software Engineer•LinkedIn System Design•Software Engineer System Design
PracHub

Master your tech interviews with 8,000+ 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.