How to Hire a Director of Product / VP Product

What Is a Director of Product?

The Director of Product — also titled VP Product, Head of Product, or Senior Director of Product Management — is the most senior individual product management role at a scaling technology firm operating below the scale threshold where a Chief Product Officer mandate is warranted. The Director of Product is accountable for the product management function: the product roadmap’s quality and prioritisation, the product managers’ development and effectiveness, and the day-to-day delivery of the product management process that connects customer insight, commercial requirements, and engineering capacity.

This guide explains the Director of Product role, how it differs from the CPO above it, when each is appropriate, what the candidate profile looks like at a UK scaling firm, and how to run the search. It draws on the work Exec Capital does on product leadership appointments at UK technology firms and PE-backed software businesses.

The Director of Product is not a junior CPO. It is a genuinely distinct role with a different scope, a different authority level, and a different candidate profile. Firms that treat the Director of Product appointment as a budget-constrained substitute for a CPO will find that the hire either grows quickly beyond the role’s scope (and needs to be retitled and re-scoped within 18 months) or is frustrated by the title and authority mismatch and leaves. Getting the scoping right before the brief is written saves this very common sequence of events.

Director of Product vs CPO: Scope and Authority

The Director of Product and CPO roles are on the same career track but represent genuinely different scope and authority levels. Understanding the distinction is the foundation of a well-constructed product leadership brief.

The CPO owns the product strategy end to end — the firm’s view of which market to serve, which customer problems to solve, and how the product creates commercial value. The CPO operates at board and executive committee level, owns the commercial product logic, and has the authority to make strategic product bets that affect the firm’s direction. The CPO’s peers are the CEO, CFO, CMO, and CTO. For the full CPO mandate, the How to Hire a Chief Product Officer guide provides the relevant framework.

The Director of Product operates within an established product strategy — translating strategic direction into roadmap, managing the product management team, and ensuring the product management process is disciplined, data-driven, and connected to both customer insight and engineering capacity. The Director of Product’s peers are the Engineering Director, the Head of Design, and the heads of commercial functions. They report to either the CPO (where one exists) or the CEO (at firms where the Director of Product is the most senior product leader).

The key practical distinction is the locus of strategic product authority. A Director of Product who is reporting to a CPO has a clearly bounded mandate: execute the strategy, develop the team, and manage the process. A Director of Product reporting directly to the CEO at a firm without a CPO is effectively carrying a CPO-scope mandate regardless of the title — and should be scoped and compensated accordingly. Firms in the second situation who give the Director of Product title without the CPO scope create an authority gap that the product management team will feel immediately.

What a Director of Product Actually Does

The Director of Product mandate at a UK scaling technology firm covers five areas of ownership, each requiring a combination of product management expertise and people management capability.

Roadmap management and prioritisation. The Director of Product owns the product roadmap process — translating strategic direction into a prioritised backlog, managing the quarterly planning cycle, and making the trade-off decisions that determine what gets built, in what order, and at what quality. This is not simply receiving requests from sales or customers and scheduling them; it is the analytical and judgment-intensive process of weighting opportunities by commercial value, strategic fit, and engineering feasibility, and communicating the resulting priorities to all stakeholders credibly.

Product manager development and team leadership. The Director of Product manages the product management team — typically two to eight product managers at the relevant scale — and is accountable for their development, performance, and effectiveness. This means setting the standard for what good product management looks like at the firm, providing feedback and coaching, managing underperformance, and developing the next generation of senior product managers who will support the firm’s growth.

Discovery and customer insight. The Director of Product owns the product discovery process — the ongoing research and insight-gathering activities that ensure the product roadmap is grounded in genuine customer need rather than internal assumptions or sales anecdote. This includes managing user research, synthesising customer feedback from multiple channels, and maintaining the product team’s connection to the customers they serve. The quality of the discovery process directly determines the quality of the roadmap decisions.

Stakeholder management and cross-functional alignment. Product management requires effective relationships with engineering, design, data, sales, and marketing. The Director of Product manages these relationships at the working level — ensuring that the product roadmap is feasible from an engineering perspective, that design has the capacity and brief to support it, that sales has the product information they need to sell it, and that marketing can position it effectively. Misalignments at this level are the most common source of product delivery failures, and the Director of Product is the person responsible for catching them early.

