Interview questions in Product Management, page 15
When is it appropriate for engineering to propose a vision change?
Tests your sense of engineering's strategic boundary: co-creating vision without owning it. Strong answers cite a trigger where tech changes business constraints, outline a 2-week spike on the riskiest assumption, and quantify impact.
How would you structure your growth team's experimentation portfolio?
3 asset classes (iterative 30-70%, tech investments, big bets 20-40%), use expected value per week, and evolve the mix.
How do you manage event schema evolution without breaking reports?
Backward-compatible serialization, nullable new fields, raw versus modeled layers, versioned schemas, and consumer alerts.
What is the Sprint Goal and how does it guide planning?
Goal-driven Sprints vs ticket batches. The Sprint Goal is the agreed objective guiding selection of ordered backlog items to build a valuable Increment and enable inspection. Red flag: calling it optional or pulling the top N items without negotiation.
How do you manage schema evolution in an analytics pipeline?
This tests your grasp of data as a contract. A great answer covers schema registries, backward compatibility, and a phased rollout from producer to warehouse. A red flag is only mentioning an ALTER TABLE command, ignoring the entire data pipeline.
What is a Sprint Goal and how does it influence planning?
Tests if you grasp that a Sprint Goal defines a valuable outcome, not just a list of tasks. A good answer explains it's a filter for selecting work, provides flexibility, and creates team coherence. Red flag: equating the goal with 'finishing all the tickets'.
How do you manage an event schema change?
This tests your understanding of data contracts and backward compatibility. A great answer details a phased, backward-compatible rollout (add nullable field), starting with consumers (warehouse) then producers, and mentions using a schema registry for…
Sprint Goal: Purpose and Influence on Sprint Planning
Tests if you understand a Sprint is about a single objective, not just a list of tasks. Define the Sprint Goal as the 'why'—a commitment providing focus and flexibility that guides PBI selection. A red flag is defining the goal as a summary of tickets.
What specific metrics define a 'fast' report export?
Propose user-facing latency percentiles and throughput; split SLI from SLO target; pick realistic targets.
WAU is flat despite positive A/B tests; why and how to diagnose
This tests distinguishing real impact from statistical artifacts. Strong answers cite false positives from low base rates, peeking, novelty, and local-global mismatches. Diagnose with long-term holdouts, audits, and causal bridges.
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.
Build an opportunity-sizing model before building
Locate the affected funnel step, estimate addressable population times a bounded conversion lift times value per user, then sanity-check against a realistic ceiling.
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.
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