How to become a product manager with no experience

01What hiring managers are really checking

A product manager's job is to make decisions about what to build, with incomplete information, in a way other people will accept. So the only thing an interviewer can really assess is whether you have made such decisions and how you made them. A degree says you can study. A certificate says you can finish a course. Neither shows a decision.

This is why people with unusual backgrounds get hired into product roles all the time: support leads, teachers, analysts, engineers, founders of things that failed. They have a story about a problem, evidence, a call they made, and what happened. That story is the interview.

02Build decisions, not a résumé

If the job is decisions, the preparation is making some. You do not need permission, a title or a company. You need a product you can observe closely. That might be an app whose reviews are public, a tool your current team uses and complains about, a small business you can talk to, or something of your own.

The sequence is always the same. Read the feedback and keep the exact words. Find a problem that shows up repeatedly and attach a number to it. Write one page that states the problem, the evidence, and what you would do. If you can, build the smallest version of the fix, put it on a real URL, and get five people to use it. Then write down what happened, including when it did not work.

Each loop takes a few weeks of evenings. Three loops is a portfolio. It is also the content of every interview you will ever have.

03Learn by doing the job, not by reading about it

The product management content industry is enormous, and most of it is frameworks: prioritisation matrices, canvases, five-step processes. Frameworks are fine as vocabulary and useless as preparation, because the hard part of the job is never the framework. It is noticing that two reviews describe different bugs, or that the number everyone celebrates has a counter metric nobody tracks, or that the engineer's estimate was for a different scope than the one on the page.

Those are skills of attention, and attention is trained by doing the task with real material and getting feedback. This is the entire design principle behind PMcademy: every lesson is a scene inside a company, with real-looking data, and ends with something you build. It is free, all six levels, because the thing that gets you hired is the work, not the receipt.

04Use AI the way a working PM does

The job now involves a model from the first morning. A good product manager uses it to extract fields from five hundred reviews, draft the first ugly version of a spec, generate test cases for an edge the engineer mentioned, or build a working prototype of a flow before design has time to look at it. A poor one asks it to summarise and pastes the paragraph into a document.

Learn the move and the trap for each use. The move is extraction into a table you can audit. The trap is a fluent summary that cannot be checked. Interviewers increasingly ask how you use these tools, and "I asked it to write my PRD" is the wrong answer.

05Get the first conversation

With three written loops you have something to send. Do not apply cold with a résumé that says "aspiring product manager". Send the one-page memo from your best loop to a product lead at a company whose product you studied, with two sentences: here is a problem I found in your product, here is what I would do, happy to talk. Some will ignore it. Some will reply, because people who care about a product like hearing from someone who read its reviews more carefully than they did.

Associate product manager roles, internal moves from support or analytics, and small companies with a founder doing product badly are the three most common doors. All three open to the same key: a decision you made, written down, with evidence anyone can check.