David Meyer: Why You Should Hire People Who Aren’t In Product Already | E1076
Harry Stebbings (host), David Meyer (guest), Harry Stebbings (host)
In this episode of The Twenty Minute VC, featuring Harry Stebbings and David Meyer, David Meyer: Why You Should Hire People Who Aren’t In Product Already | E1076 explores why Great Product Managers Aren’t Born in Product Roles at All David Meyer argues that modern product management is widely misunderstood, often glamorized as a “mini-CEO” role when in reality it’s a demanding, compromise-heavy service function sitting between sales, engineering, customers, and finance.
Why Great Product Managers Aren’t Born in Product Roles at All
David Meyer argues that modern product management is widely misunderstood, often glamorized as a “mini-CEO” role when in reality it’s a demanding, compromise-heavy service function sitting between sales, engineering, customers, and finance.
He explains why he prefers hiring people who already behave like PMs in other roles (engineering, sales engineering, field) rather than those with conventional PM pedigrees, and how he tests for real impact versus “riding” a strong company’s success.
Meyer emphasizes truth‑seeking over being “data-driven,” using metrics only to expose blind spots, not as goals in themselves, and stresses customer obsession at the aggregate “collective customer” level, not overfitting to loud individual accounts.
Across hiring, org design, and leadership, he highlights emotional realities: everyone thinks PMs are terrible if they’re doing the job right, reality distortion can turn toxic, and effective leaders must combine optimism, vulnerability, and deep empathy for how people receive feedback and change.
Key Takeaways
Hire people who can’t stop product-managing from other roles, not just titled PMs.
Meyer looks for engineers, sales engineers, or field people who already fight for better specs, interrogate customer problems, and push back on bad product decisions; if someone can “live” in their function without doing that, he believes they’ll never be a strong PM.
Get the full analysis with uListen AI
Optimize for the collective customer, not the loudest single account.
He never lets individual customers design features; instead, he digs into what they’re trying to accomplish and checks whether that need is shared across the broader customer base to avoid overfitting and harming everyone else.
Get the full analysis with uListen AI
Use data to find blind spots, not to “win” arguments or chase vanity goals.
Meyer critiques “data-driven” cultures where dashboards become infinite scroll and metrics are weaponized; he argues metrics should trigger questions and course corrections, and targets should be changed when hypotheses are disproved.
Get the full analysis with uListen AI
If everyone loves you as a PM, you’re probably not doing the job.
Because PMs balance irreconcilable demands—sales vs. ...
Get the full analysis with uListen AI
Conduct customer conversations to understand the system, not to confirm your idea.
He goes into meetings “knowing nothing,” interrogates until he could do the customer’s job, and then reframes the problem and ideal outcomes; he acknowledges it’s very hard not to lead the witness, so he often brings others to observe and de-bias.
Get the full analysis with uListen AI
Design product reviews and decision forums with very small, high-bandwidth groups.
Meyer warns that large review meetings become ceremonies where language is diluted and misinterpreted; he prefers 4–6 deeply trusted, cross-functional people, with clear notes and context shared out afterward.
Get the full analysis with uListen AI
Great product leadership requires emotional intelligence as much as frameworks.
He tailors feedback style to individuals, explicitly mourns “killed” projects, uses vulnerability to build trust, and stays aware that his words carry asymmetric weight—while admitting this is an area he still needs to improve.
Get the full analysis with uListen AI
Notable Quotes
“If you're rocking it as a product manager, everybody thinks you suck.”
— David Meyer
“You’re not the rockstar, you’re the roadie.”
— David Meyer
“Don’t write unless you have to, because it’s miserable… and I feel the same about product management.”
— David Meyer
“The data in your progress serves one purpose only: to figure out your blind spots and where to ask questions.”
— David Meyer
“If you cannot not product manage, then you should be a product manager.”
— David Meyer
Questions Answered in This Episode
How can aspiring PMs in other functions practically demonstrate they’re already “doing product” to get considered for the role?
David Meyer argues that modern product management is widely misunderstood, often glamorized as a “mini-CEO” role when in reality it’s a demanding, compromise-heavy service function sitting between sales, engineering, customers, and finance.
Get the full analysis with uListen AI
What are concrete ways to avoid leading the witness in customer interviews while still testing a strong product hypothesis?
He explains why he prefers hiring people who already behave like PMs in other roles (engineering, sales engineering, field) rather than those with conventional PM pedigrees, and how he tests for real impact versus “riding” a strong company’s success.
Get the full analysis with uListen AI
How should a growing startup design its metrics so they’re truth-seeking and hard to game, rather than just vanity dashboards?
Meyer emphasizes truth‑seeking over being “data-driven,” using metrics only to expose blind spots, not as goals in themselves, and stresses customer obsession at the aggregate “collective customer” level, not overfitting to loud individual accounts.
Get the full analysis with uListen AI
When a CEO is deeply product-driven, how can a CPO carve out meaningful agency without creating constant strategic friction?
Across hiring, org design, and leadership, he highlights emotional realities: everyone thinks PMs are terrible if they’re doing the job right, reality distortion can turn toxic, and effective leaders must combine optimism, vulnerability, and deep empathy for how people receive feedback and change.
Get the full analysis with uListen AI
What signals indicate that a company’s reality-distortion field has tipped from empowering to toxic, and how should product leaders respond?
Get the full analysis with uListen AI
Transcript Preview
Do you think product managers today are worse than they were years ago? (drum roll)
On average, yes. Because I don't like happy customers. Because the opportunity to shift reality in the meeting is low. If there's a customer coming in rip shit about something, or upset about the product, you have an opportunity to totally reframe the way they look at the world. (drum roll) If you're rocking it as a product manager, everybody thinks you suck. If sales loves you, engineering hates you because you're chasing deals and you're not thinking about the long-term future. If engineering loves you, sales hates you because you're just doing long-term stuff and you're never helping them close a deal. It's finding these impossible compromises.
Why should people not go into product and product management?
It might sound goofy, but... (cymbals crashing)
(laughs) David, I am so excited for this. So I spoke to Ali years ago, and I've heard many great things, so thank you so much for joining me today.
I'm, I'm really excited to be here.
Well, I want to start, how did you make your way into the world of product? It's, it's an interesting world. What was your entry point?
You know, I'm a civil engineer by training, environmental/civil, and then I became a nuclear engineer. So it's not an obvious route. But I ended up, um, at this startup, Plumtree Software, and, uh, first running QA, then running engineering. This guy that ran product, Phil Sopher, he was, like, a very good friend of mine, and every day, I told him how he was doing his job wrong. I was the receiving end, building stuff, right? So I just told him this every day, and then one day, he decided to move on, to leave Plumtree, and he told the CEO I had run product.
Huh.
To, like, get back at me, right? I did it. I didn't want to do it, you know? I was like, "My job's too important doing engineering, you know? I can't give that up." But once I got into it, it was incredible. Like... (laughs)
(laughs) I've g- I've got too many things to ask you. First, on the, uh, you know, uh, helpful feedback to your boss, uh, or to your colleague-
(laughs)
How did you do that in a productive way that wasn't, um...
I, I was pretty young. I wasn't that productive.
(laughs)
Like, the, the thing is, you need to build things that matter, right? Like, I... The way I got into engineering is I was in QA and there was, uh, (laughs) there was this engineer and his stuff had so many bugs. So I went under the source control system and I started to figure out the bugs, right? Um, and he locked me out-
(laughs)
... of the source control system. I was like, "Wh- what the hell?" Right? So I went to the CEO, and I'm like, "I don't know what to do here. I want this code to work." So he fired the guy, and he told me to write it.
Install uListen to search the full transcript and get AI-powered insights
Get Full TranscriptGet more from every podcast
AI summaries, searchable transcripts, and fact-checking. Free forever.
Add to Chrome