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.

11 questions

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.

2 questions

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.

0 questions

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.

0 questions

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.

52 questions

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.

0 questions

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.

22 questions

Growth, Activation and Retention

Driving product-led growth across the user lifecycle: onboarding, activation, engagement, retention, and churn prevention. Covers designing growth features, activation funnels and onboarding experiments, building long-term engagement loops, and improving product adoption, value realization, and lifetime value. Also covers diagnosing why users churn and spotting early warning signs, win-back and re-engagement programs, lifecycle messaging and in-product nudges, referral and viral loops, prioritising growth experiments and roadmaps, and weighing short-term gains against user trust. Assesses systematic thinking about how users discover, adopt, stick with, and keep getting value from a product.

0 questions

Experimentation and Validation

Designing experiments, prototypes, and validation plans to de-risk product decisions before full investment. Covers A/B testing, prototyping strategy, experiment roadmaps and phasing, and reading results honestly. Assesses hypothesis-driven product development and evidence-based decision making.

0 questions

Product Metrics and KPIs

Selecting, defining, and instrumenting the metrics that measure product health and success, including North Star metrics, KPI trees, OKRs, and guardrail metrics. Covers choosing the right metric for a product stage, diagnosing metric movement, and avoiding vanity or gameable measures. Assesses quantitative product judgment and goal-setting rigor.

0 questions

Problem Definition and Framing

Turning an ambiguous prompt into a well-scoped, clearly-stated problem before proposing solutions. Covers structured decomposition, clarifying assumptions, identifying the real user and job-to-be-done, and framing the problem to fit the constraints. Assesses disciplined problem-first thinking under ambiguity.

4 questions

Prioritization and Trade-Off Decisions

Making and defending a ranked decision about what to work on among competing options under conflicting goals, incomplete data, and time pressure. Covers explicit prioritization frameworks (RICE, ICE, MoSCoW, Kano, weighted scoring, impact vs effort, cost of delay, WSJF) and how to make their inputs honest: handling low-confidence estimates, testing whether a ranking is stable, and guarding against gaming, sponsor seniority and recency bias. Also covers backlog and request triage, feature and scope trade-offs, technical debt, reliability, security, compliance and accessibility work versus new features, large-customer and sales-driven requests versus the roadmap, sequencing a limited set of options, urgent interruptions and incidents versus planned work, deciding whether a single initiative on the list should continue or stop, saying no or not now and communicating a deprioritization, documenting a call and later checking whether it was right, and the governance and escalation used to settle prioritization disputes. Assesses whether a candidate can make and stand behind a defensible call rather than treating everything as equally important. Excludes architecture and technology-selection trade-offs, supplier and sourcing decisions, experiment and metric design, portfolio budget and headcount allocation, and delivery trade-offs inside an already committed project.

88 questions

Stakeholder Management and Cross-Functional Alignment

Getting engineering, design, sales, marketing, finance, security, legal, and leadership to agree on and execute a specific product decision when their interests conflict. Covers mediating disagreements between named parties (for example sales versus engineering, design versus engineering, product versus security), settling contested ownership or shared capacity between teams and business units, defining decision rights and escalation paths, sequencing pre-alignment touchpoints for a launch or roadmap change, running a working session that ends in a decision people will stand behind, agreeing what to promise publicly when timelines and lead times collide, and communicating a decision or a changed plan back to each party. Emphasizes the alignment process around a product call rather than the prioritization framework itself.

19 questions

Customer and User Obsession

Reasoning from the customer or end user inward when making decisions in any role: building empathy for users, including buyers who are not the people who use the product; identifying and prioritizing customer pain points and workarounds; collecting and acting on customer feedback, including how representative it is, how it compares with usage data or satisfaction scores, and how it reaches the people who can act; bringing the voice of the customer into roadmap and technical trade-offs; advocating for users against internal or deadline pressure; and balancing customer needs against business goals and engineering constraints, such as a large account's bespoke request, power users versus everyday users, or retiring a feature. Includes stories of changing course because of customers or recovering after letting one down. Assesses whether a candidate starts from the customer's problem rather than from features or technology. Study design and fieldwork, research synthesis, personas and journey maps, analytics and experimentation mechanics, reliability engineering, customer-success operations, market and competitive research methods, and live handling of angry customers are covered elsewhere.

18 questions

Product Management Fundamentals

Foundational product-management knowledge and the shape of the role itself: what a PM does, how product organizations are structured, and core concepts a PM is expected to know. Covers baseline PM literacy, role expectations, and holistic product thinking. Assesses whether a candidate has the fundamentals before deeper strategy or execution probing.

0 questions

Product Strategy, Vision and Innovation

Setting long-term product direction: articulating a compelling product vision and telling it apart from strategy and a slogan, choosing where to play and which customer segment to serve first, and defending positioning and differentiation against incumbents, price leaders, and entrenched network effects. Covers connecting an ambitious future state to concrete near-term choices, fitting a multi-year strategy to company goals, responding strategically to a competitor's move, and deciding when to pivot as market signals or company priorities change. Also covers portfolio-level direction: when to invest in, hold, expand into an adjacency, or wind down a product or legacy offering, and how to combine overlapping products after an acquisition, alongside reasoning about moonshots and emerging-technology bets while balancing ambition with execution. Excludes ranking individual features or initiatives, building and sequencing a roadmap, market-entry and launch plans, pricing, metric and experiment design, and executing a delivery plan.

7 questions

Product Management Topics

Product Documentation (PRD, PR/FAQ)

Product Roadmapping

Product-Market Fit

Platform and Ecosystem Strategy

Product and Engineering Collaboration

Pricing Strategy and Business Model

Technical Product Management

Growth, Activation and Retention

Experimentation and Validation

Product Metrics and KPIs

Problem Definition and Framing

Prioritization and Trade-Off Decisions

Stakeholder Management and Cross-Functional Alignment

Customer and User Obsession

Product Management Fundamentals

Product Strategy, Vision and Innovation