Read AI
Read AI is a productivity AI company that helps knowledge-workers and teams everywhere turn their meeting, email and messaging workflows into high-impact, low-waste interactions. Founded in 2021, we are a fast-growing startup backed by Madrona with millions of users and rapid global expansion
Open Opportunities
No Open Opportunities
Read AI doesn't have any open opportunities at this time. Check back later for new postings.
Available Challenges
Keeping Meetings in Sync (Private Link)
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: Ingest updates from multiple providers Use timestamps or version keys to decide which update wins Handle creates, updates, deletes, and recurring exceptions Resolve duplicates or overlaps in a predictable way Example event input: Submit a video walking us through your approach, along with a system design sketch and a conflict resolution plan.
Keeping Meetings in Sync
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: Ingest updates from multiple providers Use timestamps or version keys to decide which update wins Handle creates, updates, deletes, and recurring exceptions Resolve duplicates or overlaps in a predictable way Example event input: Submit a video walking us through your approach, along with a system design sketch and a conflict resolution plan.