PMP Eligibility Requirements: Do You Qualify?

Search "PMP eligibility requirements" and you'll get three different answers in the first page of results. One site says 36 months of experience with a degree, 60 without. Another says three years, or four, or five, depending on qualification. A third still quotes the old 4,500 and 7,500 hour figures PMI retired back in 2021. If you're trying to work out whether you actually qualify, that's not reassuring. It's the kind of inconsistency that makes people assume the safest answer is the strictest one, and quietly rule themselves out.

That instinct is understandable. Nobody wants to spend three months building an application only to have PMI reject it. So candidates tend to gravitate towards whichever version of the rules sounds hardest, on the theory that if they clear that bar, they're safe whatever the real bar turns out to be. It's a sensible instinct applied to the wrong problem, because the rules genuinely have moved more than once, and most of the content sitting at the top of a search result was written to describe an earlier version of them.

The first shift happened in 2021, when PMI moved from an hours-based experience model to a months-based one. Plenty of training providers updated their pages. Plenty didn't, or updated the headline number and left the surrounding explanation half-changed, which is how you end up with a page that quotes 4,500 hours in one paragraph and 36 months in the next as though they're two separate requirements rather than the same one, twice. The second shift has been quieter still. For a long time, PMI recognised two education tiers: a four-year degree, or everything else. That's the version most blog content still describes, usually paired with an eight-year experience window.

Neither of those is quite what PMI's own eligibility page currently says.

There are four routes in, not two, and the education level you hold changes how much experience you need rather than whether you qualify at all. A high school diploma, GED, or equivalent secondary qualification gets you in with five years of experience leading projects. An associate's degree or vocational trade diploma drops that to four years. A bachelor's degree or higher brings it down to three. And a degree from a PMI-accredited GAC programme needs just two years. That associate's-degree tier in particular barely gets a mention on most of the pages currently ranking for this topic, which means a real slice of candidates are assuming they need a bachelor's degree or five years of graft, when the qualification sitting in their drawer already buys them a shorter path.

The experience window has moved too. It's ten years now, not eight. That matters more than it sounds. A candidate who led a genuine project nine years ago, then spent a stretch in a role without that kind of responsibility, may have written that year off entirely under the old rule. Under the current one, it still counts.

A trainer we work alongside had this conversation with a delegate a few months back. She'd spent a weekend working through her application using a checklist she'd found online, concluded she was fourteen months short, and had more or less talked herself out of applying this year. Walking through PMI's actual current criteria with her took about twenty minutes. She had an associate's-level qualification the checklist hadn't accounted for at all, and two years of project leadership sitting just inside the ten-year window that her original eight-year tally had quietly excluded. She wasn't short. She'd been measuring herself against a version of the exam entry criteria that didn't exist any more.

The experience requirement itself is worth being precise about too, because "leading projects" doesn't mean you needed the job title Project Manager on your contract. PMI is looking for evidence that you took responsibility for planning, decisions, delivery and outcomes on something with a defined start, end and result, whether that sat inside a formal PMO or happened because you were the person who ended up running the thing. Coordinating a system migration as a technical lead counts. Running a product launch as a marketing manager counts. What doesn't count is time spent contributing to someone else's project without owning any of those decisions yourself, and PMI does ask you to avoid double-counting months where two projects overlapped, so tally carefully rather than assuming every month you were busy adds a month to the total.

Alongside the experience requirement sits the 35-hour training requirement, which hasn't moved and isn't going anywhere. You can satisfy it through a formal PMP exam prep course, a PMI Authorized Training Partner, a GAC programme, an active CAPM certification, or third-party training that meets the same bar. It's worth knowing that PMI does audit a percentage of applications at random, asking for supporting documentation and a signed verification from a supervisor or project sponsor for each project you've claimed. That's a routine check, not a sign your application looked suspicious, but it's a reasonable argument for logging your project history properly as you go rather than trying to reconstruct it from memory the week before you apply.

None of this got harder. If anything, the current criteria are more forgiving than the version most people are checking themselves against, wider tiers, a longer window, a training requirement with several ways to meet it. The actual risk isn't that you fall short of what PMI is asking for. It's that you rule yourself out against a set of numbers nobody's using any more. Worth checking the current criteria properly, on their own terms, before you decide either way, and if you want a second pair of eyes on how your own experience actually maps against them, get in touch about your PMP training options.

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.