How to hire an AI-native product manager - by Adam Faik

The AI Thinker

SubscribeSign in

How to hire an AI-native product manager<br>Rewrite the job description around real AI usage. Screen for the last thing they built. Watch them direct an AI live. Decide on judgment, with a fluency bar.

Adam Faik<br>Jul 20, 2026

Share

The headcount finally came through. You need a product manager, your recruiting partner needs a job description by Friday, and the process sitting in your ATS (the software your whole recruiting pipeline runs on) is the one you’ve run since 2023. Résumé screen, recruiter call, case-study interview, take-home, panel, offer. Every stage works the same way: the candidate produces something, and you grade it. A résumé. A structured answer. A polished deck. Look at it honestly and your hiring process is a machine for grading documents.<br>Here’s the problem: AI just made polished documents free. The tight résumé, the crisp case structure, the take-home that used to signal “this person is serious”: any candidate with Claude and an evening now produces all three. You’ve probably felt it already, reading applications that all sound suspiciously excellent. And it happened at the worst possible moment, right when you were asked to make your team AI-first and every open seat became a chance to hire the mindset. The signal collapsed at the exact moment the stakes went up.<br>So I went and read what the companies furthest into this shift actually did about it. I pulled the live PM job posts at Anthropic, Ramp, Notion, and Stripe, straight from their own job boards this week. I read the interview loops Sierra and Canva published, and the one candidates describe at Shopify. I read the fluency rubric Zapier now applies to every single hire. Different companies, different stages, one converging move. Stop grading the deliverable. Watch the candidate work. The bar isn’t “knows AI.” It’s “directs AI and catches it when it’s wrong.”<br>Here’s the whole arc in one picture.

The diagnosis. I’ll show you why every stage of your current process stopped measuring anything real.

The rebuild. Five moves, one per stage, with full requirements quoted from live postings and the interview questions from companies that already made them.

The calibration. You’ll see the data on how much AI to actually demand, and the walk-back that warns against overshooting.

The walkaway. One forwardable paragraph for leadership and your recruiter, plus a checklist to run on the req you have open.

By the end you’ll have a full replacement for the old process: job-description language you can borrow whole, two screening questions, a live interview format with a published AI policy, a work-sample design, and a decision rubric, all compressed into a closing checklist you can run this week. Your next PM hire stops being a coin flip on polish and becomes the clearest AI-first signal you send your team this year.<br>Let’s rebuild it, stage by stage.

Why your hiring loop went blind

Walk through the classic stages and name what each one actually measures. The résumé screen grades a document. The case interview grades a rehearsed structure, the kind a decade of candidates drilled from Cracking the PM Interview, McDowell and Bavaro’s 2013 prep book (”How many pizzas are delivered in Manhattan?”, “How do you design an alarm clock for the blind?”). The take-home grades another document, produced somewhere you can’t see. The panel grades a performance, and every stage grades some kind of output.<br>For years we told ourselves polish correlated with skill, that producing a crisp PRD required a crisp mind. The honest version is less flattering. Selection studies have long ranked résumé screens and unstructured interviews among the weakest predictors of actual job performance. The old process wasn’t a good instrument that AI broke. It was a weak instrument whose weakness AI made undeniable.<br>Picture the machine you’ve been running.

There’s a famous precedent for this kind of audit. Back in 2013, Google ran the numbers on its own famously clever interviews. Laszlo Bock, who ran People Operations there, went public with the verdict: brainteasers were “a complete waste of time” that “serve primarily to make the interviewer feel smart.” Google moved to structured interviews as a result. The lesson stings a little: a signal-free process can feel rigorous for years, because nobody checks. AI didn’t create the weakness. It removed the excuse for ignoring it.<br>You can watch the collapse happen in real interviews. In Nikhyl Singhal’s The Skip (Singhal ran product at Meta and Google), hiring manager Sam Stone observes that candidates who used AI to prep their case structure “will abandon the structure the moment Q&A starts, because they never internalized it.” In the same piece, product leader Mckenzie Lock shares the probe she used when screening at Netflix: when new information invalidates an assumption, “can you say ‘oh, that changes things’ and walk through updated...