Do You Need a PMP to Be a Project Manager?

Nobody asks you for a licence before you run a project. There is no regulator checking your credentials before a sponsor hands you a budget and a deadline. Most people who end up managing projects arrive there sideways, from operations, from engineering, from being the person who was organised enough to keep a spreadsheet nobody else wanted to own. They learn the job by doing it, and a fair number of them do it well for years without a single letter after their name.

And yet the question keeps surfacing, usually at a moment that isn't really about the certification at all. A job advert lists PMP as "essential" for a role that sounds exactly like the one you're already doing. A recruiter mentions, almost as an aside, that the client "prefers PMP-certified candidates." A colleague with less delivery experience than you gets shortlisted and you don't. None of this tells you whether PMP is required in any formal sense. It tells you something is filtering candidates before a human being reads your CV properly, and you're trying to work out whether that filter is arbitrary or real.

It helps to separate two different questions that tend to get collapsed into one. The first is whether PMP is a prerequisite for doing project management work. It isn't, not in the way a law degree is a prerequisite for practising law. There is no governing body that will stop you leading a project without it, and organisations hire and promote uncertified project managers constantly, often into senior roles. The second question is whether PMP changes what happens to your application before anyone assesses your actual capability, and that is where the honest answer gets less comfortable. In a lot of hiring processes, especially at larger organisations and especially in the United States, PMP has become a proxy that recruiters and applicant tracking systems use to shortcut a judgement they don't have time to make properly. It isn't testing whether you can run a project. It's testing whether you cleared a bar that someone decided was easier to check than your actual track record.

That distinction matters because it changes what you're actually solving for. If PMP were a skills gap, the fix would be obvious: get the skills. But for a lot of experienced project managers, the gap isn't skill. It's legibility. You already know how to build a schedule, manage a risk register, handle a stakeholder who won't engage, and recover a project that's slipping. What you don't have is a fast, external way to prove that to someone who has never worked with you and has forty other CVs to get through before lunch. PMI's own eligibility structure makes this more visible than most competitors: to sit the exam, you need three to five years of documented experience actually leading projects, depending on your education level, plus thirty-five hours of formal project management training. The credential isn't awarded for knowledge alone. It's awarded on top of experience you already have to hold before you're allowed to apply. In that sense, PMP doesn't create your competence. It packages competence you already have into a format a stranger can verify in under a minute.

This is where the picture becomes less binary than "worth it" or "waste of time." Consider two people with genuinely similar delivery experience. One has spent the last six years running projects inside a single organisation, well regarded internally, never needing to compete against strangers for a role because promotion happened from within. The other has spent the same six years moving between employers, each time needing to prove capability from scratch to people who had no prior context on their work. The first person may never feel the absence of PMP, because their track record travels with them through relationships, not paperwork. The second person is far more likely to hit doors that simply don't open, not because they're less capable, but because nobody screening their application has any way to know that yet. Certification does the most work precisely where reputation can't follow you, which is why its value looks so different depending on which kind of career you're actually living.

There's a version of this conversation that turns moralistic, treating the certification as either a badge of seriousness or a hollow tick-box exercise depending on which side someone has landed on. Neither framing is particularly useful. PMP is a tool that solves a specific, real problem, which is that hiring is expensive and imperfect and organisations look for cheap signals wherever they can find them. If you're in a role or a market where that signal genuinely gates opportunities you want, ignoring it on principle costs you more than it proves. If you're already past that gate, through internal reputation, a specialised niche, or a market where employers hire on demonstrated delivery rather than acronyms, the certification adds less than the study time it costs. The question was never really "do you need a PMP." It's closer to: where exactly does your career currently rely on a stranger's fast judgement of you, and is that reliance increasing or shrinking from here.

That's a harder question to sit with than a yes or no, but it's also the one that actually points somewhere. If you can answer it honestly, get in touch about your PMP training options and we can talk through whether it changes anything for where you're headed next.

Andre Malowney is a project management trainer accredited across PMI, APMG, APM and PeopleCert frameworks, working with both traditional plan-driven practitioners and Agile delivery teams. Find him on LinkedIn: www.linkedin.com/in/andremalowney.