Facebook | E5 | Android | Offer
Anonymous User
273

I applied on Meta website and also reached out to couple of recruiter who were in touch for previous attempts i had taken. Got call from recuirter after couple of months in April. I expedited my phone screen since I was in touch and was aggressively looking out.

Got my phone screening done in April last week.

  1. Given building heights in an array and an ocean on the right hand side of the array, print all the building index which has ocean view.
  2. Question related to tree which i have forgotten :(

I performed well for both the questions and was done within 40 mins. Got confirmation for onsite within couple of hours.

Got in touch with my recuiter and scheduled next 4 rounds after 2 weeks time with 2 interviews a day, back to back.

Round 1:

  1. Given a string, convert it into integer. An easy question with many corner cases. Confirmed on all corner cases and coded the solution.
  2. Given two nodes having parent access, find the common ancestor. Gave solution using hashset. Interviewer nudged for better solution which i did by using slow and fast pointer.

Round 2:

  1. Given a string, return true if it is possible to create palindrome after rearranging the characters. Again naive solution was followed by a more optimized solution.
  2. Build a Data structure which has put, delete, last (-last accessed item) and get in O(1) time - Similar to LRU cache.

Round 3:
Design an in house push notification system similar to Firebase notification system. Focus was more on mobile of how would sync work.

Round 4:
Behavior round - More on previous work and scenario based questions.

Got offer in May, 2024 for E5 level.

In my experience, overall Meta looks at speed and optimized coding. Just getting the solution working on LC might not work and hence striving for 100% faster solution is the key to Meta.

P.S - Got through in my 3rd attempt so if you got rejected don't feel low and keeping working on your skill. Eventually, a day would come when you would be wirting a similar post :)

Comments (2)