THE RUBRIC
The product manager competency framework
Every participant is scored against the same 4 competency families and 16 dimensions, the same way, every time. Each dimension below explains what it actually measures, what strong evidence looks like, what weak evidence looks like, and a real example of the kind of follow-up question the interview asks about it.
Publishing this in full is deliberate. A 30 to 60 minute adaptive interview cannot be gamed by knowing the topics in advance, only by having the evidence to back an answer up.
Strategic Thinking
Product Strategy
Whether your product strategy is specific, tradeoff-driven, and connected to real resource allocation and measurable outcomes, not a vision statement everyone in the room would agree to.
Market & Competitive Judgment
Whether you understand the real market context around your product, not just the internal roadmap: competitors, substitutes, market structure, and the alternatives your customer actually has.
Innovation Behavior
Whether an unconventional idea was actually built, adopted, and tied to a real customer, business, technical, or operational outcome, not creativity for its own sake.
AI-Era Product Leadership
Whether you understand what AI can and cannot reliably do inside a product, including hallucination risk, data quality, human-in-the-loop design, and the governance and trust tradeoffs of actually shipping it.
Execution & Judgment
Prioritization & Judgment
Whether your prioritization decisions hold up under pressure -- weighing customer impact, business impact, technical effort, and executive pressure against each other -- not whether you can describe a scoring template.
Execution & Delivery Discipline
Whether you can move from idea to shipped outcome without avoidable chaos: scope, sequencing, dependencies, risk, and what you actually learned after launch.
Analytics & Data Judgment
Whether you use data to change a real decision, not just to report on one -- choosing the right metric, reading it correctly, and knowing when the data is not enough to decide.
Technical Competency
Practical product-technology judgment, not coding ability: architecture, scalability, technical debt, and build-versus-buy tradeoffs, tied to customer and business outcomes.
Leadership & Influence
Communication & Executive Presence
Whether you can explain a complex tradeoff clearly and concisely to an audience that was not in the room for the details, including at the executive or board level.
Stakeholder Management & Influence
Whether you can turn real disagreement into a committed decision across functions with conflicting incentives, not just get everyone to nod in the same meeting.
People Leadership & Talent Development
Whether you can hire, coach, and manage the performance of product talent, including handling underperformance directly rather than avoiding it.
Product Operating Model Maturity
Whether you can move a team from feature delivery to outcome-based product management: clarifying decision rights, reducing order-taking, and improving discovery and prioritization rhythms.
Commercial & Customer Judgment
Commercial & Business Acumen
Whether you can connect product decisions to revenue, margin, retention, or unit economics, not just engagement or feature delivery.
Customer Centricity
Whether customer insight actually changed a decision and an outcome, not whether you can describe your customers sympathetically.
Ethics & Responsibility
Whether you can identify and manage user harm, dark patterns, privacy risk, and trust tradeoffs while still creating business value, rather than avoiding the tension entirely.
Learning Velocity & Adaptability
Whether you changed your approach because of evidence, feedback, or failure, not whether you say you're a fast learner.
See how this applies to you
Reading the framework is one thing. A structured conversation that tests where you actually stand against it is another.