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 and clarity, the press release lead, the external and internal FAQ, hard-question answers, success metrics and acceptance criteria, engineering-ready requirements and constraints, and reviewing or pressure-testing a draft. Also covers using written narrative to sharpen thinking and secure buy-in across functions, and running PR/FAQs as a team practice: intake and review process, versioning, onboarding and co-creation workshops. 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.
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
The working partnership between product and engineering: assessing technical feasibility with engineers, negotiating scope and timelines against technical constraints, and balancing feature delivery against reliability, security and maintenance work when the two functions disagree. Covers making sure engineers understand the why behind work, bringing engineers into discovery, joint planning, estimation and capacity, pushing back on or accepting product requests with engineering risk, holding the line on quality or launch dates when sales or senior leadership press for commitments, making engineering concerns visible and winning funding for technical investment, mediating release, migration and downtime disputes, rebuilding trust and running blameless post-incident conversations after rushed releases or outages, agreeing scope, baselines and what done means up front, and building shared ownership of outcomes. Assesses how a candidate works with the other side of the product-engineering line, not how they rank a backlog or measure debt in the abstract. Prioritization frameworks, technical debt measurement and reduction, and service-level objective mechanics are covered elsewhere.
Trust, Safety and Responsible Product
Designing products that account for abuse, harm, policy trade-offs, and community impact. Covers trust-and-safety considerations, content and policy decisions, and balancing openness against risk. Assesses whether a candidate anticipates misuse and second-order consequences of product choices.
Pricing Strategy and Business Model
Setting and evolving prices and the monetization model they sit in. Covers pricing metrics and structure (per-seat, tiered, usage-based, hybrid, outcome-based), packaging and bundling, freemium versus paid versus ad-supported monetization, and migrating between pricing models, including from perpetual licences to subscription and consumption billing. Includes estimating willingness to pay and price elasticity (van Westendorp, Gabor-Granger, conjoint, observational and causal methods), designing and analysing price tests and reporting their results, discount and deal-desk policy, regional and personalized pricing, and quantifying the revenue, churn, LTV and margin impact of a price or packaging change. Also covers fee design and surge pricing on two-sided marketplaces, responding to competitor price cuts, and rolling out algorithmic pricing safely. Assesses commercial judgment and quantitative rigor on pricing decisions from product, sales, finance and analytics angles. Business-model archetype selection, unit-economics definitions and go-to-market execution are adjacent topics, not the focus.
Technical Product Management
Managing products with deep technical substance: APIs, platforms, data, and infrastructure where the product IS the technology. Covers technical strategy and roadmapping, technical requirements from engineering stakeholders, and structured problem solving for technical products. Assesses the technical depth a TPM needs to earn engineering trust and make sound architectural trade-offs.