Best AI Prompts for a VP of Product Interview in 2026 (Copy-Paste Ready)

You are a VP of Product coach who has helped senior PMs and Directors land VP roles at Series B through Series D companies. Help me craft a compelling product vision for an early-stage B2B SaaS company I am interviewing with. The company is a workflow automation platform with $8M ARR, 80 employees, and 200 customers in the SMB and lower mid-market segments. They have not defined a clear product vision beyond "make workflows easier" and the board has flagged this as a gap. Build me a product vision statement and the supporting narrative I would walk through in the interview. Specifically: (1) a 1-sentence product vision that is specific, differentiated, and defensible — not generic; (2) the 3 strategic pillars that the vision rests on and what each one means for the roadmap in the next 12 months; (3) how I would validate or pressure-test this vision with customers and the team in the first 60 days; (4) what I would deprioritize in order to deliver on this vision — what we would stop doing; (5) how I would present this vision to the board at the first quarterly review. Write the full vision narrative as a 3-minute verbal answer with a clear opening line that signals strategic conviction, not just product process.

Act as a VP of Product interview coach and executive storytelling expert. Help me build a rigorous STAR-format answer for the question: "What is your framework for prioritizing features?" I need a response that demonstrates VP-level thinking — not just a list of prioritization frameworks. My STAR story: I was Director of Product at a B2B SaaS company. The engineering team had been building a complex multi-step workflow automation feature for 3 months. Halfway through, I ran a re-prioritization exercise and discovered this feature was in the bottom quartile of customer demand and required 40% of our quarterly engineering capacity. Meanwhile, a lightweight version of a different feature — one we had deprioritized — had been requested by 68% of our top-quartile customers by NRR. I made the call to pause the in-progress feature, ship a scrappy version of the high-demand feature in 3 weeks, and validate before committing to the full build. The scrappy version shipped, achieved 3x the adoption rate of any feature we had shipped in the previous 6 months, and became the most-mentioned improvement in our next customer satisfaction survey. Write this as a polished STAR answer I can deliver in 2.5 minutes. Lead with my prioritization framework, then prove it with the story. Include the specific outcome metrics.

You are a VP of Product and product operations expert. Help me build a structured answer for the interview question: "How do you build a 12-month product roadmap when you inherit a messy backlog?" This question comes up in almost every VP interview and most candidates answer it with process steps instead of demonstrating judgment. Build me an answer that covers: (1) the diagnostic I run in the first 30 days — the specific questions I ask to understand what is in the backlog, why it is there, and what hidden commitments or landmines exist; (2) how I categorize what I find — the 4 buckets I sort every backlog item into and what I do with each bucket; (3) how I engage the team, engineering partner, and stakeholders in the roadmap build without creating a planning process that takes 3 months; (4) the structure of the resulting 12-month roadmap — what quarters 1, 2, 3, and 4 look like in terms of investment allocation across new bets, core improvements, and technical health; (5) how I handle the person who shows up on day 30 and says "you forgot my critical feature." Write as a direct, experienced 3-minute answer that signals I have actually done this before.

Act as a VP of Product coach and executive communication expert. Help me build a clear, confident answer script for the interview question: "How do you balance engineering capacity with business priorities?" This question tests whether you have operational credibility and can manage the relationship between product and engineering without becoming a bottleneck or a pushover. Build me a script that covers: (1) how I think about the allocation of engineering capacity across planned work, unplanned work, and technical investment — and the specific percentages I typically use and why; (2) how I handle the situation where a high-priority business request from sales or the CEO lands mid-sprint and engineering says they cannot absorb it; (3) how I create a shared capacity model with the VP of Engineering so that neither of us is surprised by the other; (4) how I communicate trade-offs to the CEO or board when business priorities exceed available capacity — the specific framing I use; (5) a brief STAR example of a time I navigated a capacity vs. priority conflict and what the outcome was. Write as a 2.5-minute script I can use in a panel with a CEO, CPO, or board member.

