Design a Calendar System
Six candidates have reported this prompt at LinkedIn, all in the main 45 to 60 minute design round. The newest is from September 2026, an IC2 loop where the discussion covered "the architecture, components, scalability, and design decisions." In April 2026 an India candidate got the same "Design Google Calendar" prompt and was rejected for a below-average design rating. A Senior+ candidate (SDE3) in February 2026 had time zones thrown at them as the curveball. The earlier write-ups are from 2025, across generic SWE, Applications and India SSE loops. Two of them say the API ate a big share of the hour. One also lost time on requirements. The other lost it on the database schema, and that interviewer asked for a SQL query against it too.
A calendar looks easy until you write down the schema. A daily standup that repeats forever is one thing the user created but hundreds of meetings they'll attend. Move one of those meetings and you have an exception to a rule. Put an attendee in London and a 9 a.m. meeting in Los Angeles lands at a different London hour for a few weeks every year. Raw traffic is modest next to a feed. The hard part is a data model that answers "what's on my calendar this week" fast and correctly.
LinkedInPremium lesson · System design round
The LinkedIn design, worked end to end.
- Requirements and scopeSystem design · Frequently asked
- The API and data model
- The design, drawn out1 diagram
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
1,074 LinkedIn interview reports · guide updated
LinkedIn interview guideKnow what LinkedIn asks before you walk in.
28 coding · 7 system design · 26 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.