Why the PM you hired isn't working out (and how to hire differently)

Failed PM hires are expensive in ways that don't always show up on a spreadsheet. There's the time lost, the team frustration, the product decisions that went sideways, and the erosion of trust that happens when a senior hire doesn't work out and everyone knew it for six months before anything was said.

After enough of these situations, patterns emerge. Here are the most common ones.

The level was wrong

This is the most common failure mode and the one companies are least honest with themselves about. A company at Series B decides it needs a senior PM and hires someone with seven years of experience at a large tech company. Six months in, the relationship is strained. The PM is frustrated by the lack of process and tooling. The leadership team is frustrated that the PM isn't 'scrappy enough.'

The problem isn't the candidate. It's that the role requires someone who has operated in resource-constrained environments where the PM has to do the research, write the tickets, chase the data, and still ship something by end of quarter. That person's resume often looks less impressive than someone who managed a team of researchers and PMs at a company where the infrastructure was already built.

Before scoping a search, be honest about what environment you're hiring into. A PM who thrived at Google may be a poor fit for a twenty-person startup. A PM who excelled in a scrappy environment may struggle with the governance requirements of a large enterprise. Neither is better. They're just different.

The mandate wasn't clear

Another common pattern: the PM was hired to 'own the product,' but what that meant was never agreed. The engineering team had their own views on what should be built. The CEO had strong opinions and a habit of going directly to engineers. The PM spent the first three months trying to establish what their actual authority was.

This is a leadership failure, not a PM failure. But the PM carries the consequences. They get labelled as not driving enough, not having enough influence, not being strategic. What they were, in many cases, was placed in an environment where product ownership was contested and nobody resolved that before the hire was made.

If you're hiring a PM into a team where product ownership isn't clearly defined, define it first. Or at minimum, be explicit with candidates that this is part of the challenge they're being hired to solve.

The skills were right but the timing was wrong

Some hires fail not because the person was wrong but because the company wasn't ready for them. A company in early product-market fit hires a PM with deep experience scaling mature products. The PM tries to introduce roadmap processes, OKRs, and structured discovery. The founders resist because they're still running on instinct and moving fast. The PM leaves after a year.

This happens in the other direction too. A company that needs rigorous process and stakeholder management hires a PM who is excellent at zero-to-one but has never managed the complexity of a large organisation. The PM is great at building things and not great at navigating them.

The question to ask before hiring: what does the product need to do in the next eighteen months, and what PM archetype does that require? Not what PM you can attract, or what seniority level your investors expect, what does the work actually demand?

Nobody was honest in the interview

Interviews are performances on both sides. Companies present their best version. Candidates present their best version. The hard questions about team dysfunction, slow engineering cycles, unclear strategy, or founder involvement in product decisions often don't get asked, or get deflected with optimistic answers.

The result is a hire who arrives expecting one environment and encounters another. If they're resilient and adaptable, they adjust. If the gap is too wide, they don't.

We think it's the recruiter's job to close this gap, not by making the company sound worse than it is, but by surfacing the honest challenges early enough that candidates who would struggle with them opt out before an offer is made. That costs a placement in the short term. It saves a failed hire in the long term.

How to hire differently

Define the environment, not just the role. What constraints will this person work within? What autonomy will they actually have? What's the hardest part of this specific context?

Be honest with shortlisted candidates. Share the real challenges. The right person won't be put off by them, they'll ask better questions about how to navigate them.

Assess for environment fit, not just capability. A strong PM in the wrong environment is a failed hire. Test for it directly: give them a scenario that reflects the actual conditions of your team and see how they respond.

Check references properly. Not 'was this person good?' but 'in what environment did they thrive? Where did they struggle? What kind of leadership did they need to do their best work?'