Nooks·Software Engineer·Onsite - System Design / Architecture
May 2026
System design round at Nooks for a software engineer role, basically one big question about designing Twitter from scratch. Covered a lot of ground in not that much time, felt like I was constantly making trade-off calls without enough space to fully justify each one.
- Design a system like Twitter, covering core features like posting tweets, following users, viewing a personalized home timeline, search, and notifications.
- Walk through the trade-offs between pushing tweet fan-out to followers' feeds on write versus pulling and merging tweets on read, and when you'd use a hybrid approach.
- What data stores would you use for this system and why? Consider the timeline storage, caching layer, and any relational needs.
- How would you handle media storage and delivery for tweets with images or video?
- How would you approach search across tweets at scale?
“I started with requirements scoping which felt okay, read-heavy workload, eventual consistency is fine, low-latency reads matter most.” The rest of the author's notes on Software Engineer interview at Nooks, 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