A recruiter cold-reached out to me for an E5 software engineer role, and the whole process felt very standard Meta. I had a short recruiter call, then a coding screen with two common problems in one session, and I actually did poorly on the easy one but still barely made it through. After that I got the full loop spread across multiple days, and they gave me a few weeks to prepare. The final coding rounds were mostly standard too, but I felt weak in behavioral because I did not have the right work stories ready, especially for conflict, and I think I mishandled system design by not controlling time and not setting scale assumptions myself. I got the rejection after the final round.
I got into Meta through a referral, and the recruiter reached out quickly. The process was recruiter chat, then a pre-onsite package with CodeSignal, a live technical screen, and a weird multiple-choice engineering philosophy questionnaire, and then about a month later the onsite with DSA, system design, behavioral, and the AI-enabled coding round. Honestly, Meta gave me the best prep materials of any company I interviewed with: a long prep PDF, portal videos, mock system design resources, and even a practice environment for the AI round. Most of the coding questions were exactly the kind of stuff people tell you to study in the Meta-tagged LeetCode list, so I never felt like they were hiding the ball. I didn't get the offer, and I think the system design round was what sank me because I expected distributed systems and got an API-design style chess problem that I handled in a really unorganized way.
The process is quite messy. The recruiter reached out back in August, and then when I expressed interest it took her another couple of weeks to get back to me. Then another week to schedule initial talk with a team member. Then I had two screening interviews with members from Reality Labs, none technical but talked about past projects, how I see myself fit in the team, what can I contribute, etc.
The interview was a standard FAANG type of interview, where the recruiter screen talked about resume and behavioral questions, and the first coding round was a non-AI traditional leetcode question.
The process was pretty rigorous, mainly because the bar at E6 felt more about scope and judgement than just solving the questions. Recruiter was clear and helpful. The coding rounds went ok, but I spent too long explaining some edge cases. Design was probably the strongest part, good back-and-forth and tradeoffs. Behavioral was fine, though I could’ve been more specific with impact numbers. Overall, a solid process but definitely tiring.
Basic process. I guess much shorter for interns. I think they just ranked us by our DSA scores and took on as many as their quota let them. Not too adverserial.
The interview went smoothly overall. 1 round of phone screen followed by the full loop of 4 rounds packed in a day. 2 coding 1 behavior 1 system design.
The process was smooth, general interview skills, prepare well to discuss you solution before coding / jumping to the optimized solution
Meta is still leetcode heavy and medium to hard questions should be expected.
Since it's leetcode style interview you can predict the out come and also prepare easily.
What didn't go well
- For the second question couldn't walk-though the code with example due to time constraint.
- I spent too much time explaining my approach for both problems.
Overall keep your thoughts concise and finish the code first to quickly finish both questions.
Software Engineer
1. Applied through careers portal
2. Technical screen from the interviewer
The interview began with a brief self-introduction, followed by two questions:
Most challenging project.
What do you want to work on at Meta?
The discussion lasted exactly 15 minutes. The interviewer did not interrupt at any point. Notification of passing the initial interview was received after an hour.
Overall, the interview process was pretty straightforward and well organized. The interviewers were friendly and gave me a good opportunity to talk through my experience and approach to problems. The process was a little lengthy, but overall it was a positive experience.
Software Engineer
Phone Screen:
Question 1: Variation of Valid Palindrome II (Easy/Medium)
Question 2: Kth Largest Element (Quickselect approach expected)
Verdict: Strong Hire. I finished both in ~35 mins.
---
Onsite 1 (Coding):
Question: A graph traversal problem similar to "Shortest Path in a Grid with Obstacles Elimination".
Experience: I almost froze here. The interviewer added a constraint I hadn't seen before. This is where my prep strategy (which I’ll mention below) really saved me. I was able to vocalize my thought process clearly because I’d practiced exactly this scenario—getting stuck and un-sticking myself.
Verdict: Lean Hire / Hire.
---
Onsite 2 (Coding):
Question: Merge k Sorted Lists (Classic).
Experience: Easy. But they drilled deep on heap memory management.
Verdict: Strong Hire.
---
System Design:
Design: Design a notification system (like alerting 1M users for a flash sale).
Verdict: Hire. Focus on fan-out service and queue handling.
---
Behavioral:
Standard "Tell me about a time you had a conflict". Used STAR method.
Overall, I felt that the interview went well. I was able to clearly explain my experiences, discuss the projects I have worked on, and connect them to why I was interested in the position. I was also comfortable answering technical and behavioral questions, and I think I communicated my thought process effectively rather than just giving short answers.
The Overall Interview ProcessStep 1: Online Assessment (OA): A 60-90 minute screening on platforms like Codility or HackerRank, often featuring 2 LeetCode Medium coding questions and sometimes logic or SQL-based multiple-choice questions.Step 2: Technical Screening (often via Karat): A live technical interview with a third-party partner like Karat. This focuses on core Data Structures and Algorithms (DSA) and fundamental software engineering principles.Step 3: Technical Deep-Dive / Team Panel: A more thorough session with Citi engineers focusing on System Design, Java/Python specifics (like multithreading or database ACID properties), and a deep-dive into your past project architecture.Step 4: Hiring Manager / Behavioral Round: A "culture fit" discussion using the STAR method to evaluate your teamwork and communication, often ending with HR discussions on salary and policy
The process started with a recruiter screening testing some behavioral questions and some technical questions she read from a question bank. Then, I did a coding interview online. Finally, a 4 rounds loop online (as opposed to my previous attempt when I did the loop in one of their London (UK) offices): 2 coding interviews, 1 system design, 1 behavioral with an engineering manager.
Frontend Developer
I just went through a full multi-round interview for a Frontend Developer role and honestly it was one of the most eye-opening experiences. Sharing everything here so you don't go in blind.
Round 1 was a short HR call, maybe 15-20 mins. Nothing crazy. They just wanted to see if I could communicate, if I actually cared about the company, and of course the usual salary and availability questions. Just be honest and don't overthink it.
Round 2 was a timed HackerRank test. JavaScript problem solving, DOM stuff, some React MCQs and debugging. The thing that saved me was revising beforehand. Promises, array methods, event loop, optional chaining. Don't sleep on the basics. They care way more about clean readable code than some overly complex solution.
Round 3 was the big one. First half was live coding where I had to build a small component and literally talk through everything I was doing. They were watching how I think, not just what I typed. Second half they opened my actual GitHub and grilled me on my own projects. Why I made certain decisions, how I handled errors, what I would do differently. Be ready to explain your own work inside out. A simple project you know deeply beats a fancy one you can't talk about.
Round 4 was frontend system design. Not the typical backend stuff. They asked me to design something like a scalable image editor with routing, state management, file uploads, caching and offline support. The tip here is don't jump into code immediately. Walk them through requirements first, then components, then data flow. It shows maturity even if you're junior.
Round 5 was basically a vibe check. How do I handle pressure, how do I work with designers, what do I do when I'm stuck. They're hiring someone they want to work with every day so just be real, be curious and don't pretend to be something you're not.
A few things I wish someone told me earlier:
- Talk while you solve. Silence kills you in interviews even if your answer is right.
- Your side projects are more important than you think. Clean folder structure, good commits, a README that actually explains things, a live link. These things get noticed.
- Say when you don't know something. It actually comes across as more confident than bluffing.
- And honestly just practice explaining things out loud. Clear communication impresses more than complicated code every single time.
Software Engineer
1. Coding interview via zoom
2. 1 x coding problem, 1 x behavioral, 1 x system design
The process was very straightforward. In both technical rounds, I was asked questions from the top 50 Meta tagged LC questions list. Behavioral was also very standard.
I got HR reach out, and start to prepare the interview around 2 weeks
I didn't complete the coding section. Having some diffcult to communacate with the interview
Software Engineer
It was hard. Two medium leet code in 45 minutes and you're alright. System Design needs lots of practice and quick explanations.
Software Engineer
Software Engineer
1. Clone the graph
2. Given a stream of integers, find the average sum of window size k
Other questions below
the system design round threw me off a little bit because it was related to quad tree and some geo distance concepts which I wasn't familiar with
- normal questionnaire
- one question was related to quad tree
- one hashmap related question
It was a pretty standard interview. Didn’t have a single behavioral and everything was based on the technical, didn’t do perfectly, but still got the offer
- Implement a circular buffer.
- How would you implement malloc?
The technical rounds were generally well structured and covered both coding and system design. I performed well in most of the technical discussions, but I found the system design round more challenging. Overall, the process was professional and gave me a clear understanding of the technical expectations.
- everyone was super nice
- questions were like leet code but with a twist
- time complexity always asked
Not a lot of time, have to solve 2 questions in an hour. Needed to budget my time wisely and make sure I can get both questions done.
It went well it was clear on what to expect and the recruiters do prime you well from the start. They will let you know what to expect and prep required per stage. Usually there was enough time and you just need to think about it well rather than rushing to an answer.
I did well on well on very coding question except 1, it was a cyclic sort problem and I actually didn't know cyclic sort at all. After doing the final round, they gave me another chance to another coding round, I again failed at the first question but not the second. So I got rejected
Focusing on leetcode was sufficient, escpecially the leetcode premium. the hard part was behavioral and needed real examples
Leetcode was doable based on the LC premium curated list, questions were similar. Culture round required thorough prep of examples for similar questions
My interview process started with a CodeSignal GCF online assessment that had four sections with increasing difficulty. The earlier sections were more straightforward and focused on implementation speed and correctness, while the later sections required more problem-solving depth and handling more complex constraints under time pressure.
After that, I had a technical interview consisting of two LeetCode-style medium questions in a 45-minute session. The focus was on both arriving at efficient solutions and clearly communicating my thought process while working through each problem.
What went well was my ability to understand the problems quickly and stay consistent across different difficulty levels. What didn’t go as well was pacing, especially in balancing correctness and optimization within the time limits.
Practice leetcode fundamentals (graph, tree), practice system design fundamentals, speaking/thinking out loud, being able to explain full flow of what happens from when user/request is received to processed to returned (ensure components are disconnected/missing a flow path)
Software Engineer
Software Engineer
It went pretty well. The interviewers were very nice, so it was easy to talk through my behavioral stories without putting on a super professional act. Coding challenges were mostly medium leetcode questions.
Initially considered for IC6 but performed poorly in the system design so got down-leveled to IC5.
For IC6 consider how your system interacts with other systems.
- Describe your day-to-day.
- Leetcode medium
- Leetcode medium
The whole process was smooth for me, prepared well from meta tagged leetcode questions and for system design hello interview was more than enough
- Design a web crawler.
- General questions around experience, motivation, etc
- Leetcode based questions - 1 medium and 1 hard
The overall interview process with Meta was structured and fairly fast-paced. The interviews focused on technical problem-solving, system design, and behavioral questions, with an emphasis on explaining my thought process clearly while working through problems.
What went well was the communication throughout the process and the consistency of the interview format. The interviewers were professional, and I felt I was able to clearly explain my reasoning and experience. The biggest challenge was the pace of the technical rounds. There was limited time to work through multiple problems, so there was not much room to recover if you spent too long on one approach. Overall, it was a challenging but well-organized interview process.
It mostly went well. I was thrown off by the fact that a lot of the focus in the system design rounds was on the product and UX side, only to discover it was product architecture later and that there had been a miscommunication.
Coding focussed with focus on leetcode style problems. The design prompts are simple and abstract like design netflix or design instagram, etc. It is upto you to drive design discussion and this round decides leveling
It was very rigorous and I feel like they really emphasize on writing bug free code. I feel like I failed by sounding like too much of a start up person during my behaviorals and they were afraid of me leaving.
The process was what was expected and they were quick in scheduling and re-scheduling as needed. All questions were ones I had seen before via LC tagged.
Software Engineer
Technical questions move fast, dont trip on edge cases. 2 questions in 60 min slot, with multiple followups. Code quickly. With 10 min of intro and questions theres not much time.
It was an extremely smooth process, though team matching was rough. Questions didn't need to be 100% right interestingly, as one of the rounds I didn't finish.
Along the interview process, I think the recruiter reached out and she was very friendly. Things were smooth. I think I had multiple rounds and overall the interview process was great.
It was overall a smooth experience. Be prepared to wait for 2 weeks to schedule interviews due to lack of interviewers.
Software Engineer
Software Engineer
Software Engineer
Software Engineer