Product Growth Analyst (L4/L5) Interview Experience

The Meta Product Growth Analyst loop started with a recruiter screen, then a 45-minute case study plus SQL screen, and then a final loop with two product improvement rounds, one SQL round, one execution round, and one problem-solving round. The whole process is very product-growth heavy, which means they expected me to think like a PM who can also talk metrics, experiments, and data. The first screen was more guided, but the final product improvement rounds were very open-ended. I think this is where most people struggle: they jump to solutions without defining the metric, the funnel, or the user segments. SQL mattered, but the bar was clearly lower than for a data scientist. I ended up joining, and my biggest takeaway was that the real signal came from whether I could stay structured, generate a lot of ideas fast, and still prioritize, as I would actually ship something in a big company.

The Meta Product Growth Analyst loop started with a recruiter screen, then a 45-minute case study plus SQL screen, and then a final loop with two product improvement rounds, one SQL round, one execution round, and one problem-solving round. The whole process is very product-growth heavy, which means they expected me to think like a PM who can also talk metrics, experiments, and data. The first screen was more guided, but the final product improvement rounds were very open-ended. I think this is where most people struggle: they jump to solutions without defining the metric, the funnel, or the user segments. SQL mattered, but the bar was clearly lower than for a data scientist. I ended up joining, and my biggest takeaway was that the real signal came from whether I could stay structured, generate a lot of ideas fast, and still prioritize, as I would actually ship something in a big company.