Product metrics and reporting. The Director of Product maintains the product metrics framework — defining and tracking the indicators that measure product health and impact — and reports on product performance to the CPO or CEO and the executive team. This includes activation metrics, engagement trends, feature adoption rates, and the connection between product investment and commercial outcomes (retention, expansion, acquisition). A Director of Product who cannot construct and defend a clear product metrics narrative is missing one of the function’s most important outputs.

When to Hire a Director of Product Rather Than a CPO

The Director of Product appointment is appropriate in three specific contexts.

A CPO already exists and needs a strong number two. The most straightforward context: the CPO’s capacity is constrained by the growth of the product organisation, and the Director of Product provides operational product leadership below the strategic level. In this context, the Director of Product role is well-defined and the CPO’s relationship with the incoming hire is clear from day one.

A founder or CEO is acting as CPO and needs a product execution layer. At many early-stage scaling firms, the CEO or founder carries the product vision. The Director of Product they hire is responsible for translating that vision into a managed product process — roadmap management, PM team development, and discovery rigour — without needing to own the strategic product direction. This is a valuable appointment that preserves the founder’s product influence while building the operational capability the team needs.

The product management function needs professionalisation before a CPO hire is ready. At some firms, the path to a CPO hire goes through a Director of Product appointment first — building the product management process and team to the point where a CPO can step in with a properly functioning foundation. This sequencing is sometimes more efficient than attempting to hire a CPO into a product function that has no established process or team.

The Director of Product Candidate Profile

The Director of Product candidate pool in the UK draws from two primary sources: senior product managers who are making the step into management, and product managers or product leads who have some management experience and are ready for a larger team or a more senior individual role.

Product management depth is the non-negotiable foundation. A Director of Product who has not personally managed a product from discovery through delivery — who has not written user stories, managed sprint priorities, analysed product metrics, and made trade-off decisions under resource constraints — will lack the credibility with the product management team that effective product leadership requires. The Director of Product must be someone the PMs below them can learn from.

Management capability is the differentiator. Many strong individual product managers are not yet ready for the Director of Product role, because the management skills — coaching, feedback, performance management, hiring, and the shift from doing to leading — are different from product management skills and require development. The assessment should explicitly test management capability: how the candidate has developed a PM who was underperforming, how they have built a team’s capability in discovery or data analysis, and how they have managed the dynamics of a product team during a delivery crisis.

Stakeholder management at the commercial level. The Director of Product interacts with commercial leaders — sales, marketing, and customer success — in a way that requires commercial orientation. A Director of Product who cannot articulate the commercial value of a product roadmap decision, or who manages the engineering-product relationship without financial awareness, will consistently be under-resourced and under-supported by the commercial functions whose cooperation they need.

B2B vs B2C product experience. As with the CPO role, B2B and B2C product management require different skills and produce candidates with different default orientations. B2B Directors of Product are typically stronger on enterprise customer engagement, stakeholder roadmap management, and integration complexity; B2C Directors of Product are typically stronger on growth metrics, funnel optimisation, and consumer psychology. The brief should specify which context is primary.

Running the Director of Product Search

Director of Product searches are most effective when they include a product case study alongside structured interviews. The case study should present a realistic product prioritisation or discovery challenge — representative of the firm’s actual product context — and ask the candidate to work through it in a structured way. The output reveals both product judgment (how they approach the problem) and communication skill (how they present their thinking to a mixed audience).

For firms with an existing CPO, the CPO’s involvement in the assessment is essential — they will be the Director of Product’s primary working relationship, and their assessment of the candidate’s product quality and management style should be a central input into the decision. For firms where the Director of Product will report to the CEO, the CEO’s role in the assessment is equivalent.

Including one or two senior product managers in the interview process is valuable both as a quality check and as a signal to the candidate that the firm takes product quality seriously. The best Director of Product candidates appreciate rigorous assessment; it tells them something important about the culture they are joining.

Timeline for a well-run Director of Product search is typically 10–14 weeks. The candidate pool at this level is competitive — strong candidates have options — but the search is typically faster than CPO searches because the candidate pool is broader and the commercial seniority requirement is lower. See the Executive Search Methodology guide for the full retained search process framework.

Compensation Benchmarks

Base salary. Director of Product base salaries at UK scaling technology firms typically run from £100,000 to £160,000 depending on firm size, the scale of the product team, and the seniority of the mandate. VP Product titles at larger firms can reach £170,000–£200,000. The compensation gap between Director of Product and CPO is typically £40,000–£80,000 in base, reflecting the difference in strategic scope and board-level authority.

