Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
Interviewed recently? Share your experience to try it free, or become a member for full access.
“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.”
“The overall process was rigorous and comprehensive, more challenging than many interviews I have done with other large technology companies. However, the recruiter’s guidance was accurate and genuinely helpful, which I really appreciated. The interviewers were professional and respectful, and I felt the process was designed to evaluate both technical depth and practical problem-solving ability. What went well was that the process gave me opportunities to discuss my experience, research background, and approach to problem solving. What did not go as well was that a few questions caught me off guard, especially where I needed to connect fundamentals, implementation details, and communication under time pressure. Even though I was not able to answer every question as well as I wanted, the experience helped me understand which areas I should strengthen further.”
“The overall process was rigorous and comprehensive, more challenging than many interviews I have done with other large technology companies. However, the recruiter’s guidance was accurate and genuinely helpful, which I really appreciated. The interviewers were professional and respectful, and I felt the process was designed to evaluate both technical depth and practical problem-solving ability. What went well was that the process gave me opportunities to discuss my experience, research background, and approach to problem solving. What did not go as well was that a few questions caught me off guard, especially where I needed to connect fundamentals, implementation details, and communication under time pressure. Even though I was not able to answer every question as well as I wanted, the experience helped me understand which areas I should strengthen further.”
“Technical screening wasn't that hard. Have to solve 3 SQL and 3 Python. You are fighting against the time.”
“More difficult than I had expected. The questions were new, and there was a lot more counter questioning than expected. Especially in the product design round.”
“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 interview process consisted of several stages: an initial recruiter screening, an online assessment, technical/product interviews, and a final round of behavioral interviews. The recruiter screen focused on my background, product experience, and motivation for applying to Meta. This was followed by an online assessment that tested my product thinking, analytical skills, and ability to structure solutions clearly. In the technical interviews, I was evaluated on product sense, execution, and analytical thinking. I was asked to design product features, define success metrics, and walk through how I would investigate changes in key performance indicators. These interviews emphasized structured thinking, user-centric design, and data-driven decision-making. The final stage included behavioral interviews, where I discussed past experiences, leadership, conflict resolution, and how I align with Meta’s values. There was a strong focus on collaboration, impact, and ownership. Overall, the process was rigorous but well-structured. It largely matched my expectations in terms of the focus on product design, metrics, and behavioral fit. The emphasis on clarity of thought and structured problem-solving was particularly consistent with what I had anticipated. ”
“The process was standard, with a recruiter chat first, then scheduling round 1 with 2 PMs: 1 on product sense and the other on metrics. Product sense - the interviewer likes to know how you frame the problem, set goals, and how it ties with the overall company strategy. Make sure to be concise and walk users through problems to solutions before time is up.”
“Clear, some interviews are chiller than others. Just need to put in the work and you'll be okay. Should know all of the Meta products well enough to do an interview on them. ”
Preview full access of other recent interview experiences
“The weirdest Anthropic round was the company values interview. It was almost like a therapy session, and honestly if you went to a therapist at some point, you will pass that round much more easily.”
“What was very unusual is they didn’t give me any tooling to draw the system design, so I just sketched it on a piece of paper and talked them through it, then we got into this oddly deep debate about whether hover-over history should count as a recommendation signal.”
