Skip to content
Insights

Do You Need a Product Management Certificate?

by Adrienne Tan

Illustration of a hiker holding a map with a straight dotted route, walking a winding path towards a fork in the hills, with a certificate left behind on a signpost at the start of the trail

At a Glance

You don’t need a product management certificate to get a job in product or to get promoted. A certificate shows you have the knowledge, but it can’t show whether you can use it when the data is incomplete and stakeholders disagree. The best way to learn product is to do the work, and product work isn’t tied to a job title. Spotting a recurring customer complaint, gathering evidence and proposing a fix is product thinking. Training such as Brainmates’ Essentials of Product Management helps you see your existing experience as product work and tell that story, which is what hiring managers and leaders actually look for.

I get asked this a lot, usually by someone who is trying to break into product or trying to step up into a bigger product role. So my short and honest answer is no.

You don’t need an official product management certification to get a job in product, and you don’t need one to get promoted either.

That doesn’t mean that training and certifications are a waste of time. It means they’re not the only thing that gets you to your goal. I say that as someone whose own company gives one out. At Brainmates we award a certification for our Essentials of Product Management (EPM) course, and while it demonstrates your commitment to learning, it’s not required to get you a job in product. I’ll come back to what it is good for.

What a product management certificate actually proves

A product management certificate is a piece of paper that says you have the knowledge. You sat through the course, understood the concepts, and maybe passed an exam. That’s a good thing. Knowledge is good, and I’d never tell anyone to stop learning.

But a certificate can’t tell anyone whether you can use that knowledge when it counts. It doesn’t show whether you can sit with a messy problem where the data is incomplete, and the stakeholders disagree, and still work out what to do next. It doesn’t show whether you’ve ever had to make a decision and live with the consequences. That’s the part of product that matters, and it’s the part a certificate can’t test for.

Knowing isn’t the same as doing

There’s a gap between knowing something and doing it, and most of us live in that gap more than we’d like to admit. I see people who know exactly how a good discovery interview should run and they still walk out of one realising that they spent half of it pitching their own idea. The knowing was there. The doing needed practice.

That’s why I always say the best way to learn product is to actually do the work. Theory gives you a map, but you only learn the terrain by walking it, getting a bit lost, and figuring out what you’d do differently next time.

Product work isn’t tied to a job title

You’re probably thinking, “That’s all very well, Adrienne, but how am I meant to do product work if I’m not a product person?”

Here’s the thing. Product work isn’t attached to a job title. So many of the tasks people do every day could be classified as product work; they just don’t get called that.

Let’s say you work in a call centre. You’re listening to customer complaints all day, and after a while you notice the same complaint coming up again and again. You start to think there’s a real problem here that someone needs to solve. In that moment, you’ve taken raw customer data and treated it as a signal. That’s product thinking.

Now take it a step further. Start keeping a tally of how often it comes up. Think about why it might be happening and what might fix it. Then take it to your manager, or go and find the product manager who looks after that part of the business, and make yourself heard. You’ve just identified a problem, gathered evidence and proposed a solution. Nobody gave you a certificate for that, but it’s exactly the kind of thing a hiring manager wants to hear about.

Where EPM fits in

We give out the EPM certification because it demonstrates your commitment to learning, and that counts for something. You earn it through active participation, not attendance, so you’ve had to practise as well as listen. EPM alone won’t get you a job, but it does give you a boost.

The bigger benefit is the foundation it gives you. Once you understand how product work is framed, you can look back at your existing experience and see it differently. Suddenly the complaints you tracked in the call centre look like customer research, because that’s what they were. EPM helps you link those experiences together and showcase where you’ve picked up product experience without the title. The badge looks nice on LinkedIn, but being able to tell that story is what really helps.

If you’re going for a promotion

If you’re already in product and looking to move up, a certification can signal that you’re willing to go the extra mile to learn. I don’t want to dismiss that. It shows some initiative.

What’s far more powerful, though, is putting your hand up for extra projects. Take on the gnarly piece of work nobody else wants. Be curious about the parts of the business you don’t normally see, like how finance thinks about your product or what the sales team keeps hearing from customers. And help the people around you. When you demonstrate your capability like this, your leaders notice, because it’s exactly what they’ll need from you in the next role.

I don’t have one either

For what it’s worth, I don’t have a product management certificate. I’ve done plenty of courses over the years, on all sorts of topics, and I still love learning something new.

The habit I’ve built is that I don’t let a course finish when the course finishes. I always look for a way to put what I’ve learnt into practice, even in a small way, the very next week. Sometimes it works beautifully, and sometimes it falls flat, but either way I end up understanding the idea far better than I did sitting in the room.

What employers actually look for

When product leaders are hiring, they want to know how you think and what you’ve done. They’ll ask you to talk them through a problem you noticed, how you worked out whether it was worth solving, and what happened when you tried. They want to hear about the time you changed your mind because the evidence told you to. A certification might get a line on your CV, but those stories are what get you the job.

So if you’re weighing up whether to spend money on a certification, go ahead if you’ll enjoy it and it helps you learn. Just don’t stop there. Find a problem close to you, in whatever role you’re in today, and start doing something about it. That’s where you’ll really learn product, and it’s what people will remember when the next opportunity comes up.

Adrienne Tan
About the Author

Adrienne Tan

Co-Founder and CEO, Brainmates

Adrienne Tan is the CEO and Co-Founder of Brainmates and founder of Leading the Product, ANZ's biggest product community. With 20+ years in product, she's known for cutting through buzzwords, calling out the nonsense, and helping organisations make product thinking actually work, without the drama.

product leadership capability development product advisory product strategy product transformation

Take the next step

Judgement is a capability. Build it deliberately.

As AI accelerates delivery, strong product judgement becomes a competitive advantage. Learn how Brainmates helps organisations strengthen product management capability, decision-making, and strategic thinking.