Meta Software Engineer interview questions

One Phone Interview. Three questions. Leetcode Medium level. Then onsite after two weeks. 4 rounds of whiteboard interviews. Interviewers we pretty chill. One leetcode easy and other questions were of leetcode hard level. Screwed up the easy question (brain freeze I guess). Managed the hard questions with the best possible complexity but missed a few edge cases and some silly mistakes that could have been avoided. I guess they look for a complete working solution with the best time complexity. Got a generic reject mail within 2 weeks. Overall a positive experience !

I was contacted by a recruiter who sent me information and when I was ready could schedule my first phone interview. They are overbooked on interviews so it took 2 weeks to get one scheduled. They use coderpad+ a phone call and it is straight to business on a couple coding problems, there was no discussion of my resume, experience, goals etc. If the interview isn't a solid positive but not bad either, you might have to do a second one, same as first, same 2 weeks to get rescheduled, different interviewer and question. The interviewers are randomly assigned from different teams, it seems to be pretty hit or miss there is little feedback from the interviewer on what they are looking for from you. They just say thanks and that you'll hear from the recruiter afterwards. I was told it would be pretty much a same day response but it took a week to hear back each time. The first time the feedback was that there was no issue with the solution but the interviewer wanted a more vocal, step by step explanation while writing it. He did not say so during the interview though. The second interviewer seemed confused about a recursive solution and asked to have it redone as iterative despite there being no differences performance wise and his final feedback was that the second problem did not have a full solution despite him explicitely saying during the interview that since his request for a iterative solution took up more time that I should not write the code for the second problem, just vocally describe it . Both interviewers did not seem very engaged in the interview so I suppose the take away here is to always be as explicit and vocal about your solutions and try to get the interviewer to tell you definitively what they want because otherwise they just mostly quiet and you only find out afterwards when it is too late. The actual difficulty of the problems seem on the easy side, you need to be able to explain the Big O if your solutions but none of the ones I had involved any complicated tricks.