- Published on
Meta | E5 | Seattle | Reject
- Author
- Shared Anonymously
System Design:
Proximity services, design FB search for nearby businesses.
Used same concepts as design yelp. Feel good about this one, provided a bunch of optimizations and the time ran out. Interviewer mentioned that it's okay, I've already provided more than enough information.
Coding 1:
https://leetcode.com/problems/add-strings/editorial/ , the caveat was integers can have decimal "5.09"
Coded this one, while running through the test cases found a bug and fixed that too.
https://leetcode.com/problems/binary-tree-right-side-view/editorial/
Provided the 2 queue solution as only 15min were left. Verbally mentioned about a small optimization.
Coding 2:
https://leetcode.com/problems/powx-n/editorial/
Provided optimal solution
https://leetcode.com/discuss/interview-question/568482/facebook-phone-merge-3-sorted-arrays
Provided optimal solution, provided incorrect Time complexity. I said it will O(length of longest array) but it should have been O(l + m + n), where l,m,n are length of the three arrays.
Behavioral:
This was kind of weird experience, the interviewer wasn't interested in listening to the STAR methodology, rather kept asking about learning. Kind of threw me off a bit :(
Tell me about a time when you had difference in opinion with a teammate
Tell me about a time when you had to pivot in the middle of a project
Tell me about a time when a project got delayed
Tell me about a time when you had to pick up a new technology
Tell me about a time when you mentored someone
Received a reject from the recruiter after two weeks.
My take is don't take the behavioral lightly. Even though I had prepared scenarios for some questions, I couldn't fit them in the questions that were asked to me and I got a feeling that the interviewer wasn't satisfied in the call itself.