Easy interview questions in Product Management, page 5
When is a pie or donut chart appropriate?
Tests judgment of part-to-whole encoding. Answer: use for few categories with clear dominance, cite a share scenario like device traffic, and name angle-comparison difficulty and 3D distortion as pitfalls.
Daily Scrum ticket updates: what primary purpose is missing?
This tests whether you know the Daily Scrum inspects Sprint Goal progress and adapts the plan rather than reporting status. A strong answer identifies the missing purpose as team inspection and adaptation against the Sprint Goal.
When is a pie chart an appropriate visualization?
Tests your grasp of data viz principles for part-to-whole data. A good answer defines this use case (e.g., market share), then lists pitfalls like too many slices or comparing multiple pies. A red flag is defending pie charts for complex data.
What is the primary purpose of the Daily Scrum?
This tests your understanding of Scrum events as tools for inspection and adaptation, not status reports. A great answer states the purpose is to inspect progress toward the Sprint Goal and plan the next 24 hours.
When is a pie chart an appropriate choice for visualization?
Tests data viz principles for part-to-whole data. A good answer defines this use case, gives a clear example (market share), and lists pitfalls like too many slices or similar values. A red flag is defending them for complex data or time-series analysis.
What's missing from a ticket-focused Daily Scrum?
This tests if you know the Daily Scrum is for Developers to inspect progress toward the Sprint Goal, not a status report. A great answer states this purpose, explains how it enables adapting the next day's plan, and focuses on the team.
How would you technically deconstruct a competitor's magical photo filters?
Tests systematic deconstruction of competitor effects via observation. Strong answers cover black-box testing, signal artifacts, pipeline clues, and latency constraints. Red flag: proposing "just use ML" before defining what makes output magical.
Compare five companies' market share: bar or line chart?
This tests categorical vs. temporal encoding. Pick a bar chart because companies are discrete categories, not a time series; line charts falsely imply sequence or trend. Calling a line chart acceptable is a red flag.
Explain the difference between code complete and Done. What artifact defines this?
Tests whether you know Done means a usable Increment, not just written code. Strong answer: code complete is a dev milestone; Done means the Increment meets quality standards. Red flag: saying testing happens after Done or that Done is optional.
Bar Chart vs. Line Chart for Market Share Comparison?
This tests your grasp of visualization fundamentals for categorical vs. time-series data. A bar chart is correct for comparing discrete categories (companies) at one point in time. A line chart wrongly implies a trend. Red flag: justifying a line chart.
Code Complete vs. Done: What's the Difference?
Tests your understanding of value delivery vs. task completion. A great answer defines 'code complete' as a developer milestone and 'Done' as a team-agreed state of shippable value, governed by the Definition of Done.
Bar Chart vs. Line Chart for Market Share Comparison?
Tests basic chart selection: comparing static categories vs. showing trends. A bar chart is correct for comparing discrete companies at one point in time. A line chart wrongly implies a time-series relationship. Red flag: choosing a line or pie chart.
Difference Between 'Code Complete' and 'Done'?
Tests if you grasp value delivery vs. task completion. A great answer defines 'code complete' as a dev step and 'Done' as a team-agreed state of shippable value, governed by the Definition of Done. A red flag is equating 'Done' with just 'QA passed'.
How do you set up a button color A/B test?
Tests whether you can define a valid experiment, not just a color change. A strong answer covers hypothesis, randomization, primary metric, sample size, and significance threshold.
What is a p-value in A/B tests and what does threshold mean?
P-value is the chance of this or more extreme result if the null is true; the 5% threshold is the accepted false-positive rate.
What user segments do you check first after a 10% DAU drop?
Validate by time, platform, and geography; then slice by new vs returning, channel, and feature usage to isolate the bleeding cohort.
What is the Sprint Retrospective output and what happens next?
Output is a concrete improvement plan enacted in the next Sprint, not parked.
DAU dropped 10%. How do you investigate?
Tests structured problem diagnosis. First, verify the data isn't corrupt. Then, segment the drop by user type (new vs. returning), platform (iOS/Android/Web), and geography to isolate the 'what' before hypothesizing the 'why'.
Sprint Retrospective: What's the output and what happens next?
This tests if you see Scrum as an action-oriented framework. A good answer identifies concrete improvement items as the output and explains that the most impactful one is added to the next Sprint Backlog as a formal work item.
DAU dropped 10%. What user segments do you investigate first?
Tests your systematic problem-solving. First, clarify the metric and timeline. Then, segment by platform, geography, and user tenure (new vs. returning). A red flag is jumping to external causes before ruling out internal issues like a bad deployment.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles