PMP Interview Questions: 30 Behavioural + Technical Q&As

I have sat on both sides of dozens of project manager interviews, and the PMP credential changes the bar in interesting ways. When I see PMP after a candidate’s name, my expectations shift. I expect more structured answers. I expect them to talk about stakeholders without prompting. I expect them to know what an RACI is without having to explain it. And I am less forgiving when they fluff a question about risk because they should know better.

In this article I am going to walk through 30 PMP interview questions, split between behavioural and technical, that I have either asked or been asked. For each one I will share what interviewers are really probing for, what a strong answer looks like in STAR format where appropriate, and what red flags candidates tend to signal without realising. By the end you will have a structured way to prepare for your next interview, whether you are aiming for a senior project manager role, a programme manager step-up, or a PMO leadership position.

A non-PMP project manager interview tends to be lighter on terminology and heavier on personality fit. A PMP interview, particularly for senior roles, assumes you know the vocabulary and tests whether you can apply it. Hiring managers want to see if you can talk about a project the way the PMBOK frames one: through processes, knowledge areas, performance domains, and tailoring decisions.

That said, do not over-jargon. I have rejected candidates who answered every question with textbook definitions but could not point to a single real example. The PMP gives you a language, but the interview is about the work you have actually done.

The interviewer is asking themselves one core question: would I trust this person with a real budget, a real team, and a real outcome? Every answer should reinforce that yes, they can.

The format I recommend is hybrid: behavioural questions answered with STAR-format examples, technical questions answered with a brief framework followed by a real-world example. Both kinds of answers should be tight, structured, and concrete.

Almost every behavioural question deserves a STAR answer:

• Situation: The context in two or three sentences. Where were you, what was the project, what was at stake?
• Task: What were you specifically responsible for?
• Action: What did you do? This is where most candidates underspend. Be specific about the steps you personally took.
• Result: What was the measurable outcome? Numbers help.

A common mistake is spending 80 percent of the time on situation and only 20 percent on action. Flip that ratio. The interviewer wants to hear how you actually behaved, not just the background of the project.

Another tip: prepare 6 to 8 strong STAR stories that you can flex to answer 20+ different questions. Stories about a major delivery, a recovery from failure, a difficult stakeholder, an innovative solution, and a team conflict will cover most of what you get asked.

Q1: Tell me about a time you had to lead a team without formal authority.

What they probe: Your ability to use influence, persuasion, and credibility instead of position power. This matters because most project managers do not have direct authority over their team members.

Strong answer structure: Describe a cross-functional initiative where you were leading senior people from other departments. Talk about how you established credibility (through expertise, by listening first, by sharing wins), how you built shared purpose, and how you managed accountability through visibility rather than hierarchy.

I once led a regulatory remediation across four business units. None of the people reporting into the workstream actually reported to me. I built a weekly steering committee, made commitments visible across the group, and quietly gave credit upward. By month four, the workstream leads were holding each other accountable without me having to nudge.

Q2: Describe a time you motivated a disengaged team member.

Probe: Empathy, situational leadership, and your read on what drives people. The best answers acknowledge that motivation is individual, not generic.

Q3: How have you developed someone on your team?

Probe: Whether you see your role as just delivering projects or also growing people. Senior PMP roles increasingly weigh this.

Q4: Tell me about a conflict you had with a senior stakeholder.

What they probe: Whether you can disagree professionally without becoming political, and whether you have the spine to push back when needed. Avoiding the conflict question entirely is a red flag.

A strong answer acknowledges the disagreement honestly, describes how you separated the issue from the person, and shows that you went to data rather than escalation as your first move. End with what you learned about that stakeholder’s underlying interests.

Q5: Describe a time two team members were in conflict and you had to mediate.

Probe: Your conflict resolution approach. The PMI playbook is collaborate, compromise, smooth, force, withdraw. Most interviewers want to hear collaborate or compromise, not force or withdraw.

