Databricks·Software Engineer·Onsite - System Design / Architecture
- Design a team messaging service similar to Slack, covering workspaces, channels, direct messages, real-time delivery, message history, presence, notifications, search, and file attachments at scale.
- How would you handle message ordering guarantees across distributed storage, and what tradeoffs does your approach introduce?
- Walk through how you'd scale WebSocket-based fan-out for a channel with tens of thousands of active concurrent members.
- How would you design the presence service to show online/offline/away status at scale without overloading your backend?
- How would you build search across message history for millions of users and messages?
“This is the kind of question where you can talk for an hour and still feel like you only scratched the surface.”