Interview questions in Product Management, page 19
Move from flat to usage-based billing
Reliable usage capture, idempotent aggregation into billing periods, and reconciliation with the provider.
Design a programmatic SEO system for 1 million landing pages
Tests data infrastructure thinking, not content generation. Covers one-row-one-page schema, template rendering with edge caching, hierarchical routing, and crawl-budget controls via sitemaps. Red flag: AI bulk writing without structured data or caching.
Average latency up 50ms but p99 flat: diagnose the discrepancy
Tests if you know mean reflects full distribution while p99 is a threshold. Strong answers hypothesize body shift like cache misses or traffic mix changes, and demand histograms and segmentation by endpoint. Red flag: blaming outliers, which would raise p99.
What action ensures a retrospective improvement is implemented?
Tests whether you treat adaptation as a deliverable. Propose making the top improvement a Sprint Backlog item with an owner and definition of done, then inspect it in the next retrospective. Vague agreements or more meetings without ownership are red flags.
Average latency is up 50ms, but p99 is flat. How do you diagnose this?
Tests your grasp of latency metrics. A rising average with flat p99 means the *bulk* of requests (p50-p90) slowed, not the tail. Hypothesize a common bottleneck and segment data by endpoint/user to find it. Red flag: blaming new, slow outliers.
How do you ensure retro action items are implemented?
Tests your ability to make process improvements concrete within Scrum. A great answer suggests adding the top improvement item from the retro directly into the next Sprint Backlog.
Average latency is up, but p99 is flat. Why?
This tests your grasp of latency distributions. Hypothesize that a large group of typical requests slowed, pulling up the average but not crossing the p99 threshold. Segment by endpoint or customer to find the cohort.
How do you ensure retro ideas become action?
This tests your ability to drive change by treating process improvements as formal work. A great answer suggests adding the top retro item to the next Sprint Backlog, making it visible, accountable, and part of the team's commitment.
Design a pricing-page A/B test for $10 vs $15 plans
This tests sticky bucketing and revenue attribution. Hash user IDs to lock variants, persist assignments server-side, and join experiment logs to subscriptions via shared IDs. Red flag: client-side randomization that flickers or breaks billing context.
How would you instrument a 4-step onboarding wizard?
Track Step Started and Step Completed with step_index and flow_variant; tie via distinct_id.
Write SQL to generate a monthly cohort retention table from raw events
Tests window functions and date truncation for cohort analysis. A strong answer finds each user's first month, counts returning users per period, and divides by cohort size. Aggregating all users without isolating acquisition month hides new-user churn.
How would you shift a Sprint Review from demo to working session?
Tests if you see the Sprint Review as empirical inspection and adaptation with stakeholders. Strong answers reframe it around the Sprint Goal and Increment, gather live feedback on the Product Backlog, and adapt ordering together.
How to query a monthly cohort retention table in SQL?
Tests your ability to translate a core business metric into a multi-step SQL query. A good answer finds each user's acquisition month, joins that back to their activity, and pivots the data into a cohort grid. A red flag is calculating aggregate retention.
How do you make a Sprint Review more than a demo?
Tests your understanding of Scrum's purpose beyond ceremony. A great answer outlines how an engineer can partner with the PO, structure the meeting for feedback, and ensure that feedback directly influences the backlog.
Generate a monthly cohort retention table from user events
This tests your ability to translate a business metric into a multi-step SQL query. A great answer defines cohorts by first activity, maps subsequent activity to period indices, counts distinct users, and pivots the result.
Shift a Sprint Review from a Demo to a Working Session
Tests your understanding of Sprint Review's purpose: inspection and adaptation. A great answer shows how an engineer can partner with the PO to frame the session around goals, solicit feedback on the Increment, and collaboratively update the Product Backlog.
How would you detect and mitigate free trial abuse?
Device fingerprinting, rate limits, progressive verification, and behavioral scoring; weigh precision vs false positives and effort.
How do you determine if a user is 'new' for a setup guide?
This tests whether you separate account age from user state for onboarding. Good answers compare created_at (brittle) with a persistent flag (idempotent) and consider milestones. A red flag is using a timestamp as a permanent new proxy without managing reruns.
A/B test shows 5% lift with imbalanced mobile traffic. What next?
This tests sample ratio mismatch and Simpson's paradox. A strong answer says the lift is confounded by platform, demands stratified analysis to isolate the true effect, and checks randomization. A red flag is accepting the 5% lift without questioning skew.
How should the team address poor internal quality when stakeholders are happy?
Tests whether you protect transparency when stakeholders are happy but quality is poor. Answer: At Review, expose the increment's real state—low transparency causes risky decisions; at Retro, inspect why quality degraded and adapt the process.
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