You are a VP of Product interview coach and executive onboarding expert. Help me build a structured, specific answer to one of the most common VP of Product interview questions: "What would you do in the first 90 days as VP of Product?" Most candidates answer this with a generic 30-60-90 framework. I want an answer that demonstrates strategic judgment, not just process. Build me a response structured as: Days 1-30 — Listen and diagnose (the specific people I would talk to, the questions I would ask, and what I am trying to understand about the product, the team, the market, and the company's relationship with customers); Days 31-60 — Synthesize and frame (the deliverable I would produce at day 60 — a product strategy memo or opportunity brief — and how I would share it with the team and leadership to build alignment before committing to a direction); Days 61-90 — Align and commit (how I would finalize the roadmap, gain cross-functional buy-in, and set the first set of measurable product goals I will be accountable to). For each phase, include one specific thing I would NOT do in that phase — and why. Write as a 3-minute verbal answer that sounds like an experienced executive, not a management consultant.

You are a VP of Product and customer discovery expert. Help me build a complete, structured script for running a 45-minute customer discovery session to identify ICP pain points that I can describe in a VP of Product interview. The context: I am joining a Series B B2B SaaS company and want to run 15 discovery sessions in my first 30 days with customers across SMB, mid-market, and enterprise segments. Build the session script to include: (1) the opening 5 minutes — how I establish rapport and frame the conversation so customers feel safe sharing real problems, not just product feedback; (2) the core 30 minutes — the 8 to 10 specific questions I use to surface unmet needs, current workarounds, and the emotional intensity of the pain (not just its existence); (3) the closing 10 minutes — how I synthesize back what I heard, identify the 1 to 2 highest-signal moments from the session, and close in a way that makes the customer want to be in the follow-up session; (4) what I do in the 30 minutes after each session — the specific notes I take and how I structure my synthesis across 15 sessions to find patterns, not just anecdotes; (5) the deliverable I produce at the end of the discovery sprint — what it looks like, who it is for, and how I use it to influence the roadmap. Write as a concrete, practitioner-level answer that signals I have run this process, not just studied it.

Act as a VP of Product interview coach and executive storytelling expert. Help me write a strong STAR-format answer for the question: "Tell me about a time when customer discovery revealed a significant blind spot in your product roadmap." My situation: I was Director of Product at a workflow SaaS company. We had a full quarter of engineering committed to building a new dashboard and reporting layer — it was the top-voted feature in our quarterly survey and had been on the roadmap for two years. Three weeks before we were going to kick off the sprint, I ran a series of discovery interviews with 12 customers specifically about how they used data in their workflows. What I discovered: the reporting request was a proxy for a deeper problem — customers did not trust the data in the product because of a sync reliability issue that caused records to go stale. No one had articulated it that way in a survey. I paused the dashboard project, ran an emergency diagnosis with engineering, and confirmed that 40% of customers were affected by the sync issue. We spent the quarter fixing data reliability instead. Within 60 days of shipping the fix, our NPS moved up 14 points and three enterprise deals that had been stalled specifically over data reliability concerns closed. Write this as a polished STAR answer I can deliver in 2.5 minutes, emphasizing: the discovery method, the courage to act on an inconvenient finding, and the measurable outcome.

You are a VP of Product and competitive strategy expert. Help me build a rigorous competitive landscape analysis framework I can walk through in a VP of Product interview when asked: "How do you analyze the competitive landscape and decide where to play and where to win?" Most candidates describe competitive analysis as a feature comparison matrix. I want to demonstrate strategic thinking. Build me a framework that covers: (1) the 3 types of competitive intelligence I gather — direct competitors (same job to be done), indirect competitors (different approach to the same problem), and category substitutes (how customers solve the problem without a product like ours); (2) the 4 strategic questions I answer for each major competitor: where are they winning and why, where are they losing and why, what are they building next (based on job postings, pricing changes, and customer churn patterns), and what is the one thing they cannot do because of their current architecture or business model; (3) how I use competitive intelligence to make "where to play, where to win" decisions — the specific framework I use to identify whitespace vs. defended territory; (4) how often I run this analysis and how I share the findings with product, sales, and the board; (5) a specific example of a competitive insight that directly changed a roadmap decision. Write as a 3 to 4-minute answer that demonstrates genuine strategic fluency, not just analytical process.

Act as a VP of Product and growth strategy expert. Help me build a specific, metrics-based answer to the interview question: "How do you know when you have achieved product-market fit?" This is one of the most overused terms in product and most candidates give a vague answer about retention and customer love. I want a rigorous, specific answer. Build me a response that covers: (1) the 3 quantitative signals I look for that indicate strong PMF in a B2B SaaS context — cover: net revenue retention above 110% from the ICP cohort (not the full customer base), a top-down churn rate below 5% annually from ICP customers, and a 40% or higher response to "how disappointed would you be if this product went away" from active users; (2) the qualitative signals I look for — the 3 behavioral patterns in customers that tell me they have changed the way they work because of the product (not just use it, but depend on it); (3) how I distinguish between PMF in a segment vs. PMF across the market — why this distinction matters for how you allocate product investment; (4) what I do after I believe I have PMF — the 3 things that change in how I run the product org once PMF is established; (5) a brief example of a company or product where I have seen real PMF vs. false PMF signals that looked similar but were not. Write as a 2.5 to 3-minute answer that signals genuine product experience.

You are a VP of Product and discovery facilitation expert. Help me build a complete discovery call script I can use when I am asked to assess a product I know nothing about yet — a scenario that comes up in VP of Product interviews when the interviewer says "pretend you just joined and your first week is customer calls for a product in [category X]." Build the script for a B2B workflow automation product the interviewer has just described to me in 2 sentences. The script should cover: (1) the 3 context-setting questions I ask before diving into discovery — how the customer came to use the product, how long they have been using it, and how they would describe what it does to a new colleague; (2) the 5 core discovery questions that work regardless of what the product does — questions that surface the job to be done, the workflow context, the current frustrations, the workarounds, and the stakes of the problem not being solved; (3) how I probe for emotional intensity — the follow-up questions that distinguish a mild inconvenience from a problem worth solving; (4) how I close the call in a way that surfaces what the customer thinks would be the single highest-value improvement; (5) the 3 patterns across 10 calls that would tell me where the product has strong PMF vs. where it has gaps. Write the script as specific questions I can actually use verbatim, not as a description of discovery best practices.

You are a VP of Product and stakeholder management expert. Help me build a confident, specific answer to one of the most common VP of Product interview questions: "How do you handle the tension between sales bringing in feature requests to close deals and maintaining product integrity?" This question is designed to reveal whether you have spine, judgment, and political sophistication — or whether you capitulate to every sales request and call it customer-centricity. Build me an answer that covers: (1) how I distinguish between a legitimate market signal from sales (the feature reflects a real gap across multiple customers) vs. a one-off request driven by a specific deal (the feature serves one customer and one salesperson's quota); (2) the process I use to evaluate a sales-driven feature request without making sales feel dismissed — the specific questions I ask and how quickly I respond; (3) how I handle the situation where the feature is not the right thing to build but the deal is real and important — the alternative I offer and how I frame it; (4) how I build a relationship with the VP of Sales that creates a shared framework for these conversations before they become conflicts; (5) a STAR example of a time I said no to a sales-driven feature request, how sales reacted, and what the outcome was. Write as a 3-minute answer that signals I have navigated this relationship with both backbone and respect.

Act as a VP of Product interview coach and executive storytelling expert. Help me write a strong STAR-format answer for: "Tell me about a time you resolved a significant conflict between Engineering and Product that was putting a launch at risk." My situation: I was Director of Product at a B2B SaaS company. We had committed to a major enterprise customer that we would ship SSO and advanced permissions by the end of Q3. Six weeks before the deadline, the VP of Engineering came to me and said the permissions system was 3x more complex than initially scoped and the team needed 10 additional weeks. I had a choice: slip the date and risk losing the customer, or find a path that maintained the commitment. I asked for 48 hours. I spent 2 days with the engineering team doing a detailed scope review and discovered that 70% of the complexity was in edge cases that the customer had never asked for. I redesigned the requirements to deliver the 80% that the customer actually needed, presented the revised scope to the VP of Engineering, and got agreement that the simpler version could ship in 4 weeks. I briefed the customer proactively, explained what we were shipping and why it covered their use case, and we launched on the original date. The customer signed the expansion 30 days later. Write this as a polished STAR answer I can deliver in 2.5 minutes. Emphasize: how I diagnosed the real problem, the collaboration approach, and the outcome.

You are a VP of Product and board communication expert. Help me build a complete structure for running a quarterly product review with a board that I can describe in detail in a VP of Product interview. Most VP candidates have a vague answer about "communicating the roadmap." I want a specific, structured approach. Build the quarterly review structure to cover: (1) the pre-meeting preparation — the 3 documents I send to board members 48 hours in advance and what each one contains; (2) the meeting structure — the 5 segments of the quarterly product review with time allocation, the key question each segment is designed to answer, and who presents each section; (3) how I handle board members who want to go deep on execution details (sprint velocity, individual feature status) when I need to keep the conversation at the strategy level; (4) how I present roadmap trade-offs in a way that invites genuine board input rather than rubber-stamp approval — the specific framing I use; (5) the one question I always ask the board at the end that most VPs of Product forget to ask — and why it matters. Write as a concrete, practitioner-level answer that signals I have actually run board reviews, not just prepared for them.

Act as a VP of Product and engineering culture expert. Help me build a practical, specific answer to the interview question: "How do you get engineering teams to actually care about customer problems?" This question is designed to surface whether you have thought carefully about the Product-Engineering relationship or whether you rely on process mandates and hope. Build me a response that covers: (1) the 3 specific things I do in the first 30 days to change how engineers relate to customer problems — not policies or mandates, but direct experiences; (2) how I structure customer exposure for engineers — the specific format (customer interviews engineers attend, support ticket reviews, recorded call libraries) and why format matters; (3) how I connect the work engineers are doing right now to the customer problem it solves — the ritual I use in sprint planning or roadmap reviews to make the connection explicit; (4) how I handle the senior engineer who is genuinely resistant to customer involvement and sees it as a distraction from technical work; (5) a specific story of a time I changed an engineer's relationship with customer problems — and how it changed the product. Write as a 2.5 to 3-minute answer that sounds like someone who has actually moved an engineering culture, not just advocated for one.

You are a VP of Product and organizational influence expert. Help me build a clear, specific answer to the VP of Product interview question: "How do you influence marketing and customer success to align with the product roadmap when you don't have authority over those teams?" This question tests whether you can operate as a genuine cross-functional executive or whether you rely on product authority to get things done. Build me an answer that covers: (1) how I build the marketing partnership specifically — the 2 key rituals I use to keep marketing aligned to the product direction (a monthly product-marketing sync with a specific agenda, and a joint positioning review when major features launch); (2) how I handle the marketing team that is already 6 months ahead in their content calendar and does not want to reprioritize for a product shift; (3) how I build the CS partnership — the 3 things I do to make CS a genuine voice in roadmap decisions rather than a stakeholder I brief after the fact; (4) how I handle a CS team that is making commitments to customers about features that are not on the roadmap; (5) the one thing I do in my first 30 days with marketing and CS leadership that is different from what most incoming VPs of Product do — and why it changes the relationship from the start. Write as a 3-minute answer that signals organizational maturity and genuine cross-functional experience.

You are a VP of Product and product analytics expert. Help me build a comprehensive answer to the interview question: "How do you define the North Star metric for a SaaS product and build a metric tree under it?" Most candidates can name a North Star metric. Few can explain how they chose it, what sits underneath it, and how it drives daily team decisions. Build me an answer that covers: (1) how I define a North Star metric for a B2B SaaS product — the 3 criteria a good North Star must meet (it must reflect customer value delivered, it must be leading not lagging, and it must be something product decisions can actually move); (2) a worked example: for a workflow automation platform with 500 SMB customers, walk through the process of selecting the North Star and explain why I would choose "workflows completed per active account per week" over alternatives like MAU or feature adoption rate; (3) the metric tree below the North Star — the 4 to 6 input metrics that drive it, how they are structured (acquisition, activation, engagement, and retention layers), and which PM or product area owns each one; (4) how I use the metric tree in roadmap prioritization — the specific decision I can make because of the tree that I could not make without it; (5) how I change the North Star when the business model evolves (e.g., moving from usage-based to seat-based pricing). Write as a 3 to 4-minute answer that demonstrates I have built and used metric trees in real product organizations.

Act as a VP of Product interview coach and executive storytelling expert. Help me write a strong STAR-format answer for: "Tell me about a time a key product metric was declining and how you turned it around." My situation: I was Director of Product at a B2B SaaS company. Our 30-day activation rate — the percentage of new customers who completed a core workflow within their first 30 days — had been declining for 2 consecutive quarters, from 68% to 52%. The business was growing in new signups but NRR was starting to slip as early churn increased. I launched a structured diagnosis: I ran 20 customer interviews specifically with customers who had signed up and not activated, reviewed the onboarding funnel data with the engineering team, and shadowed 5 customer onboarding calls with our CS team. The root cause: our onboarding flow assumed customers already understood how to map their workflow to our product structure. Most SMB customers did not have that context and dropped off at the first configuration step. I redesigned the onboarding experience with a 3-step guided workflow builder, reduced the time-to-first-workflow-completion from an average of 4 days to 6 hours, and within 90 days our 30-day activation rate recovered to 71% — above the prior peak. NRR stabilized and improved 8 points in the following quarter. Write this as a polished STAR answer for a 2.5-minute verbal delivery.

You are a VP of Product and product operations expert. Help me build a specific, structured answer to the interview question: "How do you measure success for a new feature launch?" This question reveals whether you have a rigorous product measurement practice or whether you ship features and move on. Build me an answer framework that covers: (1) the pre-launch hypothesis — how I define success before we ship, what the measurable outcome looks like in 30, 60, and 90 days, and how I document it so the team is accountable; (2) the launch metrics I use — the 3 layers of measurement I apply to every feature: leading indicators in the first 7 days (adoption rate, feature discovery, time-to-first-use), validation metrics in 30 days (retention of feature users vs. non-users, support ticket volume change, NPS movement in the affected segment), and business impact metrics in 90 days (ARR contribution, churn reduction, or NRR change in the cohort); (3) how I run the post-launch review — the specific meeting, who attends, and what decisions come out of it; (4) how I handle the feature that is getting used but not moving the metric I expected — the diagnostic process; (5) how I handle the feature that is not getting used at all — the 3 things I check before writing it off. Write as a 2.5 to 3-minute answer that signals disciplined product accountability.

Act as a VP of Product and product analytics strategy expert. Help me build a clear, opinionated answer to the VP of Product interview question: "How would you build a product analytics stack from scratch at a company that currently has no instrumentation?" This is asked at early-stage companies and at companies that have grown faster than their data maturity. Build me an answer that covers: (1) the first 2 weeks — the 3 things I do before touching any tooling: define the 10 core events that matter most based on the product experience and the metrics I care about, align with engineering on an event taxonomy and naming convention, and establish the single source of truth for product data; (2) the tooling layer — the stack I recommend for a Series A or Series B company (event tracking via Segment, product analytics in Mixpanel or Amplitude, data warehouse in BigQuery or Snowflake for deep analysis, and a lightweight BI layer for stakeholder dashboards) — explain the role of each tool in one sentence; (3) the first dashboards I build — the 5 dashboards I stand up in the first 30 days, what each one shows, and who its primary audience is; (4) how I get engineering to instrument properly and maintain instrumentation over time without it being a constant battle; (5) what good product data culture looks like at 12 months — the behavioral changes I want to see in PMs, engineers, and CS when the stack is embedded. Write as a structured, practical answer I can walk through in 3 minutes.

You are a VP of Product interview coach and accountability culture expert. Help me build an honest, specific answer to the VP of Product interview question: "Tell me about a feature you shipped that failed. How did you handle it?" This question tests psychological safety, learning culture, and leadership maturity. The worst answers deflect blame. The best answers demonstrate that you own outcomes, diagnose clearly, and build better systems from failures. Build me a response using this situation: I was Director of Product and we shipped a redesigned onboarding flow that we had validated in user testing with a 15% improvement in completion rate. In production, our 30-day activation rate dropped by 9 points. Investigation revealed: the user test cohort was biased toward tech-savvy users, the redesign removed a help tooltip that less technical users relied on, and we had not tested adequately with our SMB segment. Cover: (1) how I owned the failure publicly — the specific communication I sent to the team and to leadership; (2) the root cause analysis process — how I diagnosed what went wrong and what I discovered; (3) the fix — what we shipped and how quickly; (4) the systemic change — what we changed in our validation process to prevent this class of error; (5) what I would say to a CEO or board who asks "how did this happen?" Write as a direct, mature answer that shows accountability without self-flagellation. No corporate hedging.

You are a compensation expert and executive career advisor specializing in VP of Product placements at venture-backed and growth-stage companies. Help me benchmark VP of Product compensation so I can enter any offer negotiation with accurate market data. Build a comprehensive benchmark covering: (1) base salary ranges by company stage — Seed: $140k–$200k; Series A: $180k–$260k; Series B/C: $220k–$350k; Series D+ and pre-IPO: $280k–$420k; enterprise public company: $250k–$400k + RSUs — for a VP of Product with 8 to 15 years of experience including prior PM leadership at the Director level; (2) equity benchmarks by stage — typical option grant as a percentage of the company at each stage (Seed: 0.3–1.5%, Series A: 0.25–0.8%, Series B: 0.1–0.5%, Series C+: 0.05–0.25%, public company: RSU dollar equivalent) — and what the vesting schedule typically looks like; (3) the other package components I should always negotiate: performance bonus structure, signing bonus norms at each stage, equity refresh cadence, and severance terms; (4) how geography affects these numbers — the Bay Area premium, the rise of location-neutral packages, and how to negotiate a remote premium; (5) the 3 questions I must ask during due diligence to evaluate the real value of an equity grant at a private company — cover liquidation preference stack, last 409A valuation, and option pool size. Format as a reference document I can use in any VP of Product compensation negotiation.

Act as a VP of Product career advisor and executive offer evaluation expert. Help me build a comprehensive framework for evaluating a VP of Product offer that goes beyond the base salary number. I have received an offer from a Series B B2B SaaS company: $290k base, 0.4% options (4-year vest, 1-year cliff), $20k signing bonus, 15% performance bonus tied to company ARR milestones, no board seat. Build me an evaluation framework that covers: (1) how I assess whether the base is competitive for this stage — what market data I check and what range I should be comparing to; (2) how I evaluate the equity grant — the specific questions I ask about the strike price, the last 409A, the option pool, and the liquidation preference stack to understand what 0.4% is actually worth in a realistic exit scenario; (3) how I evaluate the reporting line and organizational structure — the questions I ask about who I report to, what authority I have over roadmap and headcount, and how product decisions are made at this company; (4) how I evaluate the team I am inheriting — the 5 questions I ask in the final rounds to understand what I am walking into; (5) the 3 red flags in a VP of Product offer that would cause me to either negotiate hard or walk away. Write as a structured evaluation guide I can use to assess this specific offer and prepare for the negotiation conversation.

You are a VP of Product career coach and interview preparation expert. Help me build a confident, authentic answer to the interview question: "Why do you want to leave your current role?" as a senior PM or Director targeting a VP of Product position. The worst version of this answer burns bridges or sounds desperate. The best version is forward-looking, specific, and honest without being disloyal. Build me 3 versions of the answer for different situations: (1) I am leaving because I have grown as much as I can in my current company and want to operate at a larger scope — write this in a way that honors my current company while making clear I am ready for the next level; (2) I am leaving because the company has shifted strategy and product is no longer central to how value is created — write this diplomatically without criticizing the leadership team; (3) I am leaving because I was passed over for the VP role and I believe I am ready — write this confidently without sounding bitter or entitled. For each version: write the 90-second answer, identify what the interviewer is trying to learn by asking the question, and flag the one thing candidates most often say that backfires. Write as genuine, natural language — not corporate polish.

Act as a VP of Product interview coach and executive branding expert. Help me write a 60-second "why I am the right VP of Product for this stage" pitch I can use at the start or end of any VP of Product interview. This pitch should answer the implicit question every CEO and board member has: out of everyone we could hire for this role, why is this person the obvious choice right now? Build the pitch for a specific scenario: I am a Director of Product at a Series B company, I have led a team of 5 PMs, managed a $2M product budget, and shipped 3 major product initiatives that collectively contributed $4M in new ARR over the last 2 years. I am interviewing for a VP of Product role at a Series B company preparing for Series C. Structure the pitch as: (1) Opening observation — a specific, researched diagnosis of the company's current product moment (not a compliment, a genuine strategic observation about their opportunity or challenge); (2) Experience bridge — the 2 things in my specific background that are most directly relevant to what this company needs in the next 18 months, framed in terms of what I will deliver, not what I have done; (3) Why here, why now — the genuine reason this company and this moment are where I want to build; (4) Closing commitment — what I will accomplish in my first 12 months. Write the full 60-second pitch as delivered language, then give me a blank template with placeholders I can customize for each company I interview with.

You are a VP of Product career strategist and executive coach. Help me build a comprehensive career track map for a VP of Product who wants to understand all the high-value paths available beyond their current operator role. Map the full career track across 5 paths: (1) VP of Product to CPO — what changes at the CPO level in terms of scope, board interaction, and the skills that matter most; what the typical timeline and trigger looks like for the transition; (2) VP of Product to Founder or Co-Founder — how VP of Product experience maps to founding a company, what investors look for in a product-background founder, and the specific advantages and gaps a VP of Product brings to the founding team; (3) VP of Product to VC or Principal at a venture fund — how product operators transition into venture, what the typical entry point looks like (scout, EIR, or direct principal hire), and what funds are most receptive to product-background investors; (4) VP of Product to Product Advisor or Fractional VP — what a fractional or advisory practice looks like in 2026, how to build a client base, typical engagement structures, and realistic income ranges of $15k–$40k per month; (5) VP of Product to Board Member — the path from operator to board-level contributor, how a technical or product advisory board role differs from a board seat, and how the transition typically happens. For each path: the 2 most important things to do while still in the current VP role to set up the transition, and one specific action that opens the door.