Domain Expertise Is the Wrong Filter. Here's What to Use Instead.
The product marketing job market is brutal right now. That's not an opinion, it's what the numbers say. According to layoffs.fyi, more than 245,000 tech workers were cut in 2025 alone, and the pace in 2026 has accelerated to nearly 975 per day. A meaningful share of those cuts landed in marketing, and experienced PMMs — practitioners with eight, ten, twelve years of real work behind them — are sitting on the sidelines months into their search with no clear end in sight.
The instinct is to blame the market. And the market is genuinely difficult. But there's a second problem compounding the first, one that is entirely self-inflicted: hiring managers at the companies still adding headcount are using a filter that doesn't work. They're requiring domain expertise, specifically that candidates come from the same vertical the company operates in. In doing so, they're systematically passing on some of the best PMM talent available.
I want to be clear about what I'm arguing. Domain expertise has real value. I'm not dismissing it. What I'm arguing is that using it as a hiring filter is the wrong call, because domain knowledge is teachable by the people already inside your organization. PMM craft isn't. Commercial instinct isn't. The business literacy required to influence strategy isn't. Those capabilities come from years of doing the work at a high level, and right now, the hiring managers who understand that distinction have access to a candidate pool they are not going to see again for a long time.
The Market Has Changed. The Filter Hasn't.
The scale of displacement in tech over the past eighteen months is significant enough that it's worth pausing on. Robert Half's analysis counted more than 24,800 PMM-specific job postings in 2025. At the same time, companies report difficulty filling those roles. Searches stretch to six months. Hiring managers complain about the candidate pool. The disconnect is not a supply problem. It's a filtering problem.
Job descriptions that once listed domain experience as a preference have calcified it into a requirement. "Must have 3+ years in cybersecurity." "Financial services background required." Strong practitioners with genuine craft, real commercial instincts, and the kind of positioning capability that's actually hard to find get screened out before anyone reads the rest of their resume.
The obvious counter is: with this many candidates, why not use domain as a first-pass filter and then look for craft within that pool? It sounds efficient. The problem is that the pool inside the domain filter is not a random sample of the available talent. It skews toward practitioners who have stayed in one vertical, which correlates with exactly the category-conforming thinking that limits positioning work. The highest-ceiling PMMs, the ones with the most versatile craft and the sharpest commercial instincts, tend to move across categories. More practically: if the domain-filtered pool contained enough strong candidates, searches wouldn't be running six months. The filter isn't saving time. It's producing the scarcity problem hiring managers are actively complaining about.
This is a 2021 hiring posture operating in a 2026 market. When PMM talent was scarce and every strong candidate had multiple offers, tightening filters made sense; you could afford to hold out for a narrow match. That calculus has completely inverted. The talent is there. The candidate pool is genuinely deep. The filter is the constraint.
Domain Can Be Taught. Craft Can't.
Here's the core problem with the domain filter: it conflates two very different types of knowledge and treats the more acquirable one as the scarcer resource.
Domain expertise, knowing how your category works, who the buyers are, what they care about, what the competitive landscape looks like: that can be taught. Not by a training program, but by the people already inside your organization. Your sales team knows the buyer cold. Your product team lives in the market every day. Your CS team hears what customers actually struggle with. A strong PMM who joins without domain experience is not flying blind. They're inheriting a rich internal curriculum from people who are already expert in it.
Take CRM software as a concrete example. If you understand how sales and marketing leaders buy, how platform decisions get made inside a GTM organization, and how to translate technical capability into commercial outcome, you can pick up CRM domain competency faster than almost any other category. The buyers are familiar. The platform dynamics, ecosystem integrations, data centralization, GTM motion fit, are GTM concepts a strong PMM already understands. The technical depth that matters is learnable. What you bring on day one, the craft and the commercial instinct, is not.
PMM craft is different. The ability to develop positioning that creates genuine separation, build messaging architecture that holds under competitive pressure, and run a launch that moves the market rather than just announcing a release: those capabilities come from years of repetition across different situations, different products, different buyers. You cannot hire for domain and expect craft to follow. But you can hire for craft and teach domain.
One product management practitioner made this argument recently: over-indexing on domain experience carries a specific risk: people too steeped in how a category currently works often can’t see past it. For a PMM function whose job is to move the company to its next stage, that’s a meaningful constraint.
There are real exceptions to this, and they're worth naming. Some categories carry technical depth that can't be meaningfully compressed: deep infrastructure software, quantum computing, highly regulated industries where compliance architecture is genuinely years-long to master, or situations where the PMM needs to function as a quasi-subject matter expert to have credible conversations with product and buyers at all. In those contexts, domain experience at hire isn't a preference, it's a functional requirement. But that band is narrower than most hiring managers assume, and it doesn't describe the majority of enterprise B2B SaaS categories where the domain filter gets applied most aggressively.
You're Not Trying to Stay Here. You're Trying to Get to the Next Stage.
There's a version of this argument that goes beyond the hiring logic, and it's the one I find most compelling.
The companies that most frequently default to domain filters are growth-stage B2B SaaS organizations trying to get to their next inflection point: from $50M to $100M ARR, from one segment to three, from a single product to a platform play. At exactly that moment, when breaking through requires challenging the assumptions baked into how the category has always worked, they hire someone whose entire professional identity is built on those same assumptions.
A PMM who spent six years in, say, HR tech doesn't arrive with a fresh perspective on how HR buyers think. They arrive with their previous company's perspective, encoded over six years of repetition, shaped by a specific competitive context and a specific product narrative. That's not a clean read on the market. It's a weathered one. And weathered reads tend to produce messaging that sounds fluent, credible, and indistinguishable from everyone else in the category.
| The PMM who has never worked in your category will ask why you say things the way you say them. The one who has worked in it for five years already knows — and that's exactly the problem.
I've seen this play out more than once. A company brings in a PMM with strong vertical credentials, and in the first quarter they produce messaging that sounds polished and category-appropriate. It also sounds exactly like the category. It confirms what buyers already expect to hear. It doesn't create separation. The PMM isn't doing anything wrong by their own reference points; they're drawing on what has worked in the space. But what works in the space is, by definition, not what gets you past it.
The PMM coming in without legacy assumptions has something genuinely valuable: the discipline to do a real deep-dive on the market from scratch, without the shortcut of already knowing how the category talks about itself. That learning process, done rigorously, often surfaces angles and contradictions that the insider has long since stopped seeing. It's not a limitation. Used well, it's an advantage.
AI Has Changed the Ramp Equation
Even setting aside the strategic argument above, the practical case for requiring domain expertise at hire has eroded significantly over the past two years.
The traditional logic held that domain ramp was slow: roughly six months to reach genuine working competency in a new vertical. Learning the buyer vocabulary, absorbing the competitive landscape, understanding the use case universe, building enough context to have credible conversations with sales and product. That timeline was real. It was also the economic justification for the domain filter.
That justification has collapsed. A strong PMM with a well-structured research workflow can build working competency in a new category in three to four weeks, not six months. Competitive landscape analysis that once required weeks of primary research now takes days. Buyer language patterns can be extracted at scale from call recordings, review sites, and support ticket data. Technical concepts that once required months of osmosis can be explored iteratively until they click. The adoption of AI-driven research and synthesis tools across marketing functions has fundamentally changed what domain ramp costs, and the trend is not reversing.
The trade-off you're making when you require domain expertise is no longer months of reduced productivity in exchange for years of category advantage. The ramp is short enough now that the trade isn't worth making, particularly when the candidate who ramps quickly may bring exactly the perspective your positioning needs most.
What AI cannot replicate is judgment: knowing which question to ask, which insight actually changes the commercial conversation, how to look at a category from the outside when you're working from inside it. That is the craft. That is what you should be hiring for.
What to Filter For Instead
Dropping domain expertise as a screen doesn't mean accepting vague capability claims. It means replacing one filter with better ones. At BlindSpot, we think about PMM performance through three capability layers, the PMM capability model: PMM craft, marketing acumen, and business literacy. None of these require vertical-specific experience. All of them predict performance.
PMM craft is the foundation. Can this person develop positioning that holds up under competitive pressure? Can they build messaging architecture that translates accurately across audiences without losing coherence? Can they run a launch that reflects how buyers actually move rather than how internal teams prefer to operate? The test for craft is not a portfolio review. It's a live work exercise: give a candidate a real positioning problem and watch how they work through it. Do they start from the buyer's problem or from the product's features? Do they ask about the competitive context or assume it? Can they form a defensible point of view and hold it when pushed? Category knowledge is not required to demonstrate any of this.
Marketing acumen is the commercial layer. A PMM who doesn't understand how pipeline works, how demand is generated, or how buyers stall operates as a content function, not a strategic one. They produce assets no one can connect to revenue outcomes. Marketing acumen develops across industries; it is not vertical-specific. The signal in an interview is how a candidate talks about the connection between their PMM work and commercial results. Not which metrics they tracked, but how they reasoned about the relationship between what they built and what moved. Robert Half’s research consistently shows demand for PMMs who operate across the full GTM spectrum, a competency defined by commercial instinct, not category knowledge.
Business literacy is the strategic layer, and where the most capable PMM candidates tend to get undervalued because the filter is pointed at the wrong thing. Business literacy is fluency in how the organization makes money, how leadership frames market position, how GTM decisions connect to the numbers that matter at the board level. As I wrote in an earlier post on why PMM loses influence, the most common reason product marketing gets sidelined is not that it lacks domain knowledge. It's that it lacks fluency in how the business thinks. A PMM who can read a P&L, reason through a pipeline coverage problem, and connect their positioning work to revenue outcomes earns a seat in the strategic conversation. Domain expertise doesn't get you there. Business literacy does.
For how the capability model connects to the structural decisions around building the PMM function itself, the January 2026 post on hiring PMM covers the organizational layer alongside the capability one.
What This Looks Like in the Interview
Replacing the domain filter doesn't require rebuilding your hiring process. It requires knowing what you're looking for and structuring the evaluation to surface it.
For PMM craft, the most reliable signal is a live work exercise, not a polished portfolio. Give candidates a product description and a target buyer segment and ask them to work through a positioning argument out loud. You're not evaluating the output. You're watching the thinking: do they start from the buyer's problem or the product's feature set? Do they ask clarifying questions about what the competitive alternatives are? When they land on a position, can they defend it when pushed? Category knowledge is not required to demonstrate any of this.
For marketing acumen, ask candidates to walk through how their PMM work has connected to pipeline or revenue outcomes. The question is not about metrics. It's about whether they can trace the relationship. A PMM with genuine commercial instinct will give you a specific answer: how a messaging change affected a particular stage of the funnel, how a competitive repositioning shifted win rates in a specific segment. A PMM without it defaults to outputs: "I built the sales deck," "I ran the launch."
For business literacy, listen to how candidates talk about the organizations they came from. Do they understand how the company made money? Can they describe what the GTM priorities were and why? Do they connect their PMM work to the commercial logic behind it, or do they describe it in isolation? The gap between strategic and tactical PMMs shows up here more clearly than anywhere else, and it has nothing to do with which verticals they worked in.
The Filter Is Costing You
The current market has created something unusual: a deep pool of experienced, capable PMM practitioners, many caught in broad workforce reductions that had nothing to do with their performance. Companies running domain filters are walking past them.
Domain expertise matters. The practitioners who have it bring real value, and there are roles where it genuinely accelerates what's possible. But it is not a proxy for PMM performance, and it should not eliminate an otherwise strong candidate. It is a variable your organization can address through onboarding, through the internal expertise that already exists, and through the AI-assisted research workflows that have made category ramp faster than it has ever been.
What you cannot address after hire is the absence of craft, the absence of commercial instinct, or the absence of the business literacy that gets PMM into the strategic conversation. Those are the things worth filtering for. And right now, in a market flooded with experienced practitioners, they're available if you're willing to look for them correctly.
One practical note: for many hiring managers, the harder challenge is not changing their own filter but resetting an expectation that was established before the search started. If your CEO or board has anchored on "someone with industry experience," this post gives you the framework to have that conversation. The argument isn't that domain doesn't matter. It's that craft, acumen, and business literacy matter more, and that a candidate who brings all three can get to domain competency faster than ever. That's a case worth making before the wrong hire makes it for you.
BlindSpot works with CMOs, VPs of Marketing, and CEOs at enterprise B2B SaaS companies on the decisions that determine whether the PMM function performs: what to hire for, how to structure the evaluation, how to build the capability model into the role rather than just the job description. If you're navigating a PMM hire and want a clearer framework for making the call, contact BlindSpot to talk through it.
