Most candidates ask this question expecting a number back. A pass rate, a difficulty rating, something they can compare against other exams they've already sat. That instinct makes sense. It's also the wrong question, and answering it the way most guides do tends to leave people either falsely reassured or needlessly frightened, neither of which helps anyone actually prepare.
Here's the first complication. PMI has never published an official pass rate for the PMP, and it hasn't since a single figure appeared back in 2005. What circulates now, the numbers you'll see quoted confidently across training sites, are industry estimates stitched together from provider data and candidate reporting. They vary widely depending on who's counting and what population they're counting. None of it is PMI's own figure, and treating any of it as gospel is a mistake I see candidates make constantly, usually right before they either over-relax or panic.
So if a clean percentage isn't the honest answer, what is? The exam is criterion-referenced rather than curved. There's no fixed pass mark published either, because the threshold is calibrated against the difficulty of the specific set of questions each candidate receives. What you get back afterwards isn't a score out of a hundred. It's a rating for each of the three domains, People, Process, and Business Environment, somewhere on a scale that runs from Needs Improvement through to Above Target. You need to land at Target or better across all three. A strong result in one domain doesn't rescue a weak one elsewhere. That structural detail alone changes how people should be studying, because it means you can't decide early on that one domain "isn't really your thing" and coast through it on the strength of the other two.
The exam itself, as of the July 2026 content update, runs to 180 questions across 240 minutes, with two optional ten-minute breaks splitting it into three sections. Ten of those questions are unscored pretest items PMI uses to calibrate future exams, and you cannot tell which ones they are, so every question has to be answered as though it counts. The format has broadened too. Alongside standard single-answer multiple choice, you'll now meet multiple-response items where you select a specified number of correct answers, matching questions, and questions built around a diagram or exhibit rather than plain text. None of that is designed to trip you up for its own sake. It's designed to stop rote memorisation from being a viable strategy on its own.
That's really where the difficulty sits. Not in obscure terminology or a vocabulary test buried inside a project management exam, but in the fact that nearly every question is situational. You're given a scenario, usually with several plausible-sounding responses, and asked to identify the best one rather than simply the correct one. That distinction trips up capable, experienced project managers more often than it trips up newer candidates, because experience sometimes teaches you the answer that worked on your last project rather than the answer PMI's blueprint considers correct in the abstract. I've sat across the table from delegates with a decade of delivery behind them who found the exam harder than expected for exactly that reason, and delegates two years into their career who found it more straightforward, because they hadn't yet built habits the exam would have to overwrite.
There's a workplace pattern worth naming here, because it shows up in study sessions constantly. A candidate will read a scenario about a stakeholder escalating a concern mid-sprint, and instinctively reach for whatever their own organisation actually does in that situation, which might involve a workaround, a favour called in, or simply skipping a step because everyone trusts each other. The exam isn't testing what your organisation does. It's testing what the standard says a competent practitioner should do when the process is followed properly. Unlearning that gap, between how you actually work and how the exam expects you to reason, is often the real preparation task, and it's rarely the one candidates think they're signing up for when they buy a study guide.
Roughly half the content now sits in agile and hybrid territory rather than pure predictive delivery, which catches out candidates whose experience is entirely plan-driven. That's not a small adjustment to memorise on top of what you already know. It's a genuinely different reasoning pattern, iterative and adaptive rather than sequential, and treating it as a short annexe to traditional project management is how well-prepared people still end up surprised on the day.
So is it hard? Yes, but specifically hard, in a way that responds to the right kind of preparation rather than more of it. The candidates who struggle tend to have read plenty and practised too little under realistic, timed conditions. The candidates who do well have usually spent less time reading and more time being wrong, out loud, against a clock, until the reasoning the exam wants starts to feel like their own. That's a learnable skill, not a talent some people simply have. If you want to talk through where your own preparation genuinely stands, rather than guess at it, 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.