Uber·Frontend Engineer·Onsite - System Design / Architecture
May 2026
System design round at Uber for a frontend engineer role, centered entirely on designing an online calendar service like Google Calendar. Heavy emphasis on the client-side architecture, not just backend services. A lot to cover and the recurrence model alone could eat your whole session if you're not careful.
- Design an online calendar service (like Google Calendar) that supports individual and shared calendars, with event CRUD across day/week/month/agenda views, attendee invites, recurring events with exceptions, time zones, reminders, conflict detection, and free/busy checks. Weight the design toward the frontend client experience.
- How would you implement 'edit this and all following events' on a recurring series at the data model level, and what does it cost in extra rows or rule splits?
- A shared team calendar has 50,000 events visible in a single month and the month view is janky. How do you diagnose and fix both the frontend rendering and the data fetch path?
- How do you efficiently compute free/busy availability across 20 attendees for a 30-minute meeting slot, and what do you precompute versus compute on demand?
- A user in New York creates a weekly 9am recurring event, then moves to Tokyo. What happens to past and future instances, and what's the correct product behavior?
“This is the whole question, basically.” The rest of the author's notes on Frontend Engineer interview at Uber, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post