Meta Software Developer interview questions

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.

A recruiter had contacted me in the past, I decided to go ahead with the process now. Had first technical screening interview, I opted to do at Menlo Park office instead of phone. It was purely data structures and algorithms. He gave some hints which I did not take in first go but I did understand and solved the problem, so he gave mixed feedback, I was asked for another screening. Did it again at Menlo Park office. It went very well and I was invited for onsite. During onsite had 4 interviews, 2 coding, 1 behavioral + small code and 1 system design. At the end of system design, the interviewer said Good job. I did pretty well in the coding rounds too, Each coding round, I could solve two problems which is a good sign as per whatever I had heard from friends. But, I did end up getting rejected. Well, rejection is a part of interview process but the frustrating part was the feedback. Recruiter said unfortunately we cannot proceed with the offer as your system design did not go well. I was shocked and realized from the other glassdoor reviews I had read that it is the standard response they give because it is an open ended question. My coding rounds went very good so she couldn't say those were the bad ones. I told the recruiter that it is contradictory to what happened and she had nothing to say except for - we will ask our engineers to not give any verbal feedback. What the hell!!! Is this what you expect from companies like Facebook. Don't waste your time interviewing here if you don't have relevant work experience (I don't have that). They will reject you with system design feedback. Crap!!