The Un-Fakeable PM: Hiring for Impact in the Age of AI

As AI begins to commoditize the artifacts of product management (the PRDs, the roadmaps, and the market analyses), a quiet crisis is emerging for senior product leaders: How do we hire for a role when the traditional signals of competence can now be generated in seconds by a prompt?

At Product People, having supervised over 20 missions across sectors ranging from FinTech to HealthTech, I’ve seen that the cost of a bad hire has never been higher. When anyone can present a beautiful deck, the differentiator is no longer what a Product Manager can produce, but how they think under pressure.

To find true Builders in a sea of Prompt Engineers, we have to change the container of the interview. We need to stop testing for deliverables and start testing for the un-fakeable signals of high-stakes leadership.

‍

Looking for Un-Fakeable Signals

In the age of AI, we aren't suffering from a lack of information; we are drowning in it. The first un-fakeable signal I look for in a candidate is the ability to parse through an abundant amount of information without falling into analysis paralysis. Essentially, can they make a judgment and get things moving? 

That’s what I look for in the first 15 minutes of an interview. I’m not looking for the "right" answer; I’m looking for the ability to distinguish between "interesting" data and "decisive" data. Can they identify the signal in the noise? If a candidate cannot make a call when faced with a mountain of data, they will become a bottleneck for your engineering and design teams.

‍

Finding Real Builders

There is a common misconception that PMs shouldn't worry about the "how" of a product. While I don't expect a PM to make final architectural trade-offs, the era of the "hands-off" PM is over.

We need "Builders", aka, individuals with a technical mindset who are willing to roll up their sleeves and get dirty. This means a PM who can quickly prototype a feature if a designer is unavailable, or someone who can "vibe code" by understanding the core basics of software engineering. If a candidate only speaks in high-level jargon like "latency" or "LLM" without understanding the underlying mechanics, they aren't a builder; they’re a facilitator. Real builders understand the "cost" of a feature long before it hits the backlog.

‍

No More Case Studies

The traditional take-home case study is dead. It is too easy to fluff, and it doesn't represent the reality of the job. At Product People, we are moving toward an "In the Spotlight" simulation to test critical thinking under pressure.

Instead of a static presentation, we provide a baseline of information and expect the candidate to think on the spot. We use a progressive disclosure model: the more critical and analytical the candidate’s questions are, the more information we reveal. We aren't assessing the final deliverable; we are assessing the approach to problem-solving. This isn't a "gotcha" interview, but rather a stress test for the spotlight moments every PM faces when defending a trade-off to a skeptical C-suite.

‍

The Onboarding Nightmare

One of the most pervasive best practices in the industry is the extended onboarding period. I’ve seen PMs take six months just to settle in, and in my experience, this is a mistake.

Liquid takes the shape of the container. If you give a PM a six-month shadowing period, they will take six months to provide value. Instead, we should throw them into the deep end. PMs, by design, are built to manage ambiguity and pressure. By simulating a fast-paced environment from Day 1 and expecting value within the first few weeks, you find out very quickly if your Builder is actually ready to build.

‍

Scaling the Experiment

The hardest part of this shift is maintaining operations at scale. You cannot put 500 candidates through a high-intensity Spotlight session, for obvious reasons.

The solution lies in treating the hiring funnel like a product. We are currently experimenting with a series of async and sync steps designed to capture fit early on. The goal is to progress only high-potential candidates to the later, higher-cost stages. Just as in product management, our hiring process is experimental: we test, we learn from our mistakes, and we iterate.

‍

Conclusion

For VPs of Product and Tech Founders, the challenge is clear: stop hiring for the artifacts and start hiring for the engine. Look for the PM who can navigate the noise, who understands the vibe of the code, and who thrives when the spotlight is on them.

The cost of product management is clarity. If your hiring process doesn't demand clarity under pressure, you’ll end up with a team of great presenters, but very few builders.