How do you become a product manager without prior PM experience?

The route that works

Almost nobody gets hired into a first PM role from outside. Companies hire for the role internally because the risk is lower — they've seen your judgment.

So the practical path is to be inside a company with product teams, in any function, and start doing the work. Take a problem nobody owns. Talk to the customers who have it. Write up what you found and what you'd do. Get one thing shipped and measure whether it worked.

That artefact — a decision, an argument, an outcome — is what an interview is trying to find out about, and it doesn't require a title.

What each background carries

Engineers bring feasibility judgment and credibility with the team; the gap is usually customer contact and comfort with ambiguous, non-technical trade-offs.

Designers bring user empathy and craft; the gap is typically commercial reasoning and data.

Support and customer success bring the deepest knowledge of what customers actually struggle with, which is enormously undervalued; the gap is strategy and technical fluency.

Analysts bring rigour; the gap is qualitative research and the tolerance for deciding without a clean number.

Name your gap honestly and close it visibly. That's a better interview answer than pretending the gap isn't there.

In the interview

You'll be asked how you'd improve some product, and the answer that fails is a list of features. The answer that works establishes who the user is, what problem you're solving, why it matters, how you'd know it worked, and what you'd deliberately not do.

Superhuman's product process is a useful thing to have studied for this reason: it's a public example of someone deciding what evidence would change their mind, then acting on it. That's the mode of thinking the interview is looking for — not familiarity with a framework, but a habit of turning vague questions into answerable ones.