Product
60 bites tagged Product — interview questions with model answers, and 60-second explainers.
Error budget exhausted early: what now?
Invoke the error budget policy, shift focus from features to reliability, prioritize stability work, analyze what burned the budget. whether you use the error budget as a decision tool, not punishment.
Pushing back on a costly, low-value feature
Estimate cost in engineer-weeks, size the expected value, frame it as cost-per-unit-of-value, then propose a cheap experiment to test the hypothesis first. whether you can challenge scope with evidence, not opinion.
How would you instrument an application to calculate Customer Lifetime Value?
Tests whether you tie revenue and cost events to persistent identity and model cohort retention. Outline: track purchases, CAC, and churn with persistent IDs; project value via retention curves.
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.
Explain cohort analysis and write a retention query
Tests your grasp of user behavior metrics. First, define a cohort (e.g., May signups). Then, explain why it's better than aggregate retention. Finally, outline a query grouping users by signup week and checking for activity. A red flag is a flawed query.
MVP vs. Throwaway Prototype: Technical Differences
This tests your understanding of Minimum Viable Architecture (MVA). Differentiate by intent: a prototype is a throwaway concept test, while an MVP is a sustainable first version built on an MVA. A red flag is describing a sacrificial architecture for an MVP.
What are the components of a well-written user story?
This tests your understanding of user stories as conversation starters, not specs. A good answer covers the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. A red flag is focusing only on the "As a..."
Calculate Sample Size for a 2% A/B Test Lift
This tests if you connect statistical inputs to business goals. A good answer defines baseline rate, minimum detectable effect (MDE), and power, then explains MDE as a cost/benefit trade-off.
How would you build a SQL query for a conversion funnel?
Tests your ability to translate a business need into a technical SQL solution. A good answer uses CTEs or LEFT JOINs to model sequential steps, counts users at each stage, and discusses attribution.
What does a p-value of 0.03 mean in an A/B test?
Tests your practical statistical literacy. A good answer defines the p-value (3% chance of this result if the null is true), compares it to alpha (0.03 < 0.05) to reject the null, and decides to ship.
How would you design a product management dashboard?
Tests your ability to structure data into a decision-making narrative. A good answer moves from a high-level summary (DAU) to trends (retention) and then actionable details (feature adoption). A red flag is simply listing charts without a narrative connection.
Evidence-Based Management: Metrics Over Gut Feel
EBM replaces 'I think' with 'I know because the data shows...' It's about making decisions using evidence, not just intuition. Use it to prioritize features with user data or optimize processes by measuring cycle time. The footgun is metric fixation.
How do you convince a PO to prioritize technical debt?
Tests your ability to influence without authority by translating technical issues into business impact. A great answer quantifies the cost of inaction (e.g., slowed velocity) and proposes concrete Scrum strategies like allocating 20% capacity.
How can developers support the Product Owner in backlog refinement?
Tests your proactivity and partnership beyond just executing tasks. A great answer covers proactive technical analysis, suggesting ways to split stories for incremental value, and helping the PO quantify impact.
Multivariate Testing: Find Which UI Changes Interact
Multivariate testing finds the best *combination* of UI changes, not just which single design wins. Use it to see how a new headline interacts with a new button on a high-traffic page. The footgun: it requires far more traffic than A/B testing to get a.
CSAT: Measuring If You Met Customer Expectations
CSAT measures if your product met a customer's expectations for a specific interaction. It's used to evaluate experiences like a support call or purchase, giving a direct pulse check on service quality.
Research Hypothesis: A Testable Bet on Reality
A research hypothesis is a testable bet about user behavior, not just a guess. It frames A/B tests by turning an observation into a statement you can prove or disprove. The footgun is confusing it with a theory; a hypothesis is a starting point, not.
UX Research: Building for Real People, Not Assumptions
UX Research is about watching what people *do*, not just what they *say*, to build products that solve their actual problems. It's used to design everything from websites to medical devices, guiding development with real user feedback.
Working Backwards: Start with the Press Release
Start product development by writing the press release for its launch. This forces you to define the customer benefit first, ensuring a new idea is customer-obsessed before you build. The footgun is starting with tech capabilities, not customer needs.
Open vs. Closed Platforms: Walled Garden or Public Park?
An open platform is a public park, inviting others to build on it; a closed one is a walled garden with total control. This choice defines growth: via a third-party ecosystem (Android) or tight integration (Apple).
Two-Sided Markets: Playing Matchmaker for Value
A two-sided market plays matchmaker, connecting two distinct groups like buyers and sellers. It creates value by enabling their interaction, growing stronger as more users from each side join.
ICE Scoring: Prioritize Features with a Quick Gut Check
ICE scoring is a gut-check for prioritizing features by multiplying Impact, Confidence, and Ease. It helps teams rapidly sort experiments or backlog items. The main footgun is its bias towards easy wins, potentially ignoring high-effort strategic projects.
The 80/20 Rule: Find the Vital Few
The 80/20 rule states that most outcomes (80%) come from a few causes (20%). It's used to find high-impact work, like fixing the few bugs causing most crashes. The footgun is treating 80/20 as a precise law instead of a general heuristic.
Roadmap Capacity Planning: Ideal vs. Reality
Capacity planning isn't about your team's ideal output (design capacity), but their actual output (effective capacity) after accounting for meetings, bugs, and on-call. Use it to build realistic roadmaps.
Get Product bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.