The interview process consists of two stages.
First, a technical screen stage. You have the option to take this over the phone or in person, onsite. Typically, an average difficulty LeetCode programming question is asked for this round.
Tips to succeed in this stage:
Handling of corner cases has significant weightage in the interview.
The second stage is a series of onsite interviews, generally comprising four 45-minute interviews each.
For the coding interviews, again, LeetCode average difficulty level questions will be asked. You will be evaluated on how quickly you come up with a solution, how you optimize your approach to arrive at the most optimized solution, how cleanly you code, and how you consider all possible scenarios/test cases while implementing the code. Ideally, you should be done with all of the above within 30-35 minutes, allowing you time to discuss your implemented code and ask questions to the interviewers.
For the system design interview, a distributed system design question will be asked. You need to discuss the system in detail before talking about its design. The interviewer will try to steer the discussion in a particular direction, so go with the flow and let them analyze your skills. Be as verbose as possible.
Finally, the resume deep dive interview will involve an in-depth discussion of projects mentioned on your resume. Be thorough with all projects and skills listed on your resume.
My interview experience was good. I cleared the technical screen and completed the onsite interviews but did not receive an offer. All the interviewers were nice and soft-spoken, and they made me feel comfortable. The interview process was quick, and they provide you with enough time to prepare if you ask for it.
I was contacted by a recruiter in late February. I scheduled my technical screen for mid-April, received the result within two days, and then scheduled the onsite for mid-May. The result of the onsite interviews was also communicated within two days. The questions are below.
Given two very large numbers in the form of strings, multiply them and return the result also in string format.
Given an array of integers and a sum, return the indices of the subarray which adds up to the given sum.
Implement a typeahead feature.
Implement an online chat system.
The following metrics were computed from 359 interview experiences for the Meta Software Engineer role in Menlo Park, California.
Meta's interview process for their Software Engineer roles in Menlo Park, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Meta's Software Engineer interview process in Menlo Park, California.