Principal Product Manager - Vertical Data

The Role

Depth is a differentiator in go-to-market data. Knowing a company exists is table stakes. Knowing its fleet, its franchise structure, its lenders, its benefits plans, and its real estate is what closes deals. That kind of depth only works if every record from every source resolves back to the right company and the right person, and almost nobody can do that at scale. ZoomInfo can. The entity resolution infrastructure we've spent years building lets us stitch specialized datasets together into a single connected view of a business, and it's why vertical data is becoming a core part of how we grow our monetizable data assets. We're investing in the team behind it.

We're hiring a Principal Product Manager to own datasets end to end: where the data comes from, how it's built and resolved to ZoomInfo's company and contact universe, how it shows up across every surface we sell through, how it's priced and packaged, and how much revenue it generates. You'll also be the internal subject matter expert on these datasets: the data itself, the sources, the competitive landscape, and how customers actually use it.

We spend a lot of our time close to our strategic customers, working strategic opportunities directly with customers and our sales teams, shaping deals, and figuring out what a dataset needs to look like for a customer to actually buy it. Increasingly that means thinking in solutions, not single datasets. The most valuable thing we can do is package datasets together into workflows for a strategic vertical or a strategic customer, in a way that displaces the point solutions they're using today.

What You'll Own

The full lifecycle of a set of vertical datasets, which breaks down into three parts:

Dataset development. Define what the dataset is and who it's for. Source the data (public records, partner licensing, our own extraction and classification). Set the bar for coverage, accuracy, and entity resolution against ZoomInfo's company and contact graph, and work with our data analysts to hit it. Decide what "done" looks like for a dataset and hold the line on it.

Platform delivery. Partner with data engineering and platform engineering to get datasets out of the warehouse, into the GTM Data Store, and live across every surface: our APIs, MCP, and our applications. Write the requirements, define the use case queries, own the testing, drive the handoffs. This is the stage where most data products die. You'll make sure ours don't.

Commercialization. Own pricing and packaging: how a dataset shows up in the price book, what's licensed in bulk versus consumed per record, what needs supplemental terms, how it bundles with core data and with other vertical datasets. We're investing more and more in the product-led motion alongside the sales-led one, so this means enabling both: making datasets discoverable and consumable in-product, and building the sales materials our teams need to sell them by vertical: enablement content, data reference guides, use cases, positioning. Then go sell with them.

What You'll Do

Work strategic deals. Sit with sales on the accounts that matter. Get in front of customers, understand what they're actually trying to do with the data, and shape the dataset and the offer to fit. Some of this is presenting. A lot of it is listening and then going back and changing the product.

Build solutions, not just datasets. Figure out how UCC filings and commercial property data become a prospecting workflow for a commercial banker, or how Form 5500 and insurance producer data become a cohesive platform for the benefits and insurance market. Package datasets into something a vertical buyer recognizes as built for them.

Run point across data, engineering, and go-to-market. You're the person who knows where a dataset stands at every stage and is accountable for moving it forward. That means working with analysts on data quality, with engineering on delivery, with pricing and legal on terms, and with marketing on how it shows up in market.

Prioritize a portfolio. There are more datasets we could build than we can build well. You'll help decide which ones get investment based on revenue potential, customer pull, and what makes the core data more valuable.

Close the loop. What you learn from customers goes back into what we build next. What you learn from delivery goes back into how we build faster.

What We're Looking For

Commercially minded. You think about products in terms of who pays for them and why. You've owned a number, or been close enough to one that it changed how you prioritized. You're comfortable in pricing conversations and you know packaging is a product decision.

Heavy customer-facing background. You've spent real time in front of customers: enterprise product management with a lot of customer contact, solutions consulting, professional services, or a customer-facing role at a data company. You like it. You don't see customer calls as time away from the "real" product work.

Experience building data solutions. You've taken multiple datasets and turned them into a product or workflow that served a specific market, ideally in financial services, insurance, or another data-heavy vertical. You understand why a bundle of datasets wrapped in a workflow beats a data feed, and you've competed against point solutions on that basis.

Enjoys all of product management. Discovery, requirements, working with engineers, launch, enablement, pricing, and the unglamorous work of getting something actually shipped across multiple teams. Principal here means you can run the whole thing without a lot of scaffolding.

Data fluency. You can work in SQL, you understand entity resolution and the tradeoffs between coverage, accuracy, and freshness, and you can look at a dataset and form your own opinion about whether it's any good. Experience with B2B data, data licensing, or data-as-a-service is a strong plus. Experience with public records, regulatory filings, or vertical-specific data sources is a plus too.

Ownership and urgency. These are the two traits that predict success here. You take responsibility for outcomes, not deliverables. You move fast, make calls with incomplete information, and don't wait for process to exist before getting things done.

Proficient with AI tooling. AI tooling has let us move fast and compress work that historically took days and weeks down to hours and minutes. Your first instinct should be to reach for AI tools to work fast and produce an incredible amount of output. We use Claude Code and similar tools across the team for building, analysis, and writing, and you should be comfortable working that way.

Why This Role

Vertical data is a growth area for the company with executive sponsorship and real investment behind it. The datasets are live and generating revenue, customers are pulling, and the infrastructure to deliver across surfaces is in place. What we need is someone to own more of it.

You'll work with some of the largest enterprises in the world on data problems they care about, alongside a team of analysts, forward-deployed engineers, and AI-native builders. You'll have a direct line to the revenue your work produces. And you'll help define how ZoomInfo builds and sells specialized data for years to come.

#LI-AR2

#LI-REMOTE