2024 Presidential Election
15h
516
Heartwarming peaceful protests
India
1h
358
Modi is a legend, will be remembered for centuries to come
Personal Finance
2h
788
$10 million is the new $1 million
Tech Industry
18h
3444
Asians - what are your thoughts on asian female white male ?
Tech Industry
7h
1116
The end of Backdoor Roth?!
I was interviewing for my first big tech companies (Square & Dropbox). I was up for some senior roles (IC3 @ DBX, IC6 @ Square). So a large portion of it was the System Design interview. When I was doing prep, I saw a LOT of expamles of Backend & Distributed Systems, but practically nothing for Frontend. I remember when I started frontend engineering, it wasn't even considered "real programming". JS folks were referred to as "script kiddies". Since then, FE has gotten significantly more complex. But maybe some of this stigma still remains. At both companies, my interviewers were actually Backend engineers! So I decided to take my prep notes and turn it into a collaborative, opensource GitBook. Since us FE folks need some love too!!! Would love to hear your thoughts, and feel free to make PRs. https://www.feinfra.com/ New TC: $395K (accepted verbally, signing tomorrow) YoE: 12y
Look into the book building micro front ends by Luca mezzalira. Covers a lot of useful stuff concerning sys design & architecture for modern UI.
Thank you!
Pretty good, thx for the resource
Solid guide OP. I think it'd be nice to have some more tradeoffs compared. Ex: infinite scroll vs pagination, cookie-based auth vs JWT, when to use websockets vs. webhooks vs. pub/sub vs. polling, etc.
Oh yeah those are good ones. Will cover for sure. This is just what I kinda cobbled together this weekend, but I want to really expand this guide as much as possible.
shouldn't system design interview also include FE? like CDN, endpoint design, authentication, those involves FE
Absolutely. Actually touched on all of those. I haven’t organized it quite too well yet. Open to suggestions on structure.
I agree. One of my favorite open-ended interview questions to gauge how much a candidate knows about how the web works is around there lines of “you type http://amazon.com [return] in a browser. Tell me what happens (eg interaction diagram)” So we’re talking DNS resolution (can be used for geo routing / load balancing), browser caching, reverse proxies, serving assets from CDN, etc etc