VP of Product Search
VP of Product searches fail more often than they should because the brief describes what the company wants product to be, not what it currently is. The gap between those two states is the job — and it requires a specific kind of person to close it.
Founder, Majhi Group & Majhi OS
VP of Product is the executive hire that companies most often get wrong at the growth stage — not because good product leaders don't exist, but because the brief is almost always written about the product the company wants to have, rather than the product organisation the company actually needs to build.
The result is a search that attracts candidates who are excellent at running a mature product function and evaluates them against criteria that would make sense if the product function already existed in the form the company wants. It doesn't. That's why they're running the search.
What the VP of Product actually inherits
At most growth-stage companies running a VP of Product search, the incoming leader inherits one or more of the following: a product roadmap that has been built by committee and lacks a clear strategic logic; a product team that is talented but has been operating without a consistent process or prioritisation framework; an engineering team that has been building what the sales team asked for rather than what the product strategy requires; and a founding team that has strong opinions about product direction and has not yet fully separated the founder's role from the product leader's role.
These are real conditions, and they are the conditions under which the VP of Product will be working for at least the first 12 months. The brief that doesn't describe them accurately produces candidates who are surprised by them — and a hiring process that hasn't assessed whether the candidate can navigate them.
The PM who became a manager vs. the product executive
There are two distinct profiles under the VP of Product title, and they are not interchangeable.
The product manager who grew into leadership. This person started as a PM, became excellent at it, started managing other PMs, and is now leading a product team. Their strength is deep product craft — they understand user research, prioritisation frameworks, roadmap development, and the PM-engineering-design triad at a level that earns respect from the teams they lead. Their potential limitation is that they have grown within a product function that already existed; they may not have built one.
The product executive who has built functions. This person has been accountable not just for managing PMs but for defining what the product function is, how it operates, how it interacts with engineering and design and sales, and what the standards are for product work across the company. They have made the structural decisions — how product is organised, what the prioritisation process looks like, how product strategy connects to business strategy — that shape whether the product function works at scale.
A company that needs the first profile and hires the second will get a product executive who is overqualified for the current state and will leave within 18 months for something more complex. A company that needs the second profile and hires the first will get someone who excels at the craft but struggles with the organisational work that the stage requires.
The CPO vs. VP Product distinction
At a certain scale, companies separate the Chief Product Officer role from the VP of Product role. The CPO is accountable for the product vision and the product strategy — where the product is going and why, in terms that align with the company's business strategy. The VP of Product is accountable for execution — how the product team actually delivers against that vision.
Below that scale, one person typically holds both accountabilities. The question at the intake stage is which accountability the company most needs right now. A company where the product direction is clear but the execution is broken needs a VP of Product with strong execution capability. A company where the product direction is unclear — where there is internal disagreement about what the product should be — needs a CPO-level thinker who can establish and defend a strategic position.
Running a search without resolving this question produces candidates who are evaluated on the wrong criteria.
What strong VP of Product candidates evaluate
Strong product leaders evaluate the quality of the decision-making environment they would be entering. Who has authority over product decisions, and is that authority clear? How does product relate to engineering — is it a partnership of equals, or does one function dominate the other? How does the founding team or CEO relate to the product — are they willing to give the VP of Product genuine ownership, or will every significant decision require founder approval?
These questions are not academic. The VP of Product who joins a company where product authority is unclear will spend the first six months in political work — establishing their role relative to other stakeholders — rather than in product work. The best product leaders have seen this dynamic before and screen for it actively.
They also evaluate the quality of the product team they would be inheriting. Not just the talent, but the culture: is this a team that has been empowered to do good product work, or a team that has learned to execute what they're told? Rebuilding a team culture is possible but takes time — and a VP of Product candidate who is being assessed partly on first-year outcomes needs to understand what they're starting from.
What closes the VP Product search
Write a brief that describes the product organisation as it is, not as you want it to be. Be specific about what the VP of Product will be accountable for building, what authority they will have to make decisions, and how their role will interact with engineering, design, and the founding team. Candidates who have navigated this specific set of conditions before will engage with the specificity. Candidates who haven't will either not engage or accept the role and discover the conditions later.
Majhi Group runs retained VP of Product searches. The engagement starts with an honest assessment of the current state of the product function and what the incoming leader will actually need to do.
If a VP Product search has produced candidates who looked right but haven't closed, or a close that didn't last past 12 months, request an assessment.
Majhi Group
Running a search that won't close?
Majhi Group runs retained VP and C-suite searches. 30–45 days against the 65–90 day industry median. 90-day replacement guarantee.
Request a Search Assessment →Continue Reading
Related writing
VP of Sales Search
VP of Sales is the executive search with the highest first-year failure rate. The reason is almost always the same: the company hired a sales rep who became a manager instead of a sales leader who builds systems.
CMO Search
CMO is the most inconsistently defined C-suite title in technology. The same two letters cover at least four genuinely different jobs. A search that doesn't resolve which one it's running will fail before outreach begins.
CFO Search
The CFO role changes more across company stages than almost any other C-suite position. A brief written for the wrong stage produces candidates who are credentialed for a company the business isn't yet — or isn't anymore.