[Meta] - [Software Eng] - [Onsite]
Level: [New Grad]
Education: [Bachelors]
Years of Experience: [0]
Questions Asked: [List of Questions Asked]
Hey everyone, I recently completed the final loop for Meta New Grad 2025. I found a lot of posts on here to be very helpful, I’m gonna try to summarize my entire experience, hopefully someone can learn from it.
Firstly, for the last couple years i’ve only applied to jobs through the alerts I’ve set on LinkedIn. I was suspicious why i never see Meta postings as a lot of people around me keep getting interviews, turns out I never included Meta in the LinkedIn filters, so i never saw a single Meta posting util i graduated recently. Finally, the next day i saw a new grad posting, applied September 20, 2024. Heard back from a recruiter September end.
OA scheduled for October second week. I hadn’t given too many OA’s in the past, had no confidence that i’d pass but i had done some leetcode, mostly Blind 75. I wanted to prep but i couldn’t get myself to be amped cuz i’m like what’s the point im gonna fail and would be put on hold for a year before applying. Just gave the OA on the last day without prepping much. I was able to get the first two (pretty intuitive), and the fourth question (Although it passed test cases it said it wasn’t optimal). The third question was failing all cases but my answer was only off by a very small margin due to some bug i couldn’t figure out. To my absolute surprise ( didn’t know what the expectations were for OA), I received a callback and was told i’d be moving on to final loop. That gave me confidence and a “Maybe i can actually do this”.
Final Loop, November second week. 3 interviews, 2 technical 1 behavioral. Couldn’t study consistently some friends and family were visiting, had to show them around and working full time. Prepped well for behavioral though and did top Meta tagged last 30 days repeatedly. Thought i did about 50 but only 30 were top tagged and 20 were questions i had done previously.
Technical # 1 - Great round, great interviewer. 1 easy, 1 medium. Had done some mocks so i followed the following format. Clarify question, discuss edge cases, discuss approach, code, discuss complexity. Got the easy optimal without hints. Got the medium without hints. Didn’t realize it was suboptimal until he asked how to improve it, it was sorting in nlogn. After he gave a hint, I figured it out immediately, kicked myself because i had seen that optimization before but hadn’t practiced it in code. Got the optimal solution.
Behavioral - Great round, great guy. A lot of questions, felt slow paced rapid fire. Most Impactful project? What challenges did you face? If conflict, how did you convince them of your opinion? How did you cede to their opinion? What do you lack? Example of how you worked on it and put yourself out of your comfort zone? Looking back, what would you have done better? Plus a few more followup project related questions. Overall i was satisfied, prepped answers in a STAR format, kept them concise and relevant, honed them using ChatGPT, picked a project big enough so it can be broken down to its core and I’m able to answer all followups.
Technical #2 - Ass, absolute ass. First question was the type of question you see and you know you’re cooked. Tried hard, came up with a brute force solution. Did a dry run, it worked fine, but it was probably buggy with a really high time complexity. But the problem with this round was that i was trying to communicate and prompt the interviewer but they didn’t say much. After a point i stopped expecting any communication and just did my dry run. After i finished i asked if they were following, and they were looking elsewhere and asked me to repeat the dry run. I was pretty disappointed cuz it was a long ass test case, it took 5-6 minutes do it again, and it was evident we wouldn’t get anywhere so we could’ve moved to the next question. Candidates were told not to worry about time and it’d be managed by the interviewer, but didn’t feel like it. I knew the next question and explained my approach and edge cases, but just a couple minutes after we started the interviewer said time’s up, couldn’t code.