SVP – Product and Markets — Developer-Tools Business

The mandate

A multinational-owned developer-tools business has accumulated a portfolio whose product boundaries no longer correspond to customer economics. Capabilities overlap, bundles obscure adoption and separate roadmaps compete for the same engineering skill. Some products attract developers but do not convert; others generate revenue while increasing support and integration cost. An urgent portfolio consolidation now needs permanent leadership.

The SVP – Product and Markets will steward approximately US$1,350 million in annual recurring revenue and lead around 400 employees and material partners. The perimeter covers product strategy, portfolio management, market insight, product operations, commercial design, lifecycle decisions, partnerships, product talent and customer evidence. Reporting is to the Group Chief Executive or designated executive committee sponsor.

The portfolio must be rebuilt around customer work. The executive will map discovery, build, test, deploy, secure, observe and govern workflows, identifying where the business removes meaningful friction. Product usage, switching behaviour, willingness to pay and service consequence should determine boundaries more reliably than historic ownership or codebase.

Each product needs transparent lifecycle economics. Acquisition, active use, conversion, expansion, cloud cost, support, engineering demand and retention should connect by cohort. A product with growing bookings may still destroy value if adoption is shallow or bespoke service expands faster. The SVP will establish comparable evidence before deciding to invest, combine, maintain, partner or retire.

Consolidation should reduce complexity for customers, not simply the organisation chart. Entitlements, APIs, data models, integrations, packaging and migration paths must be designed as a coherent experience. Removing a product without resolving its critical workflow can force customers into workarounds or competitors. Customer councils and controlled migration evidence should inform gates.

Roadmap capacity will be explicitly allocated. Reliability, security, technical debt, platform leverage, migration and new value compete for finite teams. The SVP must show what will not be delivered and the customer or economic consequence. Unfunded commitments and executive exceptions need a visible expiry or trade-off.

Markets are part of the product decision. Enterprise platform teams, individual developers, regulated buyers and technology partners have different adoption and service needs. The leader will choose priority segments and ensure product, pricing, channels and customer success support the same thesis. Broad relevance cannot remain a substitute for segment preference.

Developer trust requires careful handling. Changes to interfaces, licences, data use or roadmap can propagate rapidly through technical communities. Communications must be early, precise and supported by migration tools. The business should measure retained usage and successful transition, not declare success because an end-of-life notice was delivered.

The product organisation will need new decision rights. Product leaders should own outcomes and economics, engineering leaders technical integrity and commercial leaders market execution. Shared platforms require a clear customer and funding model. The SVP will assess leaders, fill gaps and ensure succession for critical value streams.

Why this seat is open

An accelerated leadership transition created an urgent replacement requirement. Interim coverage preserves current roadmaps, but a consolidation cannot remain under divided authority. The board expects a permanent appointment within six to eight weeks and is managing predecessor circumstances neutrally and confidentially.

What you will own

• Reframe the developer-tools portfolio around customer workflows and economics.
• Steward decisions across approximately US$1,350 million of annual recurring revenue.
• Choose which products to invest, combine, maintain, partner or retire.
• Align packaging, entitlement, migration and service across the consolidated suite.
• Allocate roadmap capacity among value, reliability, security and technical debt.
• Lead approximately 400 employees and partners across product and markets.
• Select priority segments using adoption and lifecycle-profit evidence.
• Build accountable product leadership and succession for each value stream.

The first 12 months

In the initial 90 days, reconcile portfolio and cohort facts, meet the 30 stakeholders most affected by the mismatch and assess leaders. Identify immediate customer, reliability and commitment risks. Agree board gates for consolidation, migration, capital and product retirement.

Months four to nine should activate the target portfolio, stop low-value roadmap work and launch controlled migrations. Product, engineering, sales and customer success need one definition of adoption and value. Early results may include capacity released, higher active use, lower support burden or clearer segment conversion.

At the first-year close, portfolio focus, adoption and lifecycle profitability should move together. Delivery must remain within 10% of the agreed case, supported by three forecasts that reconcile products, usage, recurring revenue, cash, customers and people. Material migration risks require independently accepted closure before irreversible retirement.

What the board will measure

• Product investment and retirement decisions grounded in cohort economics.
• Active adoption and paid conversion across selected developer workflows.
• Engineering capacity released from overlap and low-value commitments.
• Customer migration completed without hidden service or retention damage.
• More than 90% retention of pivotal talent and ready cover for 70% of direct roles.
• Lifecycle profitability incorporating cloud, support and technical demand.

The person

You are an SVP Product, Product Line GM or Commercial Product Head with 22–28 years in technology or an adjacent enterprise. You have owned a material platform or value stream end to end, including budget, talent and measurable operating outcomes.

Your accountable P&L, book, budget or portfolio must be at least US$800 million, and you have led 275 or more people. Strong evidence will include a portfolio choice that contradicted internal attachment and delivered sustained outcomes across two reporting periods.

You understand developer behaviour, product economics and the operational detail of consolidation. You can challenge optimistic roadmaps, protect customer trust through retirement and build alignment among product, engineering, go-to-market and support leaders.

Compensation and terms

The base range is US$320,000–420,000 plus annual incentive. This permanent San Francisco appointment is onsite and supports international relocation rather than remote tenure. Notice periods of up to six months may be accommodated.

Confidentiality

The client, predecessor, product map and customer evidence are confidential. Identifying details will be released when both parties elect to proceed under a mutual undertaking; the stated facts have been blended.