Q6: Tell me about a time you had to deliver bad news to an executive sponsor.

Probe: Communication discipline under pressure. Did you bring options or just problems? Did you frame impact in business terms?

The strongest answer I ever heard to this question: “I scheduled a 20 minute call, opened with the issue in one sentence, presented three options with trade-offs, recommended one, and asked for a decision by end of day. He thanked me for not surprising him in the steering committee.”

Q7: Tell me about a time scope changed dramatically mid-project.

Probe: Whether you handle change formally (change requests, impact analysis, board approval) or chaotically. Interviewers like to hear about a working change control process.

Q8: Describe a time a stakeholder asked for something out of scope and you had to say no.

Probe: Your ability to protect scope without alienating the requestor. Strong answers include offering alternative paths, parking the request for a future phase, or quantifying the impact transparently.

Q9: Tell me about a project where requirements were ambiguous at the start.

Probe: Comfort with uncertainty and your discovery techniques. Mention prototyping, workshops, interviews, MoSCoW prioritisation, and rolling wave planning.

Q10: Tell me about a project that missed its deadline.

This is the question that separates self-aware candidates from defensive ones. Everyone has missed a deadline. Pretending otherwise is itself the red flag.

What works: Acknowledge it cleanly, describe what you saw coming, when you raised the alarm, what mitigations you tried, and what you learned. Do not blame the team or the sponsor by name. Take ownership of the decisions you controlled.

Q11: Describe a project that failed outright.

Probe: Whether you can talk honestly about failure without becoming maudlin or evasive. The best answers are matter-of-fact and end with concrete lessons you applied later.

Q12: Tell me about a risk you missed that materialised.

Probe: Your risk humility. We all miss risks. The interviewer wants to know how you adjusted your risk practice afterward.

I once missed a vendor’s dependency on a single key engineer who left mid-project. After that, I started asking vendors for their bus factor explicitly and made key-person risk a standing item in my risk register.

Q13: Describe a difficult stakeholder and how you managed them.

Probe: Maturity. Strong candidates avoid name-calling and instead describe specific behaviours and how they adapted.

Q14: Tell me about a time you had to manage conflicting priorities from different stakeholders.

Probe: Negotiation and prioritisation. Mention how you brought stakeholders together to make trade-offs explicit, rather than secretly trying to satisfy everyone.

Q15: How have you handled a stakeholder who kept changing their mind?

Probe: Your facilitation skills. Strong answers include locking decisions formally, raising the cost of changes transparently, and using decision logs.

Q16: Walk me through your approach to a project kick-off.

What they probe: Whether you have a repeatable framework. Strong answers cover: confirming the charter, stakeholder identification and analysis, high-level scope and assumptions, defining the team’s working agreement, risk inventory, and communications plan. Mentioning the PMBOK process groups demonstrates fluency.

Q17: How do you build a project schedule from scratch?

Probe: Schedule competence. Walk through WBS decomposition, activity sequencing, dependency types (FS, SS, FF, SF), duration estimation techniques (analogous, parametric, three-point), critical path identification, and resource levelling.

Q18: Explain how you would set up a quality management plan.

Probe: Understanding that quality is not just testing. Strong answers cover quality standards, prevention versus inspection, cost of quality, and continuous improvement.

Q19: When would you choose agile over predictive?

Probe: Whether you understand the trade-offs. Strong answers reference uncertainty, requirements stability, customer involvement, and team maturity. The framing of Stacey’s matrix or the Cynefin framework signals fluency.

Q20: Describe a hybrid project you have led.

Probe: Practical hybrid experience. Talk about which workstreams ran agile (often the build), which ran predictive (often infrastructure or regulatory), and how you reconciled the two on cadence and reporting.

Q21: What is the difference between Scrum, Kanban, and SAFe?

Probe: Whether you know more than buzzwords. Cover sprint cadence, work in progress limits, and scaled frameworks. Be honest about what you have actually used.

