Interview Question: Design a Calendar API

The interview question is:

Design a Calendar API.

The pressure is a repeat that may never end, read from every time zone.

Creating one stored row for every occurrence cannot work when a weekly event has no end. Storing only UTC cannot preserve "nine in the morning" when the local offset changes. Treating one moved meeting as a rewrite of the whole series changes dates the caller never intended to touch.

The contract needs one recurring event, bounded occurrence expansion, and exceptions addressed in the original series.

Scope

"I will design one-time and recurring events, boun