Health & Wellness
Yesterday
1027
Issues with sleep
India
Yesterday
3543
Why is it so G*damn difficult to move money out of India
2024 Presidential Election
Yesterday
1537
Uh oh: President Trump leads Biden 49% to 43% in a two-way race.
AMA
2d
3570
I have worked at TikTok US core tech for 3 years. AMA.
Tech Industry
Yesterday
836
Musings (rant?) of an old timer
I have an E5 interview and was told that i can chose between System design interview vs Product Interview. Since i havent worked on low level systems much, i picked Product Design. Can someone tell how different this interviews are? If possible provide some examples? #facebookdesign #facebooke5 #facebook YOE: 6 TC: 220k
I was asked the following at FB product interview: Implement privacy api - takes post id and user id as inputs and returns true/false based on whether the user can see the post. Started with basic stuff - a post can be set to self, friends or everyone. Expanded to groups or any random combination of users. Next round, build facebook chess.
Wow. How did you prepare for this?
Similar to system design interview, more or less.
Can anyone post some example of kind of things they were asked for system design?
This series is pretty good and close to the actual level of detail expected https://youtu.be/vvhC64hQZMk
I have 2 YOE and my TC is higher than you
FB Recruiter here Product - recommended for candidates working full stack/middle tier backend. Think APIs, data modeling, how the client and server interact, how a user may interact with it, etc. If you are currently working on a user facing product, this may be a good choice. Systems - Large scale distributed systems. Very large scale. Think availability, scalability, partition tolerance, reliability. Storage, databases, core systems.
Another way to think about it is the AWS line: Would you feel more comfortable building a product and plug and playing AWS services Or do feel comfortable actually building AWS like services that handle massive traffic?
I kinda disagree (SWE) here. If you know how AWS products work and can plug them then you should go for systems design. Product design is more for Front end or full stack engineers. If you don't know how to build a system that can scale out; then product is the way to go.
My friend(fullstack bg) who interviewed at FB recently chose system design interview and did not perform well, but they still gave another follow up round for product design and he nailed it with E5 offer. Just a data point and good luck op!
I've got downlevel to E4 because i didn't perform well for Product design. So if you read grokking the systems design, it's actually for systems design; not for product design.
Good Choice
It sounds more and more like Product design interview is more of an Object oriented design interview, would you say that’s true?
Could you share with us if Were you able to figure it out?
Hi Guys, I have an interview coming on next week and I have also selected Product design and really want to know where should I learn or prepare for that interview. And video link or article would be great. Confuse about how deep should I go? Like creating classes or just an API definition. I am very confident in DS/Algo and behaviour round.
If you haven't worked on system before, you made the right choice
What does system involve? Distributed systems or comp architecture/os etc?
I don’t think the difference between those is very big...