Tell me about a time when you received negative feedback from your manager and how you dealt with it.

"What surprised me most was how much the process emphasized solving several coding questions under pressure. I had an initial recruiter screen, then a 45-minute pre-screen with a senior manager about my past work and impact, and after that a full loop of five interviews. The loop was two coding rounds, one of them classic LeetCode-style and one of them AI coding with data-processing and math-heavy prompts like sparse matrix times vector multiplication and k-nearest neighbor search, plus two design rounds and one behavioral. The design interviews were split between an ML modeling discussion for a computer vision problem and a system design round on something like Google Street View, which I found pretty challenging. I passed the loop, got notified that I made it through, and then moved into offer negotiation."

"The process was pretty standard compared to what I'd read online. My first round had product sense plus analytical/execution, and the second round was the full loop with product sense, analytical/execution, and behavioral. The content itself matched expectations, but what stood out was how dependent the experience was on the interviewer, especially in the second round where I felt one person was biasing me toward a specific path without really saying it outright. I had about 2 to 3 weeks between rounds, and Meta seemed flexible on scheduling, which helped with prep. I didn't make it to team matching. My read is that Meta's PM process is very structured, but your experience can still vary a lot based on the interviewer. It really did feel like the weather where you don't know if you're getting a sunny day or a rainy day, so I wouldn't assume every interviewer will be equally neutral. They also don't give much useful feedback afterward, so a lot of your learning has to come from your own reflection and prep. One thing I did like is that the process didn't feel tied to one urgent req since team matching comes after, so there seemed to be flexibility to push interviews out if I needed more time to prepare."

"I interviewed for a senior full-stack role in Seattle, and the whole process felt way more specialized than most big-company interview loops I’ve been through. By the time I got into the loop, it felt like they'd already assumed I could code, so the real test was whether my background matched the team’s exact domain and whether I aligned with the culture memo. The technical rounds were practical React exercises tied closely to internal tooling, not DS&A problems, and the system design round was surprisingly open-ended and conversational with no architecture diagramming at all. The behavioral side was much heavier than usual, and multiple interviewers repeated the same disagreement or feedback themes to see if I had more than one canned example. Overall, it felt less like a generic company process and more like a team trying to hire someone who had basically already done their job before."