Hybrid projects are increasingly the norm rather than the exception. If you cannot speak to running mixed delivery approaches, you are signalling that your experience is dated.

Q22: Explain earned value management in plain language.

Probe: Whether you can communicate technical concepts to non-technical sponsors. Strong answers tie planned value, earned value, and actual cost back to schedule and cost performance.

Q23: A CPI of 0.85 and SPI of 1.05 means what?

Probe: Quick numeric fluency. Translation: you are over budget but ahead of schedule. Likely you are crashing the project (paying for overtime or expedited resources to stay on time). Strong candidates immediately ask what corrective action makes sense.

Q24: How do you compute estimate at completion?

Probe: Formula fluency. The most-used formula is EAC = BAC / CPI. The bonus answer acknowledges that other formulas apply depending on whether the variance is typical or atypical.

Q25: Walk me through your risk management process.

Probe: Repeatable process. Hit identification (workshops, interviews, checklists), qualitative analysis (probability and impact matrix), quantitative analysis (expected monetary value, Monte Carlo if applicable), response planning (avoid, transfer, mitigate, accept), and monitoring.

Q26: How do you decide what risk response to use?

Probe: Decision fluency. Strong answers tie response choice to probability and impact, but also to the team’s risk appetite, cost of mitigation, and timing of the risk window.

Q27: What is the difference between a risk and an issue?

Probe: Vocabulary discipline. A risk is uncertain; an issue is already happening. Confusing the two is a junior signal.

Q28: How do you tailor your approach for different project types?

Probe: PMBOK 7 fluency. Strong answers reference performance domains, delivery approach, team capability, organisational culture, and regulatory context.

Q29: How do you build trust quickly with a new team?

Probe: Servant leadership instincts. Talk about listening before doing, removing blockers visibly, and being honest about what you do and do not know.

Q30: What does servant leadership mean to you?

Probe: Whether you can articulate a leadership philosophy. Strong answers tie servant leadership to specific behaviours: clearing impediments, asking what the team needs, taking blame and giving credit, and protecting focus.

Beneath every question, interviewers are really evaluating four things:

1. Ownership. Do you take responsibility, or do you deflect to circumstances, the team, or the sponsor?
2. Judgement. When the answer is not obvious, how do you weigh trade-offs?
3. Communication. Can you make a complex situation simple without making it simplistic?
4. Self-awareness. Do you know what you do not know? Do you have a learning mindset?

A candidate who scores well on all four is a senior PMP hire regardless of the specific stories they tell. A candidate who scores poorly on any one of these will struggle no matter how impressive the projects on their resume look.

Some patterns I have learned to watch for:

• Vague pronouns. “We delivered the project.” Who is we? What did you specifically do?
• Never failed. Anyone who claims they have never missed a deadline is either inexperienced or dishonest.
• Blaming the team. “My team did not perform” tells me you did not lead them well.
• Process for its own sake. Quoting the PMBOK without ever applying it.
• No numbers. A senior PM should be able to put numbers on projects: budget, team size, duration, business impact.
• Excessive caveating. “It depends” is a fine answer occasionally, but if it is your answer to every question, I cannot tell what you actually believe.
• Resume inflation. Saying you ran a USD 50 million programme when you ran a USD 5 million workstream within it.

If you catch yourself doing any of these in mock interviews, fix it before the real one.

The best preparation I have seen looks like this:

• One week out: Prepare 8 STAR stories and tag them to common question themes.
• Three days out: Drill technical answers verbally, not just in your head. Speaking is different from thinking.
• One day out: Read the job description and the company’s press releases. Anticipate role-specific questions.
• Morning of: Review your stories one last time, then stop preparing. Confidence beats cramming.

A friend who hires PMP project managers told me she can tell within the first two questions whether someone has done mock interviews. Practice out loud. Record yourself. Listen back. It is uncomfortable and it works.