Hire for the PM job that exists now

Most companies still hire product managers against a rubric built for a job that is going away. It rewards the person who runs the process: gathers the requirements, aligns the stakeholders, grooms the backlog, keeps a room full of specialists pointed the same direction. That was real work when the org was large and building was slow, because coordination was the constraint.

Building got cheap. The work moved to judgment, which is two things: deciding what is worth building, and knowing whether what shipped landed. Neither one is coordination.

Most companies still hire product managers against a rubric built for a job that is going away.

A team is also not only humans now. Agents do the read, the draft, and the check, which is most of what the coordinator used to carry between people. An agent can pull the background, write the first version of the spec, and check the build against it. It never makes the call. One decision, one owner, and a person holds it. Hire against the old rubric and you are selecting hard for the part that just got automated.

The gap shows up in the interview if you listen for it. Ask a candidate to walk through a launch, and notice who is in the story. If it is all "I aligned the teams and drove the roadmap and we shipped," you have a coordinator. Their value lived in an environment that is shrinking. Then ask the second question, which most candidates have never been asked: how did you know it landed? Anyone can ship now. The read is whether it moved anything. A candidate who can tell you which of their launches landed, which they are still watching, and which stalled is operating at the level the job requires, especially if they can name the numbers behind each verdict.

So screen for three things. First, a call they made when the answer was not obvious, including what would have changed their mind. Second, a shipped thing they can mark landed, watch, or stalled from measured numbers rather than a launch-day feeling. Third, how they work with agents: what they hand over, and what they refuse to hand over. The good answer to the third one is specific. They delegate the read, the draft, and the check. They keep the call, because they know a check is only as good as the material under it.

Screen for less process fluency, in other words, and more evidence of taste. Look for someone who will get their hands in the work. A person who can write the spec, sit with the engineer or the agent, look at the output, and tell you exactly what is wrong with it is worth more than one who has only ever run the room. That holds even when the second one has a bigger team on the resume.

There is a trap on the other side. Founders overcorrect, screen only for raw building speed, and end up with someone who ships beautifully and has no view on what deserves to ship. That is the same failure pointed the other way. The person you want holds both halves: the judgment to pick the right thing and the hands to help make it real. Rare, and that is the point.

Titles stopped predicting value here. The best candidate for this seat may have been called a founder, a design lead, or a staff engineer. What they share is that judgment sat with them, and they can show you the calls and the reads. You are not filling the old seat faster. You are hiring for the seat that exists now, and it asks for a different person than your rubric describes.