The Meta interview process began with a short recruiter screen, where I discussed my background, technical experience, and overall fit for the position, as well as details such as preferred teams and timeline. After passing the initial screening, I was invited to two technical coding interviews that focused primarily on data structures and algorithms. During these sessions, I was asked to solve medium-to-hard programming problems while explaining my thought process clearly, optimizing for both correctness and efficiency. The interviewers also evaluated my ability to reason through edge cases, write clean and readable code, and communicate effectively under time constraints.
Got connected through a friend who currently works at Meta, which fast-tracked me into the interview process. The first round was a coding challenge where I tackled a task involving user-item interaction logs. The subsequent rounds included a deeper discussion on designing an ML system for video recommendations. Lucky for me, I had spent hours on prachub.com prepping, which helped me nail the coding question on similarity computations. Ultimately, I received an offer but decided to pursue a different opportunity. Overall, it was a solid experience.
Interview questions [2]
Question 1
Design an ML system to rank and recommend short-form videos (Reels) in a user's feed, including how you'd choose features, handle cold-start, and pick an evaluation metric.
Applied online. Received a recruiter screen within two weeks covering background and role fit. Followed by a technical phone screen with coding (LeetCode medium-hard, arrays/graphs). Then a virtual onsite with 4 rounds: 2 coding, 1 ML system design (recommendation/ranking system), and 1 behavioral. Interviewers were professional and gave time to ask questions. Results communicated within a week post-onsite.
First stage was a screen round with behavioral and 2 leetcodes, one medium one hard, 15-17 min each. If selected, loop is 4-6 interviews. 2 desgin, 2 coding, 1 behavioral.
Interview questions [1]
Question 1
idiotic questions that can't be answered in depth in 35 minutes design, like "your solution isn't going to work, how will you handle it?" yea no sht this is a baseline bro, wait 15 seconds and ill talk about the optimal one.