Hello Interview (@_hellointerview) header
Hello Interview (@_hellointerview) profile picture

Where top software engineers prepare for interviews

Joined May 2023
Starting a new engineering job? Before you propose replacing the system that looks obviously wrong, find out why the team built it that way.
1
1
4
388
Ask what constraints shaped the decision, what alternatives they tried and what has changed since. You may uncover a requirement you hadn't seen, or find that the team already knows the problem and needs help fixing it.
1
99
Connect your work to the business too. Know who uses what your team builds and why it matters. That context helps you choose useful work as the onboarding checklist runs out. Our guide to getting up to speed in a new role: hellointerview.com/twitter/b…
1
72
Uber System Design
1
4
100
3,508
Queue ride requests to absorb bursts, then scale matching workers. The queue buys resilience, but waiting time still matters: accepting requests faster than you can match them creates unhappy riders.
1
132
Vector databases: why ANN skips comparisons
1
31
1,083
Hot shards are what make News Feed interesting. One celebrity account can put a disproportionate share of the write traffic on a single partition, and the fix changes the whole design.
1
1
49
2,121
Async workers, fan-out strategy and shard keys all fall out of that one constraint rather than being separate decisions.
1
1
334
System design question: A seller updates a price. The product page shows it immediately, but search still shows the old price, sometimes forever. Products live in Postgres. Search uses a separate index. What could cause this, and how would you fix it?
12
10
1
97
6,354
Adding one server to your cache cluster can reshuffle most of its keys. Consistent hashing avoids that. Here's how.
1
1
65
3,476
Consistent hashing puts servers and keys on a ring. A key belongs to the first server clockwise from its position. Adding a server takes over only the interval before that server; keys elsewhere keep their owners.
1
1
295
Virtual nodes place each physical server at many points on the ring. This helps distribute data more evenly and spreads a failed server's ranges across several surviving machines. The full visual walkthrough: hellointerview.com/twitter/c…
199