← Back to Directory

Nooks

Small

Screna has 3 Nooks interview write-ups. The most reported round is the system design round (2).

3 interview notes · updated Jun 2026

Nooks·Software Engineer·Technical Phone Screen

Jun 2026
Nooks had me do a live debugging round for a Software Engineer role where they handed over a broken full-stack app and wanted it fixed in real time. The app was a YouTube watch party thing with WebSockets, chat, and room management. Starter code was public on their GitHub so you could theoretically prep beforehand.
  • You're given a broken full-stack 'YouTube watch party' app with bugs across the frontend, backend, and WebSocket sync logic. Find and fix the issues live.

“This was more stressful than a standard coding question because the bugs weren't isolated.”

View Post

Nooks·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Nooks software engineer interview with a system design question that started simple and then turned into a pretty involved discussion about crawling infrastructure. The follow-up was where things got interesting.
  • Design a web crawler that starts from a seed URL and uses BFS to discover and visit pages, visiting each URL only once and generally staying within the same domain.
  • Your crawler makes HTTP requests to fetch each page. How do you prevent it from becoming a bottleneck or getting blocked as a potential DDOS source?

“The core BFS part I had down fine.”

View Post

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.”

View Post