📊 Product Management

Design and Implement an Upstream Kanban Process

Tests your understanding of managing demand vs. capability. A great answer defines Upstream Kanban as a pre-commitment filter, outlines board stages and policies, and explains how vetting work improves downstream predictability.

Diagnosing a Widening CFD 'Testing' Band

Tests your ability to interpret a CFD and propose data-driven experiments. A widening 'Testing' band means work enters faster than it leaves. Diagnose with experiments (e.g., tracking test failures, environment downtime) before proposing solutions.

How would you implement Classes of Service in Kanban?

This tests your understanding of risk management and differentiated service delivery. A good answer defines the 4 classes (Expedite, Fixed Date, Standard, Intangible), explains their different pull policies, and gives a risk-based example.

Explain Lead Time vs. Cycle Time on a Kanban board

This tests your grasp of core Kanban flow metrics. Define Lead Time (customer request to delivery) and Cycle Time (work start to finish). Measure Cycle Time from the first 'In Progress' column to 'Done'. Red flag: defining terms without explaining their value.

What columns would you set up on a new Kanban board?

Tests your grasp of workflow visualization, not just Agile terms. A good answer starts with To Do/In Progress/Done, then adds columns like Code Review to mirror the real process, and crucially, mentions setting WIP limits to manage flow and identify…

How do you strategically manage tech debt during product discovery?

This tests your strategic view of tech debt. A great answer defines intentional vs. unintentional debt, outlines a framework for tracking and repayment (like a debt backlog), and explains when it's a valid tool for MVPs.

Quantify and communicate a feature's cost/benefit trade-off

Tests your ability to influence product decisions with data. Quantify engineering cost (time, complexity, risk), then propose cheaper experiments like an MVP or fake door test to validate the hypothesis first.

How would you measure the success and impact of a new feature?

This tests your ability to connect engineering work to business value. A strong answer defines success metrics upfront, instruments code for quantitative data like adoption rates, and gathers qualitative feedback.

How do you adapt when user feedback invalidates your current sprint?

This tests your ability to connect process to technical strategy under pressure. A great answer involves immediately notifying the Product Owner, quantifying the impact, and proposing technical pivots like feature flagging.

intermediate3 min read

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.

How would you A/B test a redesigned dashboard?

Tests translating a vague goal ('more engagement') into a concrete engineering plan. A good answer defines key metrics first, then outlines user bucketing, instrumentation, and statistical analysis.

Describe your role in user story refinement.

This tests your understanding of refinement as a collaborative de-risking process. A great answer details your role in clarifying requirements, identifying technical risks, breaking down work, and providing estimates. A red flag is passively receiving tasks.

What do you need in a user story beyond technical requirements?

This tests your product sense. A great answer asks for the user persona, the 'why' behind the request, and measurable success metrics. A red flag is focusing only on technical implementation details without understanding the core user problem.

When to formalize a cross-cutting concern?

Tests your judgment on architectural trade-offs. A good answer uses the "Rule of Three," weighs volatility and complexity to decide, and avoids dogmatic DRY. A red flag is immediately abstracting without considering the high cost of a shared solution.

How do you fix an inverted test pyramid?

This tests your ability to create a pragmatic, multi-sprint plan to improve test suite health. A good answer involves analyzing tests, getting buy-in, then incrementally adding unit/integration tests while refactoring old E2E tests.

Trunk-Based Development vs. GitFlow for High-Frequency Releases

This tests your grasp of modern release strategy. Explain how TBD enables frequent merges to main, while feature toggles decouple deployment from release for safety. Contrast this with GitFlow's versioned release model.

What is the Strangler Fig pattern?

Tests your understanding of gradual legacy system modernization. A good answer defines the pattern (new system grows around old), outlines the steps (identify seams, build, redirect traffic), and links it to Agile's incremental value delivery.

How would you introduce TDD to a team?

Tests your ability to drive change pragmatically. A great answer outlines a gradual adoption: start with a pilot, gather data on bug rates and velocity, and scale based on demonstrated value. A red flag is demanding immediate, universal adoption.

Describe a CI/CD pipeline for a containerized web app

This tests your grasp of automated quality control in software delivery. A strong answer details the CI, build, staging, and production stages, emphasizing quality gates like security scans and E2E tests.