Bonus. Annual bonuses of 15–20% of base are standard. Product-linked KPIs — roadmap delivery rate, product adoption metrics, user satisfaction scores — are sometimes included.

Equity. EMI options of 0.1%–0.3% of the equity pool are common at series B–C firms. The equity component at Director of Product level is typically meaningful but below the CPO level, reflecting the difference in strategic accountability. The Executive Equity Incentives guide provides context on how equity is structured at scaling firms for roles at this level. Directors of Product considering their first equity-bearing role should understand the difference between EMI options, unapproved options, and growth shares before accepting an offer — the tax treatment and liquidity mechanics differ significantly between them, and the BADR and Section 431 guide covers the relevant UK tax considerations.

Common Hiring Mistakes

1. Hiring a CPO into a Director of Product role. CPO-calibre candidates who accept Director of Product titles typically do so because they need a job rather than because the role is right for them. The mismatch between their strategic ambitions and the role’s bounded scope usually surfaces within a year.

2. Promoting the most senior PM without assessing management readiness. Seniority as a product manager does not equate to readiness for management. The assessment should test management capability explicitly — not assume it from IC product track record.

3. Unclear reporting line and strategy ownership. The Director of Product needs to know clearly who they report to and who owns the product strategy they are executing. Ambiguity on either point creates dysfunction. These should be resolved before the role is advertised.

4. Insufficient time with the engineering function in the assessment. The Director of Product’s most important working relationship is with the Engineering Director or CTO. Including this person in the assessment process — and assessing the candidate’s ability to build a productive relationship with the engineering leadership — should be a standard part of the process.

5. Over-indexing on process knowledge at the expense of product judgment. A Director of Product who can facilitate a perfect sprint ceremony but cannot make a good prioritisation decision under uncertainty is a process manager, not a product leader. Assess product judgment directly — through scenario exercises and reference conversations with former engineers and commercial colleagues who can speak to the quality of decisions made.

How Exec Capital Approaches Director of Product Appointments

Exec Capital runs Director of Product and VP Product searches for UK scaling technology firms, PE-backed software businesses, and product-led companies at various stages. Our process for these appointments includes a product case study exercise built specifically for the firm’s product context, and we engage both the CPO (where one exists) and the Engineering Director in the assessment process.

For firms evaluating whether their product management needs are at the Director of Product level or the CPO level, or whether both roles are needed simultaneously (a CPO for strategy and a Director of Product for execution), we provide a diagnostic framework that maps the firm’s current product management gaps to the appropriate appointment. This scoping conversation is the most valuable 45 minutes a firm can invest before a product leadership search, because getting the level wrong is more expensive than the search cost — it is the accumulated cost of an appointment that does not deliver what the firm needed.

The Director of Product appointment sits within our product leadership practice alongside the CPO search practice. For firms evaluating whether they need a Director of Product or a CPO — a genuinely consequential scoping question — we are happy to provide a diagnostic view before any search engagement begins. The scoping decision determines the candidate pool, the compensation, and the authority structure: getting it wrong has downstream consequences that take years to unwind.

Onboarding Your Director of Product

The Director of Product’s onboarding needs to accomplish two things simultaneously: building a credible understanding of the product’s current state, and establishing the Director of Product’s authority with the product management team. Both require investment in the first 30 days, and the two are connected — the Director of Product who earns the team’s respect through genuine product knowledge will establish their authority more effectively than one who relies on title alone.

The pre-boarding briefing should include: the current product roadmap and the reasoning behind its priorities, the product metrics dashboard and the trend data for the past 6–12 months, the recent customer research and feedback, the engineering team’s assessment of the current technical debt, and the CPO’s or CEO’s honest assessment of where the product management function is strong and where it needs development. This context allows the Director of Product to enter the role with genuine understanding rather than spending the first month building a picture they should have been given.

The first 30 days should combine product deep-dives with team one-to-ones. The Director of Product should spend time with every product manager — understanding their current priorities, their development areas, and their perspective on the product’s most significant challenges. They should also sit in on engineering planning sessions, customer calls, and commercial team meetings where the product is discussed — building the full-context picture that effective product leadership requires.

Days 30–60 should produce the Director of Product’s initial assessment of the product management function: where the team is strong, where the process needs improvement, and what the highest-value changes would be in the next 90 days. This assessment should be shared with the CPO or CEO and used to align priorities before significant process changes are implemented.

