Project Management Institute
PMP — What Interviewers Actually Ask About It
The PMP gets your CV read. Then it gets you a specific interview, and it is not the friendly one.
Here is the mechanism, and it is the part candidates skip when they prepare. You cannot sit the exam without having already led projects. Under the eligibility rules that take effect with the July 2026 exam, PMI runs four paths, and the months required fall as the education rises: 60 months of leading projects behind upper-secondary school, 48 months behind an associate-level or advanced technical qualification, 36 months behind a bachelor's degree, and 24 months behind a degree from a programme accredited by PMI's own Global Accreditation Center. The experience has to be non-overlapping and accrued within the previous ten years, and every path also carries 35 hours of project management training. So by construction, every PMP holder walked in with two to five years of leading projects behind them. The certificate did not create that record; it filed it. Which means a hiring manager cannot learn anything about your delivery ability from the three letters, and the good ones know that, so they spend the interview trying to find out whether the experience underneath is real, thin, or borrowed from a team you sat next to.
That is the whole shape of a PMP interview. The credential moves you from the pile to the room. Everything after that is somebody testing the claim it implies. This page is about those questions — not about the exam, which we do not cover, and which is not what anyone is going to ask you about.
Who requires it
Read the two columns together. The left is who genuinely gates on it. The right is the half this genre leaves out.
No law does. That is the honest first sentence, and it separates the PMP from a licence. The PMP is a voluntary certification issued by a professional membership association, not a permit issued by a regulator: PMI licenses nobody, and holding the certificate confers no legal right to do anything. Take the scope of that sentence literally — we did not read every jurisdiction's statute book, and we found no regulator that gates project management the way the Saudi Council of Engineers gates engineering. The US Bureau of Labor Statistics is explicit for project management specialists: certification is "not always required," though it "demonstrates competency to prospective clients and employers."
What actually gates on it is commercial rather than legal, and it is real:
- Employers, as a screening filter. Senior project and programme postings carry PMP in the required or preferred block. We did not measure how many, and you should not take a number from anyone who has not — but you can read your own market's postings in ten minutes, and that is the filter your CV meets first.
- Bid and framework requirements. In proposal-driven work, client organizations and prime contractors ask for named project managers and their credentials in the submission itself. That is why HR wants your certificate number before a technical manager has read your CV. We could not source a public tender that awards points for a named certification, so treat the scoring as market practice we did not verify rather than a rule you can quote back at anyone.
- Internal promotion ladders. A PMO can make it a condition of a grade — which is a policy, not a law, and a policy can be waived.
The money question, answered with the actual numbers and the actual caveat. PMI's Earning Power: Project Management Salary Survey, 14th edition, published 13 November 2025, reports that PMP holders earn 17% higher median salaries than non-certified professionals across the 21 countries surveyed. In the US, certified respondents reported a median of $135,000 against $109,157 for the non-certified — a difference of nearly 24%. Tenure compounds it: US respondents certified more than ten years reported a median of $173,000, against $123,000 for those certified under five. The survey drew on 14,628 project professionals across 21 countries, fielded 9 March to 19 April 2025.
For the whole occupation rather than the certified slice, BLS reports a median wage of $102,320 for project management specialists as of May 2025, 1,094,300 jobs, growth of 7% from 2025 to 2035, and about 76,500 openings a year over the decade.
Verified: — scope: PMI's 14th-edition salary survey figures and methodology from PMI's own press release of 13 November 2025, read in full; BLS Occupational Outlook Handbook figures for project management specialists read directly from bls.gov; the four eligibility paths, the ten-year window and the 35 training hours from PMI's PMP Examination Content Outline — July 2026, read in full; renewal, suspension and registry rules from PMI's own certification and CCR handbooks, read in full. Not verified: any count of PMP holders worldwide (reported figures conflict and none traced to PMI); any claim that a specific employer or tender mandates the PMP; and any measure of how many postings ask for it.
Certification requirements and survey figures are re-issued periodically. Check PMI directly before relying on a number here.
What the certification does not do
- It does not license you. Nothing about the PMP grants a legal right to do anything. Compare the Saudi Council of Engineers accreditation, whose force comes from a royal decree: that is a licence, this is a credential, and the distinction decides which arguments work in a negotiation.
- It cannot be read as the cause of that salary gap, and PMI's survey cannot tell you how much of it it caused. Read the eligibility rule again: depending on your education you needed between two and five years of leading projects to sit the exam. So the certified population is, by definition, more experienced than the uncertified one — and the survey is self-reported, by PMI, about PMI's own credential. That is not a reason to disbelieve the 17%. It is a reason not to read it as "the exam pays 17%," which is how a page selling exam prep will read it to you.
- It is not the reference qualification everywhere. The UK government's mandated standard for its own project delivery, GovS 002, names no certification at all — it points at the APM and PMI bodies of knowledge and leaves the qualification to the department. PRINCE2 and IPMA are the alternatives you will meet in markets that work to other bodies of knowledge. We could not source market share for any of them, and neither can the pages that sell you one, so do the only reliable thing: read the postings in the market you are actually applying to before you pay for a credential on the strength of its reputation.
- It does not survive neglect. Sixty PDUs every three years, at least 35 of them in the education category and up to 25 from giving back. Miss the cycle and the credential goes to suspended for a year — during which you may not refer to yourself as a certification holder or use the designation — and then expires, at which point you reapply, pay again and sit the exam again.
- It is checkable, and the check runs both ways. PMI runs a free public certification registry: anyone can search active holders by name and country, no login. So an inflated claim on a CV is not a risk here, it is an outcome. The other direction matters too, and the marketing leaves it out — holders can ask to be removed from the registry, so a name that is absent from it is not evidence that the person is uncertified.
- It does not answer the interview. Holding it does not demonstrate that you can describe a schedule you built or a scope decision you lost, and that is precisely what the room will ask you to do. The credential raises the expected floor of your answers, which is a cost as well as a benefit.
Before you dial in — five things to have ready
Not the five most asked. The five that decide how the rest of the call goes.
- The date you certified and the date your cycle renews.Both, unprompted.
- Which experience you claimed on the application— the specific projects, because the months of leading projects you entered are a claim you already made in writing and can be asked to describe.
- One project run predictively and one run in an agile or hybrid way,because the current PMP spans both and an interviewer who knows that will check.
- A number you own.Budget, headcount, duration, variance. Not the programme's number — yours.
- The honest sentence about why you took it.Panels ask, and "for career progression" is a non-answer that costs you nothing and gains you nothing.
A. The credential itself
All levels
Fast, factual, and placed early. They are administrative in tone and diagnostic in effect — an evasive answer to a date question colours everything after it.
When did you get your PMP, and is it current?Show the answer guide
Two dates, one sentence. Certified in a given month and year, current cycle running to a given date. Then stop.
Which eligibility path did you qualify under?Show the answer guide
There are four, keyed to education: 60 months of leading projects behind upper-secondary school, 48 behind an associate-level or advanced technical qualification, 36 behind a bachelor's degree, 24 behind a GAC-accredited degree. Say which one was yours, and say what those months actually were — that is the part the question is reaching for.
How many PDUs are you into this cycle, and on what?Show the answer guide
Sounds like small talk. It is a discipline check, and it is also a taste check: the PMP who spent 35 education PDUs on things adjacent to what he does is more interesting than the one who bought a bundle. Name two real ones.
Have you ever let it lapse?Show the answer guide
If yes, say so and say what happened. Lapsing is a scheduling failure, not a character one, and a candidate who says "I let it go to suspended in 2023 while I was on a night-shift commissioning programme and reinstated it that August" sounds like a person. A candidate who is vague about it sounds like something else.
Do you hold anything alongside it?Show the answer guide
PRINCE2, a Scrum credential, a Six Sigma belt, a sector safety card. Say what you hold and, in one clause, why the combination fits the work you do. Collecting certificates is a pattern interviewers notice, and noticing it is not the same as being impressed by it.
B. The verification set — where the certificate stops helping
Mid – senior
This is the heart of a PMP interview and the reason the credential is a mixed blessing. The letters raise the expected quality of these answers, so a generic response from a certified candidate lands worse than the same response from an uncertified one. Everything here wants a specific project, a specific decision, and a specific consequence.
Walk me through a project you ran end to end. Not the biggest — the one you own.Show the answer guide
The question this section opens with, and the one people waste on scale.
Give the frame in two sentences — what, for whom, how long, how much, how many people — then spend the rest on decisions you personally made. The interviewer is listening for first-person verbs attached to consequences. "We aligned stakeholders" tells him nothing. "I moved the integration test two sprints earlier and lost the contingency I'd been holding for UAT" tells him what kind of project manager you are.
If your biggest project is one where you were one of four PMs, shrink the frame and own your quarter of it. A claim on a £40m programme invites a scale of scrutiny that "I ran the data migration workstream inside it, and here is what I got wrong in the first cutover rehearsal" does not.
What was your baseline, and how far off it did you finish?Show the answer guide
The question that separates people who ran projects from people who attended them.
Have the numbers. Planned versus actual on cost and schedule, and — the part candidates skip — what you did when the gap appeared and who you told. If you finished off baseline, say the number. Finishing off baseline is not what is being graded; whether you knew early and escalated, or knew late and hoped, is.
Do not say "we delivered on time and on budget" about every project you have ever run. It reads as untrue, and it invites the follow-up "on which one did you not?"
Tell me about a project that failed.Show the answer guide
Pick a real one with a real cost. Cancelled, descoped, overrun, or delivered and then not used — the last is the honest kind, and the one it takes nerve to offer.
The structure that works: what the decision was that made it fail, when it became visible, what you did between those two moments, and what you changed afterward. Candidates who blame a stakeholder lose the question. Candidates who take total blame lose it too, more slowly, because it reads as performance.
How do you build a schedule?Show the answer guide
Say how you actually do it, including the unglamorous parts: where the estimates come from, who owns each duration, how you get people to commit to a date they will honour, what your critical path is doing, and how much float you had. Naming a tool is not an answer. Naming who gave you the durations is.
How do you handle a change request mid-flight?Show the answer guide
Not "we assess the impact." Describe the actual protection: what has to be in writing, who prices the cost and schedule impact, who authorizes it, and what you do when work starts before authorization arrives — because it does.
The sentence that lands is that you do not let a change be built on a conversation.
What's in your risk register right now, and when did you last change it?Show the answer guide
A brilliant one-liner of a question, because a dead risk register is the signature of a project nobody is really managing. Name two live risks and the date you last reviewed them.
How do you report status to someone who doesn't want to read it?Show the answer guide
They are asking whether your reporting is a ritual or a tool. One page, three things, and the bad news in the first paragraph rather than the appendix.
The estimating clusterShow the answer guide
Three questions that rotate and are all the same question underneath: how do you estimate when you have never done this before · what do you do when a team gives you an estimate you think is wrong · how do you handle being asked for a date before you have a plan.
Prepare them as one topic, because the through-line is always the same: you name the confidence you actually have, you say what would raise it, and you refuse to convert a guess into a commitment silently. The single strongest answer to all three is a range with the assumptions attached, and a date by which the range narrows.
The bad answer to all three is a number produced to make the room comfortable. Interviewers have been burned by that number.
C. Predictive, agile, and the hybrid reality
Mid level
The current PMP spans predictive, agile and hybrid approaches, and any interviewer who knows that will check whether you span them or just passed a question set about them. This section is where a PMP out of a long waterfall background is most exposed.
Which of your projects ran predictively and which didn't?Show the answer guide
Have one of each ready. If you have genuinely never worked in an agile delivery, say so and say what you have seen from outside it — that is far better than a rehearsed vocabulary that collapses on the second question.
What actually changes for you as the PM in an agile delivery?Show the answer guide
The honest answer is about what you stop doing. You are not producing the plan; you are protecting the conditions in which the team produces it — dependencies, funding, access to decision-makers, and the difficult conversation with a sponsor who wants a date.
How do you report progress to a governance board that wants a Gantt chart, on a project that doesn't have one?Show the answer guide
The best hybrid question there is, and it is a real problem rather than a theoretical one. Describe the translation you actually do: what you show, what you refuse to fabricate, and how you handle the request for a date range you cannot honestly narrow yet.
What's your view on scaling frameworks?Show the answer guide
They want an opinion, so have one. "Both approaches have merit" fails the question. Say what you have seen work, at what size, and what it cost in overhead.
Where does your PMO help and where does it get in the way?Show the answer guide
Asked by the people who run the PMO, which makes flattery obvious. Say something true about a control that did not earn its cost, and something true about one that saved you.
D. Stakeholders, conflict and the sponsor
Mid – senior
Panels use this section as the tiebreaker between technically similar candidates, and it is where the PMP's "People" emphasis meets reality. One specific person, one specific disagreement, one outcome — including the ones you lost.
Tell me about a disagreement with a sponsor.Show the answer guide
The failure mode is spending the answer proving you were right.
A weak version
The sponsor kept adding scope without extending the deadline. I raised it repeatedly and eventually escalated to the steering committee, who agreed with me and the timeline was extended.
That is a complaint with a happy ending. It has no method in it, and it tells the panel your first instrument in a disagreement is escalation.
A stronger version
Our sponsor wanted a supplier portal in the first release; my delivery lead said it would cost us the payments integration. Rather than argue it in the steering meeting, I built two options on one page — release one with the portal and payments in March, or without it and payments in January — and put the revenue difference on both. She picked the January date in about four minutes, because it turned out nobody had ever shown her what the portal was costing. I also learned that I'd been describing this as a capacity problem for six weeks when it was a money problem, which is why nobody had listened.
Same disagreement, better candidate. The second one converted a position into a decision the sponsor could make, priced it in her currency, and volunteered his own error at the end. That last part is what makes it credible — and it is exactly the part candidates edit out.
How do you handle a team member who isn't delivering and doesn't report to you?Show the answer guide
The defining structural problem of the job and a question you should not be improvising. Describe the sequence you use, and be honest about the point at which you go to their line manager and what you say when you get there.
Who was the hardest stakeholder you've managed, and are they still speaking to you?Show the answer guide
The second half is the real question. A candidate who has only ever "won" with difficult stakeholders is describing a job he has not had.
How do you say no to a customer?Show the answer guide
One line of philosophy, then an example. The example is the answer.
E. Questions to ask them
- What's the portfolio right now, and where does this project sit in it?
- Who's the sponsor, and how often will I actually get them?
- What does the PMO require from me every week, and what does it give back?
- What's the last project here that went badly, and what changed afterward?
The last one is the highest-yield question on the list. The answer tells you whether this organization learns, and how it treats a project manager on a bad month — which is the only version of the job that is hard.
What this changes on your CV
The PMP earns its place in exactly two positions, and everywhere else it is clutter.
Beside your name in the header, as post-nominals — `Full Name, PMP` — because that is how a screener recognizes it in one pass and how a parser matches it. And once in a certifications line with the issuing body and the currency date. Twice, total.
Two specifics that matter more than they should:
- Write both the acronym and the full name somewhere on the page — "Project Management Professional (PMP), Project Management Institute." Postings use both strings and the software is matching text, not meaning.
- Give the currency date, not the award date alone. "PMP, PMI — certified 2019, current to 2028" is a fact a recruiter can act on. "PMP, 2019" invites the assumption that it lapsed, and some screeners will make it.
The thing not to do is build a certifications section that outweighs your delivery record. A CV where the credentials block is longer than the description of any single project reads as someone who has studied the job rather than done it, and that reading is hard to undo once it forms.
And be exact, because you can be checked. PMI's public registry returns active or inactive status to anyone who searches it, free and without an account. It is not a complete list — holders may opt out of appearing in it — but that cuts only one way for you: an absent name proves nothing about someone else, while a claim of yours that the registry contradicts is finished.
Roles this opens
Project manager — the directly connected role page, where the interview itself is covered rather than the credential.
Civil engineer — where PMP turns up beside chartership on construction and infrastructure programmes rather than instead of it.
Ordering note
The order here is editorial judgement about what decides these interviews, not a frequency measurement, and no question on this page carries an employer attribution — no source we could reach records what candidates are actually asked about the PMP by named employers.
The sequence follows the interview itself: the credential questions come first because they come first in the room and take four minutes; the verification set is second and longest because it is where the decision is made; approach and stakeholder questions follow because they arrive later and are where a close decision gets settled. The salary and demand figures in section 3 are the exception to the judgement rule — those are measured, they are cited to PMI's and BLS's own published numbers, and the caveat about what PMI's survey can and cannot show is stated on the page rather than buried here.
Sources
Everything consulted for this page, named in plain text.
- Project Management Institute — press release, 13 November 2025, on the 14th edition of Earning Power: Project Management Salary Survey — read 5 September 2026
- US Bureau of Labor Statistics — Occupational Outlook Handbook, Project Management Specialists — read 5 September 2026
- Project Management Institute — PMP Examination Content Outline, July 2026 (©2026 PMI) — read 5 September 2026
- Project Management Institute — Certification Handbook (revised June 2026) and Continuing Certification Requirements (CCR) Handbook (©2026 PMI) — read 5 September 2026
- UK Cabinet Office — Government Functional Standard GovS 002: Project delivery (published 1 September 2025, last modified 29 March 2026) — read 5 September 2026