Meta Interview Questions

phone interview starting with introducing yourself followed by two code questions. The first coding question is very standard coding question and the second one is a little more related to facebook's certain functionality

2 rounds of leetcode - first question was on finding the LCA of 2 nodes in a binary tree. Explained the O(log n) solution to the interviewer - he was impressed. Second was count the number of one's in a rectangle in a grid given the top left and bottome right corners - inclusion-exclusion dp.

I interviewed for the Technical PM role within the AR/VR SoC team. I applied for a remote position, which was a significant factor in my interest. This remote aspect was confirmed with both the agency and the actual hiring manager at the outset of the interview. Throughout the interview, it became evident that the hiring manager's primary focus was on my previous team structure and industry knowledge, rather than evaluating my qualifications and skills for the role. This raised significant red flags regarding the true purpose of the interview. I discovered that the hiring manager's division was in its early stages of development and actively restructuring the team. While some questions about my background were expected, the interview should have provided a balanced assessment of my fit for the role. My previous employer is one of the sector leaders in the industry.. The rejection reason provided was that they were seeking hybrid candidates, which contradicted both verbal and written communication. I hope that META HR can accept this feedback constructively to enhance its interview process and ensure fairness and professionalism for all candidates. The interviewers should aim to evaluate candidates genuinely rather than attempting to extract industry knowledge. If META HR wishes to reach out to me, I am willing to provide all the details, dates, and exact names from Meta and the contractor agency to shed light on any questionable practices.

For interview they use a STAR method process with real case scenarios, and you should use this method to every question they ask you. Interview normally is 4 rounds with HM, team leads and team members.

I was first given an the OA where I had to do some easy level leetcode easy questions. Then it was a round of some behavioral questions. I think the overall experience was good, however when reciving the first round of the itnerview I would definately practice alot of leetcode easy and medium questions specfically about string and arrays

Technical screening phase. It was very open ended but you have to mention the key words of not the interview will just run it’s course till then end with no outcome after

Call with HR ( they will ask you to talk about yourself and give you a job description) First round of coding interview ( easy question, last 30 mins) Second round coding interview (in person)

Easy. Phone screen. Not much to it. General questions about my work history and career ambitions. Learned a bit about the team too. Easy. Phone screen. Not much to it. General questions about my work history and career ambitions. Learned a bit about the team too.

Having been contacted by Meta (and interviewed for them) 3 times in 4 years for the same role, you'd have thought I'd have some idea of what they were looking for. But then, that kinda assumes they have an idea of what they're looking for. Each interview has been just a bit off. Questions quite often feel like a trap and there's very little back and forth between candidates and hiring managers. Hard to build rapport or get into the details of what you do/how you work. It feels like a very corporate tick-boxing exercise. It gives the impression that the recruitment game is to 'stack em high' from Talent Acquisition so that hiring managers have to filter large volumes of candidates. Almost everyone I've met seems disinterested and a long way from loving what they do. A reliance on the brand name also comes through in swathes. Quite a 'you'd be lucky to work here' attitude which is just off putting. The whole process lacked a sense of honesty and authenticity about expectations or the reality of the role.

It was two coding challenges with an engineer. The interview was rescheduled a few times. The interviewer was nice and gave some clues to tackle the problem. After that there would be a cultural fit interview.