I am going in for an FB leadership interview and last time (3 yrs ago) was dinged, even though I did good on the mgmt and algorithm interviews. Kept scratching my head and later found out that from recruiter that I wasn't as organized in my approach to debugging issues - which was the focus of the 3rd interview. Trying to prep a little bit more this time. Wondering if there is "standard" process to go through during interviews. Somewhat similar to the system design process available on a bunch of sites. In practice we do things a bit intuitively but that won't fly during an interview. As an example: service crashes, what do you do? I would look at crash dump, traffic load, etc., Identify if it was a app related crash or a scale crash and act accordingly. But this evidently wasn't enough. Also as an aside - do m2, d1 folks actually get hands-on?
Where can I read about the structured system design process? Please
Search GitHub for 'system design primer'
Thank you
Tech Industry
Yesterday
2220
TESLA UP 14% AFTER HOURS ๐๐๐๐
Tech Industry
Yesterday
3069
ByteDance is officially fucked
Tech Industry
Yesterday
232
Why some people are more successful than the other?
Tech Industry
Yesterday
863
The new Tesla Model 3 P goes from 0-60 in 2.9 seconds
Ask Blinders
Yesterday
927
Tipping culture is really getting out of control! Waiter gave me โa lookโ because I tipped her 10% for โBAD service!โ
Maybe U did not ask questions
Definitely. After i read up on the systems design process, i think a structured approach is required otherwise you tend to omit a bunch. In practice, you usually have more time than the 20-30 mins you get during an interview. When you accidentally omit stuff in an interview it is seen as a big problem.