Days 60–90 should deliver an improved roadmap process and a team development plan. By the end of the first quarter, the Director of Product should have implemented at least one visible process improvement — a better prioritisation framework, a stronger discovery rhythm, a cleaner roadmap communication — that the product management team and the engineering and commercial stakeholders notice as a genuine improvement. This visible early win is the Director of Product’s most effective credibility builder in the first quarter.

Product Management Tooling and Process Standards

The Director of Product typically inherits a product management tooling and process landscape that has evolved organically — a mix of Jira or Linear for issue tracking, Notion or Confluence for documentation, Amplitude or Mixpanel for product analytics, Productboard or Aha! for roadmap management, and various informal channels for customer feedback. One of the Director of Product’s early contributions is typically to rationalise and improve this landscape — not by replacing every tool immediately, but by building the process discipline around the existing tools that turns a collection of software into a coherent product management system.

The most important process standard the Director of Product establishes is the roadmap management process: how priorities are assessed, how trade-offs are made, how stakeholders are consulted, and how decisions are documented and communicated. A well-run roadmap process is the Director of Product’s primary mechanism for aligning engineering, commercial, and customer perspectives — and its absence is the most common source of product management dysfunction at scaling firms.

The Mind the Product community’s research consistently identifies roadmap communication as the product management capability most valued by commercial stakeholders — specifically, the ability to explain why certain things are being built and why others are not being built. The Director of Product who builds a roadmap communication process that the sales team, the customer success team, and the engineering team all understand and trust creates a disproportionate reduction in the cross-functional friction that is the primary source of product delivery frustration at most scaling firms.

The Director of Product in a B2B vs B2C Context

The Director of Product’s daily work is shaped significantly by whether the product serves businesses (B2B) or consumers (B2C), and the candidate profile and assessment should reflect this context explicitly.

In a B2B context, the Director of Product manages significant influence from enterprise customers on the product roadmap — customer-requested features, integration requirements, and enterprise-specific configuration needs. The skill is in distinguishing the specific needs of individual customers from the broader product direction that serves the market as a whole, and in managing customer expectations when the roadmap does not prioritise their specific request. The Director of Product in a B2B context also manages a complex stakeholder relationship with the sales and customer success teams, who are the primary conduits for customer feedback and whose commercial incentives sometimes conflict with the product’s strategic direction.

In a B2C context, the Director of Product manages a higher velocity of user data — activation metrics, engagement funnels, A/B test results, and cohort analyses — and makes more frequent, smaller-scale product decisions than their B2B counterpart. The skill is in building the analytics discipline that allows data-driven decisions at scale, and in maintaining the user empathy that prevents over-optimisation for metrics at the expense of genuine user value. The Director of Product in a B2C context typically works more closely with the design and growth teams and less closely with the enterprise sales function.

Further Reading and Authoritative Sources

For product management frameworks and the distinction between product manager and product leader roles, Silicon Valley Product Group provides the most widely cited framework for how product management should be structured at empowered scaling firms. Marty Cagan’s work on product teams versus feature teams is directly relevant to how Director of Product briefs are constructed and how the role’s mandate is defined.

The Mind the Product community publishes research on product manager compensation, career development frameworks, and the UK product management market that provides useful benchmarks for Director of Product compensation and career expectations. Their annual ProductTank survey data provides the most UK-specific product management compensation benchmarks available.

On building product management teams and developing product managers, Reforge provides professional development programmes specifically designed for senior product managers and product leaders — including the transition from individual contributor to product management leadership that the Director of Product appointment represents for many candidates.

The Productboard Product Excellence benchmarks and the Pendo product benchmarks provide data on product management metrics — feature adoption rates, time-to-value, NPS by segment — that Directors of Product use to calibrate their own firm’s performance against market norms. The Amplitude product analytics research covers the analytics practices that distinguish data-driven product teams from those that rely on intuition and anecdote. For compensation benchmarks specifically, the Index Ventures Rewarding Talent report provides UK-specific data on product management compensation at scaling technology firms.

The Teresa Torres Product Talk resources on continuous discovery are among the most influential in the UK product management community for building the discovery rigour that Directors of Product establish in their teams. The Intercom product management blog provides practical B2B product management frameworks widely used by UK scaling firms managing enterprise customer relationships. The Atlassian product management resources are widely referenced by UK product teams for agile product management practices and sprint ceremony frameworks.

Related Exec Capital guides: How to Hire a Chief Product Officer · How to Hire an Engineering Director · How to Hire a CTO · Tech and SaaS Executive Hiring · Scale-Up Executive Hiring · Executive Equity Incentives