Daily active users dropped 15% this week. How do you investigate?

Structure it: first check if it's a tracking bug, then segment by platform, region, user type and acquisition channel to isolate where the drop is. Form hypotheses, test them with data, and summarise the root cause with a recommendation.

How would you measure the success of a new feature launch?

Define a north-star metric for the feature (e.g. adoption rate, task completion), plus guardrail metrics (retention, errors) so you don't improve one number by hurting another. Mention setting a baseline before launch.

Explain A/B testing to me. When would you not run one?

Split users randomly into control and variant, measure one metric, and check statistical significance before deciding. Don't test when traffic is too low, the change is a clear bug fix, or the risk of the variant is too high.

Write SQL to find the percentage of users who return 7 days after signing up.

Talk through it: join a signups table to an activity table on user_id where activity date = signup date + 7, then divide returning users by total signups. Mention grouping by signup cohort week — that's cohort analysis.

How would you prioritise between two features the team wants to build?

Use a simple framework like RICE (Reach, Impact, Confidence, Effort) or value vs effort. Estimate each feature's impact on a key metric, check the engineering cost, and recommend the higher ratio — with data, not opinion.

What's the difference between retention and churn?

Retention is the share of users still active after a period; churn is the share who left — they're complements. Explain why retention matters more than downloads for a healthy product.

A feature has high usage but users complain about it. What do you do?

Reconcile the two signals: high usage may mean it's necessary but painful. Look at session recordings or support tickets to find the friction, then propose a fix and measure satisfaction or task time after.

Which product metrics have you tracked in a project or internship?

Use real experience — even a college app or dashboard project counts. Name the metric (signups, completion rate, bounce rate), the tool (SQL, Excel, Mixpanel, GA), and one decision the data drove.

Fresher interview prep

Product Analyst interview questions for freshers.

Product analyst interviews test whether you can define the right metrics, reason through A/B tests, write SQL for cohort analysis and help prioritise features with data.

1. Daily active users dropped 15% this week. How do you investigate?
How to answer: Structure it: first check if it's a tracking bug, then segment by platform, region, user type and acquisition channel to isolate where the drop is. Form hypotheses, test them with data, and summarise the root cause with a recommendation.
2. How would you measure the success of a new feature launch?
How to answer: Define a north-star metric for the feature (e.g. adoption rate, task completion), plus guardrail metrics (retention, errors) so you don't improve one number by hurting another. Mention setting a baseline before launch.
3. Explain A/B testing to me. When would you not run one?
How to answer: Split users randomly into control and variant, measure one metric, and check statistical significance before deciding. Don't test when traffic is too low, the change is a clear bug fix, or the risk of the variant is too high.
4. Write SQL to find the percentage of users who return 7 days after signing up.
How to answer: Talk through it: join a signups table to an activity table on user_id where activity date = signup date + 7, then divide returning users by total signups. Mention grouping by signup cohort week — that's cohort analysis.
5. How would you prioritise between two features the team wants to build?
How to answer: Use a simple framework like RICE (Reach, Impact, Confidence, Effort) or value vs effort. Estimate each feature's impact on a key metric, check the engineering cost, and recommend the higher ratio — with data, not opinion.
6. What's the difference between retention and churn?
How to answer: Retention is the share of users still active after a period; churn is the share who left — they're complements. Explain why retention matters more than downloads for a healthy product.
7. A feature has high usage but users complain about it. What do you do?
How to answer: Reconcile the two signals: high usage may mean it's necessary but painful. Look at session recordings or support tickets to find the friction, then propose a fix and measure satisfaction or task time after.
8. Which product metrics have you tracked in a project or internship?
How to answer: Use real experience — even a college app or dashboard project counts. Name the metric (signups, completion rate, bounce rate), the tool (SQL, Excel, Mixpanel, GA), and one decision the data drove.

Practise these exact questions in a mock interview

Reading tips is step one. RoundLeap builds questions like these from your own resume — 30 from the resume alone, 40 with a job description or job title — then runs an AI mock interview round with real-time feedback and sample answers, so you rehearse out loud before the real thing.

Generate my interview questions Optimise my resume for ATS

No sign in or credit card required to see results.

Product Analyst interview questions for freshers.

1. Daily active users dropped 15% this week. How do you investigate?

2. How would you measure the success of a new feature launch?

3. Explain A/B testing to me. When would you not run one?

4. Write SQL to find the percentage of users who return 7 days after signing up.

5. How would you prioritise between two features the team wants to build?

6. What's the difference between retention and churn?

7. A feature has high usage but users complain about it. What do you do?

8. Which product metrics have you tracked in a project or internship?

Practise these exact questions in a mock interview