Range and the Product Management Hiring Puzzle
I've been job searching for a a little over a month now, and I keep seeing something that puzzles me.
Product management job postings have gotten incredibly specific. Not just "we're looking for a fintech PM" or "healthcare experience preferred." Three levels deeper than that.
"PM with experience building real-time payment processing for B2B SaaS platforms serving mid-market financial institutions, with regulatory compliance background in SOC 2 and PCI-DSS, preferably in embedded finance solutions."
At first, I thought this was just a few outlier postings. But the pattern is everywhere. Every domain, every company stage. Ultra-specific requirements that narrow the candidate pool to maybe a dozen people who probably aren't looking.
I understand why companies do this. Hiring is expensive and risky. You want someone who can hit the ground running. Domain expertise feels like a way to de-risk the hire. Someone who already knows the space won't need as much ramp time. They'll understand the customers, the regulations, the competitive dynamics.
It makes sense. Except I don't think it's actually working.
The Kind vs. Wicked Problem
I've been re-reading David Epstein's "Range: Why Generalists Triumph in a Specialized World," and it's reframed how I think about this hiring pattern.
Epstein distinguishes between two types of learning environments:
Kind environments: Rules are clear and consistent. Patterns repeat. Feedback is immediate and accurate. Think chess, golf, classical music. In these environments, early specialization and deep, deliberate practice create mastery. Ten thousand hours in one domain pays off because the domain stays stable.
Wicked environments: Rules are unclear or constantly changing. Patterns don't repeat exactly. Feedback is delayed, incomplete, or misleading. Think most of the real world: business, technology, innovation, strategy. In these environments, generalists with broad experience outperform specialists because they can adapt, see patterns across domains, and avoid cognitive entrenchment.
Product management is a wicked environment.
Every company is different. What worked at your last company might not work here. The market shifts constantly. Customer needs evolve. Technology changes. Competitive dynamics are fluid. Feedback on whether your strategy worked comes months or years later, long after you've made the next dozen decisions.
Yet we're hiring for product management like it's chess. Like deep expertise in one ultra-narrow domain is what creates success.
The Question Worth Asking
Both PM craft and domain knowledge are learnable. None of us were born product managers. I started in oceanography, building 3D analytical tools for oil and gas. Then someone else wanted what I was building, and then more people, and suddenly I was learning product management by doing it.
The question isn't "is it learnable?" Everything is learnable given enough time and motivation.
The question is: what's faster to acquire on the job, and what creates more value long-term?
Domain knowledge takes 3-6 months for a competent PM to acquire:
Talk to customers. Understand the regulations and workflows. Map the competitive landscape. Learn the terminology. Figure out market dynamics. Shadow sales calls. Read support tickets. Talk to subject matter experts. Dig into the data.
This is just table stakes PM work. Any PM worth hiring knows how to learn a new domain. That's part of the job.
PM fundamentals take years to develop:
Decision-making under uncertainty. Influence without authority. Synthesizing messy feedback into clear strategy. Knowing what to build and what to kill. Understanding tradeoffs and making them explicit. Translating between customer problems, business needs, and technical constraints. Creating clarity when everyone else sees ambiguity. Building trust through consistency and follow-through. Product sense, that hard-to-define intuition about what will resonate with users and what won't.
These capabilities don't come from domain knowledge. They come from navigating complexity across multiple contexts. From making decisions with incomplete information and learning from what happened. From building products that succeed and products that fail and figuring out the difference.
The Power of Analogical Thinking
Epstein's research shows the most valuable skill in wicked environments is analogical thinking. The ability to spot patterns across different domains and apply solutions from one context to another.
This is exactly what PMs with range bring to the table.
Gaming taught me retention mechanics and monetization psychology. When I moved to SaaS, those insights transferred directly. Retention isn't domain-specific. It's about understanding human behavior and creating habits. Monetization isn't about gaming. It's about value exchange and willingness to pay.
Someone coming from consumer products might see your B2B workflow problems completely differently. They've optimized for simplicity at scale. They understand onboarding friction. They think about first-run experiences in ways B2B folks often miss.
Someone from heavily regulated industries might help you think about compliance as a feature, not overhead. They've designed systems where constraints drove creativity.
A PM who's successfully navigated 2-3 different contexts has developed pattern recognition that's more valuable than someone who's only ever lived in one narrow space. They've learned what transfers and what doesn't. They've built a repertoire of mental models they can apply flexibly.
This is what creates competitive advantage: cross-pollination of ideas, fresh perspectives, ability to adapt when the environment shifts.
Hiring only from your exact niche creates what Epstein calls "cognitive entrenchment." Everyone thinks the same way, sees the same patterns, proposes the same solutions. That's not how innovation happens.
Innovation Comes From the Edges
Epstein cites extensive research showing that breakthrough innovation often comes from outsiders or people who combine multiple fields, not from narrow experts within a domain.
People with hybrid careers produce more creative work. Cross-domain teams innovate more than homogeneous teams. Experts in a single domain can become blind to novel approaches. They've optimized so deeply for one way of thinking that alternative framings don't even occur to them.
The fintech company that only hires fintech PMs won't see the solution that's obvious to someone from a different domain. The healthcare company that only hires healthcare PMs will keep building the same patterns everyone else builds.
The PM who brings gaming psychology to enterprise software, or consumer simplicity to B2B workflows, or marketplace dynamics to SaaS? That's where the interesting work happens.
The Sampling Period Advantage
Epstein talks about the power of "sampling periods." Instead of specializing early, successful people often try many things before focusing. This broad exploration helps them discover where their talents lie, what they enjoy, and how different domains connect.
He contrasts the "Tiger Woods model" of early specialization with the "Roger Federer model" of late specialization. Federer played multiple sports as a kid. He didn't focus exclusively on tennis until his teens. Yet he became one of the greatest tennis players ever.
In complex fields, the Federer model is far more common than the Tiger Woods model.
A PM who's navigated gaming, then SaaS, then fintech has gone through a sampling period. They've tested different contexts. They've learned what kinds of problems energize them. They understand what transfers across domains and what's unique to each space.
That breadth is an asset, not a liability.
What This Means for Hiring Managers
I understand the impulse toward specificity. You're trying to reduce risk. You want someone who can contribute immediately. You don't have time to ramp someone up on domain fundamentals.
But I think this approach is creating more risk, not less.
You're optimizing for what's easy to verify (does their resume check these boxes?) instead of what actually predicts success (can this person navigate complexity, influence across functions, and make good decisions with incomplete information?).
You're screening out people who could solve your problems because they solved similar problems in different contexts. You're missing the analogical thinkers, the people with range, the ones who bring fresh perspectives.
And you're competing for an impossibly small talent pool. That person with your exact background? They're either not looking, or they're interviewing at five other companies who are being less restrictive, or they're commanding compensation that reflects how scarce they are.
Here's what I'd suggest instead:
Hire for PM fundamentals plus adjacent domain experience plus demonstrated learning velocity. Not for perfect domain match. Look for people who've successfully transitioned between domains before. They've proven they can learn. More importantly, they've proven they can recognize what transfers and what doesn't.
Value diverse experience over narrow expertise. The person who's been in three different industries has built mental models you can't get from staying in one place. They've seen what works across contexts and what's context-specific.
Assess for analogical thinking in interviews. Ask about problems they've solved and how those insights might apply to your domain. "Tell me about a problem you solved in your last role. What patterns did you see? How might similar thinking apply here?" The best candidates will make connections you didn't see.
Look for evidence of learning velocity. How quickly have they ramped up in previous roles? What did they learn in their first 90 days? How did they build credibility in a new domain? This predicts ramp time better than resume matching.
Give people 90 days to learn your domain. Judge them on how fast they build credibility, not how much they knew on day one. A great PM with adjacent experience will be fully productive in three months. If your domain is so unique that it takes longer, you might have bigger problems.
Ask better interview questions. Instead of "do you have experience with X specific technology in Y specific context," ask "tell me about a time you had to learn a new domain quickly. How did you approach it? What mistakes did you make? What would you do differently?"
What This Means for Candidates
If you're job searching and seeing these ultra-specific requirements, don't assume you're not qualified just because you don't check every box.
Focus on showing transferable thinking. "Here's the problem I solved there that's similar to your problem here." "This domain taught me X, which applies to your space because Y." Make the connections explicit. Help them see what you see.
Prove your learning velocity with examples of past transitions. How did you ramp up in previous roles? What did you learn in your first 90 days? How did you build credibility in a new domain? Show them you've done this successfully before.
Emphasize pattern recognition across contexts. What insights from one domain helped you in another? What mental models transfer? This is analogical thinking in action. Most PMs don't articulate it well. If you can, you stand out.
Apply to places that value range over hyper-specialization. The companies writing ultra-specific job descriptions might not be the best fit anyway. Look for organizations that value learning, adaptation, and diverse thinking. The job description itself tells you something about the culture.
In your cover letter or intro conversation, name the pattern. "I noticed you're looking for someone with very specific domain experience. I want to explain why I think my background in [adjacent domain] actually makes me a stronger candidate." Then make the case with specifics.
The Broader Pattern
This isn't just about product management hiring. It's about how we think about expertise, specialization, and adaptation in a rapidly changing world.
Epstein's research shows that in complex, uncertain environments (which describes most of business and technology), breadth of experience beats depth of specialization.
The generalist advantage isn't about knowing a little bit about everything. It's about integrating knowledge from multiple domains, adapting quickly to new contexts, and seeing connections others miss.
Product management sits right in the middle of this. We're translating between customer needs, technical constraints, and business goals. We're navigating uncertainty. We're influencing without authority. We're synthesizing messy inputs into clear direction.
That's a wicked environment if there ever was one.
The ultra-specific domain requirements optimize for the wrong thing. They screen for people who've done exactly this before, when what you actually need is someone who can figure out what to do when the situation is new.
A Different Way Forward
I'm not arguing against domain knowledge. It matters. Someone with zero understanding of your space will struggle.
I'm arguing for adjacent domain experience over perfect domain match. For analogical thinking over narrow expertise. For learning velocity over resume matching.
The PM who's built marketplaces and now wants to work on SaaS brings marketplace thinking to your platform. The PM who's built consumer products and now wants to work on B2B brings simplicity and onboarding expertise. The PM who's built in heavily regulated industries brings a different relationship with constraints.
That's valuable. Maybe more valuable than someone who's only ever built in your exact space.
Range matters. Especially in wicked environments.
Maybe it's time to hire accordingly.