Product Management Topics
Product leadership, vision articulation, roadmap development, and feature prioritization. Focuses on product strategy and business alignment.
Product Documentation (PRD, PR/FAQ)
Writing the artifacts that align teams and drive decisions: PRDs, one-pagers, and the PR/FAQ (working-backwards) format. Covers document structure, clarity, and using written narrative to sharpen thinking and secure buy-in. Assesses written product communication and documentation strategy.
Product Sense and Design
Reasoning about what to build and why, for a given user and business context: reading a vague brief, generating and evaluating candidate feature or product concepts, and defending the chosen concept with structured logic (user needs, business impact, feasibility). Typical prompts are open-ended 'design a product for X' or 'improve product Y' briefs, scoping a Minimum Viable Product (what ships first and why), Jobs-to-be-Done style problem framing, picking a small set of metrics to judge a proposed concept's health, and making a single interaction-shape judgment call within the chosen concept (for example, opt-in vs. default-on, or exposing a power feature vs. keeping it hidden). Also covers anticipating what could go wrong with a proposed concept, such as adoption failure or harm to an underserved subgroup, before it ships. Assesses taste, creativity, and the ability to turn an ambiguous brief into a coherent, defensible product proposal. Out of scope: the multi-phase design process itself (ideation through validation, the double diamond), platform or technical-roadmap prioritization mechanics (RICE, ICE, MoSCoW, Cost of Delay scoring drills), system or infrastructure architecture, and narrating the candidate's own past work (STAR-style storytelling).
Product Roadmapping
Building, sequencing, and communicating a roadmap that turns strategy into a phased plan. Covers cadence, timeline and budget framing, adaptive replanning as conditions change, and keeping stakeholders aligned on what ships when. Emphasizes the mechanics of translating priorities into a defensible delivery sequence.
Business Acumen and Strategy Alignment
Connecting product decisions to business outcomes, domain economics, and company strategy. Covers business-driven product reasoning, domain expertise, and aligning product bets with revenue, cost, and strategic goals. Assesses whether a candidate thinks like an owner of the business, not just the product.
Execution and Delivery Discipline
Driving products from plan to shipped outcome with accountability and predictability. Covers delivery orientation, managing constraints and risk, unblocking teams, and owning results end to end. Assesses whether a candidate reliably converts strategy into shipped, measurable impact.
Requirements Gathering and Scoping
Eliciting, analyzing, and translating stakeholder and user needs into clear, scoped requirements and specifications. Covers cross-functional discovery, distinguishing needs from requests, and writing specs engineering can build against. Assesses the ability to bridge business intent and buildable definition.
Product-Market Fit
Understanding, validating, and achieving product-market fit, and reading the signals that indicate a product is (or is not) resonating. Covers customer validation, growth readiness, and the pivots that fit requires. Assesses judgment about when a product is ready to scale versus needs rework.
Platform and Ecosystem Strategy
Strategy for platforms, developer ecosystems, and vertical expansion where value comes from integrations and third-party participants. Covers developer experience and adoption, API-as-product thinking, and sequencing platform versus application investment. Distinct from Marketplace Dynamics in focusing on developer/partner ecosystems rather than buyer-seller matching.
Product and Engineering Collaboration
Partnering with engineering on feasibility, technical trade-offs, and the balance between feature velocity and technical investment. Covers negotiating scope against constraints, managing tech-debt versus new work, and building shared ownership across product and engineering. Assesses cross-discipline judgment on how the sausage gets built.