Everything you need to pass your interviews: hellointerview.com/twitter
1
61
Candidates read these rounds far too narrowly, hunting for the right answer, when what is being scored is how you got to an answer and whether you knew what it cost.
1
2
87
"I must have bombed that interview because I used Redis instead of Cassandra." Almost certainly not.
1
8
404
Our own breakdowns of posts like these: hellointerview.com/twitter/t…𝑖𝑛-𝑡ℎ𝑒-𝑤𝑖𝑙𝑑&𝑢𝑡𝑚source=twitter&utm𝑚𝑒𝑑𝑖𝑢𝑚=𝑠𝑜𝑐𝑖𝑎𝑙&𝑢𝑡𝑚campaign=in-the-wild
Airbnb Engineering. Trust and safety systems and geographic search, both of which turn up in interviews constantly. airbnb.tech/
Shopify Engineering. Millions of stores processing billions in sales, with the Black Friday posts as the highlight. shopify.engineering/
Pinterest Engineering. Infrastructure and personalisation for discovery at Pinterest scale. medium.com/pinterest-enginee…
AWS Architecture Blog. Cloud patterns from the team that built the biggest cloud platform, which makes it close to a reference. aws.amazon.com/blogs/archite…
Five more engineering blogs worth following if you want system design knowledge that is current rather than remembered. LinkedIn Engineering first, the best source going for B2B platform problems. linkedin.com/blog/engineerin…
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
100
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
178
Starting a new engineering job? Before you propose replacing the system that looks obviously wrong, find out why the team built it that way.
Replying to @sarthak13997
Hm, it shouldn't? Send us an email [email protected] if you have repo details and we'll take a look!
28
Read the full breakdown:
hellointerview.com/twitter/u…
131
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
146
Two riders can request the same driver. Use a shared lock with an expiry while making an offer, and move on if the driver doesn’t respond. A lock inside one server won’t coordinate the others.
1
144
Let the phone adapt location updates to movement. A parked driver doesn’t need to send GPS coordinates as often as one moving through a city. Fewer writes, with a freshness tradeoff.
1
1
238
Driver locations change constantly. Keep the latest positions in a geospatial store such as Redis so finding nearby drivers doesn’t require scanning a database table.
1
1
341






