Preparing for an interview? Check out Cracking the Coding Interview
Published on

Meta E6 Phone Screen (Accept)

Author
  • Shared Anonymously

I had a phone interview today for Android E6 with meta. My interview was about 15 mins of behavioral, followed by two coding challenges for 40 mins. Wrapped up the coding in 30ish minutes, and interviewer asked follow up questions to make things a bit harder. Heard back from recruiter literally 30 mins after the interview, and she said this was the fastest turn around she had probably seen from interview to let her know to call for onsite. Feedback was apparently all positive, with a note that one of the problems, I solved with unnecessary extra space complexity, but they were pretty sure I could fix that with a couple of extra minutes. Interviewer also enjoyed the functional, and clean/easy to read code, and all the things I said to express my thought process clearly. They were also impressed with testcases I came up with, and walk through the problem once it was done.

I initially talked to recruiter for E5 when she contacted me. But, she chatted with me for much longer than our scheduled time, and thought I should 100% do E6 instead of E5. Never really seriously considered FAANG in the past because I'm pretty happy with what I do at smaller companies, and they pay pretty much the same level as them (only true because of successful funding exits). But, when recruiter mentioned E6, I was pretty interested to give it a shot, though I always hated algo/DS interviews.

Coding today was two medium LC problems. Not exactly these, worded a bit differently, and had a couple of follow up questions to verbally talk about:
https://leetcode.com/problems/merge-intervals/description/
https://leetcode.com/problems/minimum-remove-to-make-valid-parentheses/description/

I had prepped for 2 weeks or so, solved 70ish LC problems, but really studied editorial, and other solutions in as much depth I could get into to understand "why" instead of "what". That helped quite a lot.

I have given my availability in 2-3 weeks time frame. So, will see what happens there. Recruiter mentioned that bar for onsite coding is also higher than phone screen, and sys design will all focus on building a mobile app, and must dive into atleast 2 components of the app, if not more, in real depth within 45 minutes. That's gonna be fun.

ReportMark as Helpful