First ever FAANG experience in my 14 years IT journey, Having some MNC and start-up experience so far.
Starting with -
Focus on Preparation, not for Luck. Luck will play it's role anyway and we have to play our role by preparing for best.
I wont be able to share questions (sorry), as that will not impact much. (Yes, 3 out of 5 were from top 100 FB questions. But hold on, please don't jump to conclusion like 100 filter etc. Because it will not be sufficient to get the result you are looking for, which is - "OFFER", after all these efforts.)
You are already doing good by Practicing. And trust me, before interview I was also looking for recent/shared questions but didn't work the way I was thinking. Instead of this what worked for me is - 'Practicing'
Approach -
I was also (kind of) worried (probably common feeling, no!), but I followed a plan, sharing if this can help (and I think most of you are already doing this or better than this may be) -
-
[BASICS] 'Before jumping' to competitive programming, revisited DS and started discussing with friends.(Discussing/Sharing helped a lot). In regular routine coding we may not use most of the basics as we all working on some stable frameworks or libraries or auto suggestion (and yes copy-paste 😉)
-
[TRICS] Yes, I also felt "Wow, I wish I can think of such solution in coding interview". 'It's very normal', and don't feel bad because this is called learning "NEW" thing. Now just after this timestamp YOU can come up like this in future. Yeyy!.
-
[DERIVED KNOWLEDGE] Now what if you did 300+ LC or 100 TOP of XYZ company and in interview you got a situation like 'Out Of Syllabus' 😂. Don't worry, if were not relying on count or statistical list of top/recent questions then with the help of BASIC + TRICS you learnt will help you to derive your own solution.
I am sure nothing new I am telling here, you all are rocking. Just in case if you need any help, I will try to answer (if that is appropriate.)
Thank you and all the best everyone.
Update-1
For System Design query - I created a mind map, extracted knowledge from multiple places (Actually very less content available for mobile side, for backend side you will get many)
One can apply this or something similar approach for any System/Product Design round, if finds is suitable.
Update-2
Trick to avoid multiple revisions - Start writing code ONLY AFTER crafting your own (end-to-end) algorithm or pseudo logic. Training our brain not to jump into coding/api/variables so fast (after so many years of such methodology) is difficult. Like we see a problem statement and we know some portion and jumped into coding and then in middle giving more thoughts around solving complete problem, next time it's going to be difficult again, so avoid this please.