Role: Senior Backend Engineer Team: Backend Infrastructure Location: Remote
Scenario — "Keeping Meetings in Sync"
Read AI connects to Google Calendar, Outlook, Slack, and Zoom to summarize and analyze meetings. When users update or delete events, Read must stay perfectly aligned — no duplicates, no ghosts, no outdated data.
Problem: Events can arrive out of order or from multiple providers describing the same meeting. Sometimes only one instance of a recurring meeting moves or gets canceled.
Your Task: Design a lightweight sync service that keeps Read's internal event store consistent. It should:
Example event input:
{
"provider": "google_calendar",
"op": "updated",
"id": "gcal_123",
"start": "2025-10-16T17:00:00Z",
"updated_at": "2025-10-08T09:02:00Z"
}
Submit a video walking us through your approach, along with a system design sketch and a conflict resolution plan.
Design event synchronization systems across multiple providers
Implement conflict resolution strategies for distributed data
Handle out-of-order updates and eventual consistency
Build predictable deduplication logic
Design for reliability in asynchronous systems
Required Submissions:
Video Requirements:
Your 7-10 minute video must include ALL three components:
1. Introduction (1-2 minutes)
2. Traits Assessment (2-3 minutes)
Which kind of challenge fits you best — and why?
There's no "correct" choice — just share your thoughts.
3. Challenge Response (3-5 minutes)
Walk us through your approach to the main challenge:
AI Usage Declaration:
At the end of your video, please state:
On this page