Product Growth Analyst (L4/L5) Interview Experience

What have you been doing, and can you walk me through your background?

I kept this high level and focused on the growth side of my work, how I think about user behavior, metrics, and experimentation, and why I fit a role that sits between product and data science.

I would start by defining the user journey and the metric before touching solutions. I would check whether group membership is down, whether fewer posts are being created, whether viewers are seeing posts but not engaging, and whether the drop is concentrated in certain post types or user cohorts. I would segment hard, like text vs photo vs video posts, and whether people are viewing, liking, commenting, or just ignoring. The whole point is to show multiple hypotheses instead of jumping straight to ideas.

What are you going to do about it? How are you going to increase it?

I would first pick a very clear metric, like commenters over viewers or commenters over people who already engaged, and explain why that cohort is the low-hanging fruit and will get statistically significant results faster. Then I would prioritize ideas for the people already in the funnel instead of saying something vague like 'get more people into groups.' I would segment which post formats are getting ignored and then propose things like GIFs, automated responses, or other prompts that actually make commenting easier. They really care that I prioritize one path and explain why it is executable.

Can you pull the percentage of users posting Reels within the United States?

I would expect something simple here, basically a filter and join kind of question, not some rank-heavy SQL. The bar for product growth analyst SQL felt more about whether I can get the right answer quickly than whether I can write the fanciest query.

We want more people to click the Boost button on business pages. How will you do it?

I would first clarify whether the bottleneck is top of funnel, like not enough business pages, or mid funnel, where existing business pages see the button but do not click it. Then I would define the user journey, pick the metric, and spend the rest of the round on creative ideas and prioritization. The key is not to wander. I would get to metric and data in the first 5 to 10 minutes, then spend most of my time on the idea set and why one idea is more executable than another.

Can you pull the count of users in the US who use Instagram and Threads both?

I would solve the SQL quickly with straightforward joins and filters, then switch into diagnosis mode. If the metric is going low, I would ask whether the numerator is dropping or the denominator is changing, then segment by user type, platform, and other obvious cuts to isolate where the decline is coming from.

I approached this by showing how I prioritize ideas based on impact, feasibility, and timing, especially whether something can actually ship in time for the quarter. I would also speak to how I handle pushback from partners and how I narrow choices when there are legal, marketing, or engineering blockers.

You have bandwidth for only one thing. Would you implement automated GIF replies or add a blinking comment button, and why?

I would size both. I would look at expected lift, target cohort size, engineering effort, and whether we already have evidence from a similar A/B test somewhere else. The point is not just to pick something clever. The point is to justify why one option is the better bet right now.

Suppose you have zero marketing dollars. Give me at least six different ideas to increase the number of users on Threads.

I treated this like a creativity round but kept it structured. I would generate a spread of on-platform and off-platform ideas, tie them back to user psychology, and use things like motivation and social proof instead of paid acquisition. They really want volume of ideas here, but they still want them categorized and prioritized, not random.

Instagram daily users are increasing, but Messenger daily users are decreasing. What will you do, and why do you think that is happening?

I would start with sanity checks before making up a product story, like whether this is a dashboard issue, a logging problem, or just a denominator problem. Then I would segment the decline by platform, age, and Messenger type to see where it is actually happening. I would be very specific about the metric because sometimes the numerator is falling and sometimes the denominator is changing. This round is really about asking the right questions in the right order.