READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 86 of 153
Interview experiences · Meta
Meta Data Scientist Interview Experience — SQL and Product Sense in a 45-Minute Screen
Giving back to the forum. I scheduled this interview in late March for early April. The interviewer was very nice and patiently gave me hints — maybe a few too many hints, so I'm not sure how it'll turn out. I didn't hear anything within 24 hours, so I'm probably out, but I don't think I could have done any better. While it's still fresh in my memory, let me share it with everyone. Round 1: Techn…
Interview experiences · Meta
Meta Data Scientist Interview Experience — SQL and Product Sense on a Group Call Feature
The interviewer was a very energetic and friendly woman, and everything she asked me was about group calls. The premise: Messenger has groups, but no group call feature. The first SQL question was pretty common, but the second one I'd never seen before. What percentage of today's active "gb" users had more than 50 call records in the previous 7 days (counting both calls made and calls received)?…
Interview experiences · Meta
Meta Data Scientist Interview Experience — SQL, Behavioral, and Analytics Execution Rounds
The behavioral round was also some classic questions. For this round I also prepared one example for each question mentioned on the forum — when I got something similar in the actual interview I just tweaked the answer slightly. For the result, it helps to state it clearly, so the interviewer understands exactly how your action solved the problem well and got a good outcome. The questions I got w…
Interview experiences · Meta
Meta Data Scientist Interview Experience — SQL, Fake Accounts, and an AI Ad-Creation Case Study in the Onsite
I just finished my virtual onsite a little while back. I ran into a few questions that other people have already posted about, but with slightly different follow-ups, so I wanted to share. SQL: active_ads. The interviewer was very organized and gave clear instructions. My second question was to find people whose total spend last year was over 1k, then look at what share of their spend this year t…
Interview experiences · Meta
Meta Data Scientist Interview Experience — SQL Then a Teen-Safety Product Question
In early May I got an interview invitation from HR, so I scheduled the phone screen for late May. After the interview started, we chatted for about 10 minutes, talking about why I wanted to join Facebook. Then the DS interviewing me asked whether I wanted to start with SQL or a product question. I picked SQL first, and we jumped straight into it: Table: Date, Timestamp, sender_id, receiver_id Thi…
Interview experiences · Meta
Meta Data Scientist Interview Experience — Three of Four Onsite Rounds Done, Technical Session Pushed Two Weeks
I finished 3 out of 4 rounds of my VO (virtual onsite) yesterday, and while it's still fresh in my memory I wanted to share the experience. The reason I only got through 3/4 is that right after my third round, the recruiter told me the final Technical session would need to be rescheduled — it ended up getting pushed two weeks out, which feels like such slow torture (I originally wanted to knock o…
Interview experiences · Meta
Meta Data Scientist Interview Experience — Three Rounds Done, Final Technical Session Pushed Two Weeks Out
I finished 3 out of 4 rounds of my virtual onsite yesterday, so while it's still fresh in my memory, let me share my experience. The reason I only finished 3/4 is that after the third round, I found out the recruiter said the final Technical session needs to be rescheduled — it ended up getting pushed two weeks out. Such a slow death (I originally wanted to knock out the whole day in one go, spec…
Interview experiences · Meta
Meta Data Scientist interview: SQL, product sense, and the full loop
A recruiter contacted me first, and I then went through what felt like a standard path from screening to the loop. The initial technical screen covered SQL and product sense. The questions were very much about connecting data work to business decisions. A couple of weeks later, I moved into the full loop. That loop had four rounds: analytical execution, analytical reasoning, technical skills, and…
Interview experiences · Meta
Meta Data Scientist interview: timed SQL cases and A/B experiment design
After a recruiter and screening step, I faced a fast, high-pressure set of SQL and case tasks. The Python and SQL round covered SQL mechanics and quick reasoning, including common data structures, CASE statements, and window functions. The pace stood out because the window closed as soon as it was time for the case study, so accuracy and efficiency both mattered. The case work was more demanding…
Interview experiences · Meta
Meta Data Scientist Onsite Interview Experience — AR, AE, SQL, and BQ Rounds
I interviewed for a Meta DSA onsite a while back and got the offer, so I want to write this down while I still remember it. My takeaway from the interview is that the real thing differs from interview reports in the details, so when you prepare you still need to keep your thinking flexible. Grasp the big picture, but don't just memorize answers. The interviewer wants a fairly quick response — bas…
Interview experiences · Meta
Meta E5 Software Engineer Interview Experience — Phone Screen Plus a Five-Round VO
I interviewed at Meta at the end of last year. Reading other people's interview reports on this forum helped me a lot, so I'm sharing mine to give back. Phone screen: the first part was the usual behavioral questions, and the second part was two LeetCode problems tagged Easy on Meta's list. VO (virtual onsite): 2 rounds of coding, 2 rounds of system design, and 1 round of BQ. The coding and syste…
Interview experiences · Meta
Meta Intern Software Engineer Interview Experience — OA, Tech Screen, and Two Team-Match Calls for an ML PhD Intern Offer
I finally landed the 26 summer offer that had been hanging over me. The role is SDE, ML PhD intern. Timeline: Oct 14: HR reached out Oct 24: OA + Tech Screening Nov 2: Two Team Match interviews Nov 10: Moved into the hiring process Nov 26: Offer The OA was basically the same questions people have already shared here, randomly pulled from the question bank — nothing harder than a Hard. Technical I…
Interview experiences · Meta Logistics
Meta Logistics Software Engineer interview: screen, loop, and system design
After the recruiter conversation, I had a technical screen with two coding questions. The next stage was an onsite-style loop with a behavioral discussion, two more coding questions, and system design. The recruiter was accommodating when scheduling was difficult. The coding prompts were LeetCode-like, with follow-ups that required me to explain and revise my approach. System design was about tra…
Interview experiences · Meta
Meta Machine Learning Engineer Interview Experience — A Robot Room Cleaner API Variant
Meta recruiters often say they won't ask hard questions, but there are still interviewers who ask hard problems or hard variants. Robot Room Cleaner API variant. Recording the core approach and the easy-to-miss details here for anyone who needs it. Problem summary The map is unknown, boundaries are unknown You can only interact with the environment through the robot API: move() turnLeft() / turnR…
Interview experiences · Meta
Meta Machine Learning Engineer Interview Experience — GenAI Reorg Chaos Mid-Loop
The whole interview experience was pretty bizarre, moving at the same pace as Zuckerberg's MSL reorg. At the start, it was the GenAI department interviewing me, matched to one specific team. Then they just couldn't get an interview scheduled — it dragged on for over a month. By the time the interview finally got scheduled, GenAI had already been carved out to Alex Wang, so this was one of the mos…
Interview experiences · Meta
Meta Machine Learning Engineer Interview Experience — Onsite Loop With ML System Design, BQ, and an AI-Enabled Coding Round
ML system design: One question was a common one — nearby place recommendation for mobile users who might be on the move. The other one I hadn't seen before — notification ranking. These notifications come from various products, like new product announcements, friends' new updates, and ads served by advertisers, and so on. BQ: Right off the bat they had me talk about my most proud project. Then th…
Interview experiences · Meta
Meta Machine Learning Engineer interview: paperwork after technical rounds
The technical rounds were not the main issue for me. A friendly, detailed recruiter screen covered the role and its expectations, then I moved into familiar LeetCode-style coding interviews with screen sharing. The coding itself did not feel unfair. I handled the problems and kept the normal pace while explaining my approach. Even so, I did not get an offer, and the reason I heard was paperwork r…
Interview experiences · Meta
Meta Machine Learning Engineer interview with a conversational-assistant design and declined offer
The process dragged on longer than I expected. It felt drawn out from the early weeks onward. I went through screenings on core ML knowledge, including attention and its variants, before later stages shifted into more high-pressure technical work. Onsite day was intense and tightly structured. In the system-design round, I had to build a conversational assistant and include safety measures. That…
Interview experiences · Meta
Meta New Grad Software Engineer Interview Experience — A Proctored OA Where 35 of 40 Questions Were About AI
VO on CodeSignal, camera on, screen shared. I had AI clean this up a bit — why has the polishing gotten so hard to use lately... it's not that it was hard, it's that the questions were long, with video explanations, so it took time just to understand them. New grad. HR reached out directly, and they want this filled very urgently — I need to get pushed to the final round within two weeks, and thi…
Interview experiences · Meta
Meta New Grad Software Engineer Interview Experience — Three Coding Rounds, One BQ, and an Offer
I am sharing my experience interviewing for Meta's 2025 new graduate role last year. Interview experience The interviews did not feel easy. Other people's Meta loops seemed to get two medium tagged problems and generous grading, but every one of my rounds felt difficult. The first round tested a disconnected graph. In the second round, I had 35 minutes to explain and write one hard and two medium…
Interview experiences · Meta Platforms
Meta Platforms Software Engineer interview: coding and system-design loop
After the recruiter call, I had a technical screen with two coding questions, then an onsite-style loop with behavioral, two more coding questions, and system design. It was structured to test both range and depth under time pressure. The coding was LeetCode-style. I needed to explain the approach, write clean code, and handle follow-ups and optimization. The interviewers were not hostile, and so…
Interview experiences · Meta Platforms
Meta Platforms Software Engineer interview: screens, loop interviews, and leadership expectations
I started with two screening conversations and then entered a set of loop interviews that matched the company's familiar style. The technical work centered on LeetCode-style problems, and the system design could go deep. I was surprised by how much the interviewers varied, even with a similar format. Some offered hints, while others expected me to keep going independently with very little guidanc…
Interview experiences · Meta
Meta Product Designer interview: peer rounds followed by a bench wait
I went through three peer interview rounds with technical and behavioral parts. The format matched what I had seen for this type of role, and the technical questions lined up with the resources I had found beforehand. After those rounds, I expected a decision to move forward. Instead, I was told to wait while they decided which team or role might fit me. I understood it as something like being he…
Interview experiences · Meta
Meta Product Manager interview
After the recruiter stage, I had two timed, structured parts: product sense and product analytics. Product sense required a clear framework, while analytics tested how I interpreted and used data. The interviews resembled common mock formats, where I had to walk through an approach rather than have a free-form discussion. I used the framework I had prepared, but the analytics bar did not match wh…