Yesterday was day one of my two day E6 virtual onsite loop at FB. Two coding rounds, that were really straight forward (yes they're still asking LC hards). But what was interesting was the Product Design round. From what I understand, they used to give 2 systems design interviews and now for many applicants do 1 sys design and 1 product design. My product design round wasn't perfect, FB still needs to tweak the process so that it's clear what the interviewer's role is in terms of setting up the question and how to get proper signal, and have clear guidelines on what to expect as an interviewee. I actually think this ambiguity is hardest on the interviewer. But it was - FUN. You are there solving actual problems. Real world problems. You're improving systems and functions and data with actual code, but not toy problem code. Things you'd do on a real job. You talk through relational (or not haha) data, how these relationships with the actual APIs could be improved, how you could deliver to the client, who the client is, what the client needs. This is different from system design where you're worried about QPS, bottlenecks, scaling (which is also important, I'm not demeaning that part). This is a way to see if you understand how to "full stack" things from the interface to the data. They aren't there yet, but I do think they're close. And if they get it right, they could move to maybe 2 prod design, 1 sys design, and only 1 coding round and get better real world coding signal in prod design rounds instead of relying on whether or not you know exactly when to break out Kadane's for largest sum contiguous array. #interview #facebook
E6 loop been light on coding for a long time. Even my E5 interview only had two easy coding rounds. The behavioral and system design were much more important it seemed. So I think lead code is really dead at higher level positions
Ha, I had 4 questions yesterday, 2 LC mediums (one was really hard, one appropriately medium), 1 med, and 1 hard in the second round. I'm surprised the E5 loop was light on coding since they're relied on so heavily for coding.
Guess I came in as a higher e5 I felt I was under-leveled I got promo in less than 2 years.
What do recommend in terms of resources for preparing for product design interviews?
India
Yesterday
293
Modi 3.0 | First 100 days: Top 5 reforms you wish
2024 Presidential Election
Yesterday
314
Not looking good for dems
Tech Industry
2d
33531
You cannot make this up…
Tech Industry
Yesterday
734
Can everyone agree now that USA is a banana republic
2024 Presidential Election
Yesterday
2128
What crime did trump commit?
What role was this for? Sounds similar to my FB Solutions Engineer interview question where interviewer wasn't as concerned about scaling and QPS but more about client interaction and ease of producing a MVP.
E6. I think they're splitting it to 1 and 1 for more senior roles and doing 2 sys designs for the E2-5s for now. Ironically, the product design round (at least the way mine was) is well suited for non-senior roles because they should be well-versed on optimizing code, improving structure, eliminating wasteful static functions, etc - and less versed on large scale distributed system design end-to-end.