PMP Interview Questions

Quick answer

PMP interview questions test whether you can apply project management in real work, not whether you can recite definitions: expect questions on scope, schedule, cost, risk, stakeholders, agile and hybrid delivery, plus behavioural and scenario questions answered with real examples. Interviewers for PMP-level roles assume you know the terms. What they want to hear is how you used them, what trade-offs you made and what the result was. The 50 questions below come with short model answers you can adapt to your own projects.

Key takeaways

1. How project manager interviews work when PMP is expected

Short answer: Most companies run 3 to 5 rounds: a recruiter screen, a technical or process round, a scenario or managerial round, sometimes a client round, and an HR round. PMP is used as a filter on your resume, then the interviews check that you can actually manage projects.

In India, many job posts mention PMP. On 22 October 2026, Naukri listed 2,181 results for project manager jobs in Hyderabad, and a keyword search for "PMP" in Hyderabad returned 4,899 results. The PMP search is a keyword match, so it includes posts that only mention PMP as a "nice to have". Either way, the credential gets you shortlisted, and the interview decides the offer. For the roles and companies that hire, see our guide to PMP certification jobs.

How to answer: the STAR method

For behavioural and scenario questions, use STAR:

Keep each answer to about two minutes. Let the interviewer ask follow-up questions instead of telling everything at once.

2. Basic PMP and project management questions

Short answer: Basic questions check that you understand what a project is, what the PMP credential means, how life cycles differ and what a project manager is accountable for. Freshers moving into PM roles and career switchers get many of these.

Q1. Tell me about yourself.

Give a 60 to 90 second summary in three parts: present, past and future. For example: "I am a project manager with seven years in IT services. I currently lead a 12-member team delivering a payments platform for a banking client. Before that I was a business analyst, which taught me requirements and stakeholder work. I earned my PMP last year and now want to lead larger, hybrid programmes." End with why this role fits.

Q2. What is a project, and how is it different from operations?

A project is a temporary effort to create a unique product, service or result. It has a defined start and end. Operations are ongoing and repetitive, such as running payroll every month. Building a new payroll system is a project. Running it after go-live is operations. Interviewers ask this to see whether you think in terms of outcomes and closure.

Q3. What is PMP, and why did you get it?

PMP stands for Project Management Professional, a certification from PMI (Project Management Institute). Under PMI's July 2026 rules, experience must be in leading projects, without overlap, within the last 10 years: 36 months with a bachelor's degree, 48 months with an associate degree or vocational diploma, 60 months with secondary school, or 24 months with a GAC-accredited degree. You also need 35 hours of project management training (PMI Exam Content Outline, July 2026). In your answer, link the credential to results: "It gave me a common language with clients and a structured way to handle risk and change."

Q4. What does the PMP exam cover today?

The current exam has 180 questions (170 scored and 10 unscored) in 240 minutes, with two 10-minute breaks. It covers three domains: People 33%, Process 41% and Business Environment 26%. About 40% reflects predictive approaches, and 60% agile and hybrid (PMI, July 2026). PMI says the July 2026 update added AI, sustainability and stakeholder engagement in project scenarios (PMI, October 2026). For the full format, see our PMP exam questions guide.

Q5. What is the triple constraint?

The triple constraint is scope, time and cost. Change one and at least one other moves. If the client adds features, you need more time, more money or both. Modern practice adds quality, risk and value to the picture. A strong answer gives an example: "When the client added two reports, I showed them a two-week delay or an extra developer, and they chose the delay."

Q6. What are the main project life cycles?

Predictive (waterfall) plans scope, time and cost upfront and suits stable requirements, like construction. Adaptive (agile) delivers in short iterations and suits changing requirements, like a new mobile app. Hybrid mixes both, for example a predictive plan for hardware and infrastructure with agile sprints for the software. Say which you have used and why it fit.

Q7. What is the PMBOK Guide, and which edition is current?

The PMBOK Guide is PMI's main reference for project management. The current edition is the Eighth Edition, published in November 2025. It keeps the principle-based approach of the Seventh Edition, lists seven performance domains (governance, scope, schedule, finance, stakeholders, resources and risk) and brings back process guidance in a non-prescriptive way (PMI PMBOK Guide page, October 2026). Interviewers mainly want to hear that you know it is a guide, not a rulebook.

Q8. What is the difference between a project, a programme and a portfolio?

A project delivers one specific output. A programme is a group of related projects managed together for benefits you could not get by managing them separately, such as a bank's digital transformation. A portfolio is a collection of projects and programmes chosen to meet strategic goals. The portfolio question is "are we doing the right work?" and the project question is "are we doing the work right?"

3. Scope and planning questions

Short answer: Scope questions test whether you can define what is in and out, break work down, control change and stop scope creep. Planning questions test how you build an integrated plan.

Q9. What is a project charter, and what does it contain?

The project charter formally authorises the project and gives the project manager authority to use resources. It usually contains the business case or purpose, high-level objectives, key deliverables, high-level risks, a summary milestone schedule and budget, key stakeholders and the sponsor's sign-off. Without a charter, you have responsibility but no authority.

Q10. What is a work breakdown structure (WBS)?

A WBS breaks the total scope into smaller deliverables until each piece, called a work package, can be estimated, assigned and tracked. It is deliverable-based, not a list of activities. The 100% rule says the WBS must include all the work and nothing else. A WBS dictionary describes each work package, its owner and acceptance criteria.

Q11. How do you prevent scope creep?

Start with a clear scope statement and a baselined WBS. Agree on acceptance criteria early. Run every change through a change control process: log it, analyse impact on time, cost, quality and risk, and get a decision from the right authority. Keep the sponsor close, so pressure for "small extras" goes through the process. In agile, new ideas go into the backlog and the product owner prioritises them.

Q12. What is the difference between product scope and project scope?

Product scope is the features and functions of the thing you deliver, such as "the app supports UPI payments". Project scope is the work needed to deliver it, such as design, build, testing, training and deployment. You measure product scope against requirements and project scope against the plan.

Q13. What goes into a project management plan?

The project management plan pulls together the subsidiary plans and baselines. Baselines are scope, schedule and cost. Subsidiary plans usually cover scope, requirements, schedule, cost, quality, resources, communications, risk, procurement, stakeholder engagement and change management. On a hybrid project, it also states which parts run in sprints and how releases map to milestones.

Q14. How do you gather requirements?

Identify stakeholders first, then use the right techniques: interviews, workshops, focus groups, observation, document analysis and prototypes. Record requirements with acceptance criteria and trace each one to a business objective in a requirements traceability matrix. Validate with stakeholders before baselining. On agile work, the product owner turns them into user stories in the backlog.

Q15. What is a requirements traceability matrix?

It is a table that links each requirement to its source, business objective, design element, test case and status. It proves that every requirement is delivered and tested, and that nothing was built without a reason. It also helps you assess the impact of a change, because you can see what else a requirement touches.

4. Schedule and cost questions, with a worked earned value example

Short answer: Expect questions on the critical path, float, estimation methods, schedule compression and earned value. Interviewers often give you numbers and ask you to calculate on the spot, so practise the worked example below.

Q16. What is the critical path?

The critical path is the longest path of dependent activities through the network. It sets the shortest possible project duration. Activities on it have zero total float, so any delay delays the project. Example: path A-B-D takes 3 + 5 + 4 = 12 days and path A-C-D takes 3 + 2 + 4 = 9 days. The critical path is A-B-D at 12 days, and activity C has 3 days of float.

Q17. What is the difference between total float and free float?

Total float is how long an activity can slip without delaying the project end date. Free float is how long it can slip without delaying the next activity. In the example above, C has 3 days of total float. If another activity depended directly on C's early finish, C's free float could be smaller.

Q18. How do you estimate activity duration?

Common methods are analogous estimating (based on a similar past project), parametric estimating (rate times quantity, such as 2 days per screen times 10 screens), three-point estimating and bottom-up estimating. In agile teams, you use story points and velocity. Always involve the people doing the work, and record assumptions.

Q19. What is PERT, and how do you calculate it?

PERT, or beta three-point estimating, uses optimistic (O), most likely (M) and pessimistic (P) estimates: (O + 4M + P) divided by 6. If O = 4 days, M = 6 days and P = 14 days, the estimate is (4 + 24 + 14) / 6 = 7 days. The standard deviation is (P minus O) / 6, here about 1.7 days. It gives a weighted, realistic estimate.

Q20. What are crashing and fast tracking?

Both compress the schedule. Crashing adds resources to critical path activities, such as overtime or an extra developer, which raises cost. Fast tracking runs activities in parallel that were planned in sequence, such as starting build before design is fully signed off, which raises risk and rework. Compress only critical path activities, otherwise you spend money without saving time.

Q21. What is earned value management (EVM)?

EVM measures project performance by comparing three values. Planned value (PV) is the budgeted cost of work planned so far. Earned value (EV) is the budgeted cost of work actually done. Actual cost (AC) is what you really spent. From these you get variances and indices that show whether you are ahead or behind on schedule and cost.

Q22. Walk me through an earned value example.

Here is a worked example with simple illustrative numbers. Your project has a budget at completion (BAC) of ₹50 lakh over 10 months. At the end of month 5, the plan said 50% would be done, but only 40% is done, and you have spent ₹24 lakh.

How to explain it: "For every rupee we spend, we get about 83 paise of work, and we are doing 80% of the work we planned. If nothing changes, we will finish about ₹10 lakh over budget. To finish on the original budget, the team would need to perform at 1.15, which is unlikely, so I would present recovery options to the sponsor: re-baseline, cut scope or add funding."

Q23. What is the difference between contingency reserve and management reserve?

Contingency reserve covers identified risks, the "known unknowns", and is part of the cost baseline that the project manager controls. Management reserve covers unidentified risks, the "unknown unknowns", sits outside the cost baseline but inside the total budget, and usually needs sponsor or management approval to use.

5. Risk and quality questions

Short answer: Risk questions check that you manage threats and opportunities before they become issues. Quality questions check that you build quality in rather than inspect it in at the end.

Q24. What is the difference between a risk and an issue?

A risk is an uncertain event that may happen in the future and affect objectives, positively or negatively. An issue is something that has already happened and needs action now. A key developer who might resign is a risk. A key developer who resigned yesterday is an issue. Good risk management turns fewer risks into issues.

Q25. Walk me through your risk management process.

Plan how you will manage risk. Identify risks with the team using brainstorming, checklists and lessons learned. Analyse them qualitatively with a probability and impact matrix, and quantitatively for big projects. Plan responses and assign an owner to each. Implement responses, then monitor, review the risk register in every status meeting and look for new risks.

Q26. What are the risk response strategies?

For threats: avoid (change the plan to remove the risk), transfer (shift it to a third party, such as insurance or a fixed-price contract), mitigate (reduce probability or impact) and accept (actively with a reserve, or passively). For opportunities: exploit, share, enhance and accept. Escalate is used for both when the risk is outside your authority.

Q27. Give an example of a risk you identified early.

Use STAR. Example: "On a data migration project, I saw that the legacy system had no documentation. I logged it as a high risk, got the client to assign a senior user for two days a week and added a test migration cycle. The trial run found 30 mapping errors, which we fixed before go-live. The real migration finished on schedule." Use your own real numbers.

Q28. What is the difference between quality assurance and quality control?

Quality assurance is about the process: are we following the right standards and practices so that quality is built in? Examples include audits and process reviews. Quality control is about the product: does the output meet requirements? Examples include testing and inspections. QA prevents defects, QC finds them.

Q29. What is the cost of quality?

Cost of quality has two parts. Cost of conformance is money spent to prevent defects, such as training, reviews and testing. Cost of non-conformance is money lost because of defects, such as rework, warranty claims and lost customers. Spending more on prevention usually lowers the total cost.

6. Stakeholder and communication questions

Short answer: These questions test how you identify, engage and influence people. The People domain is a third of the new PMP exam, and interview panels give it similar weight.

Q30. How do you identify and manage stakeholders?

Identify everyone who affects or is affected by the project, starting from the charter and the sponsor. Record them in a stakeholder register with their interest, influence and expectations. Use a power and interest grid: manage closely those with high power and high interest, keep satisfied those with high power, keep informed those with high interest, and monitor the rest. Review the register regularly.

Q31. How do you handle a difficult stakeholder?

Listen first to understand the real concern behind the behaviour. Meet one to one, not in a group. Find shared goals, involve them in decisions that affect them and keep commitments. Document agreements. If they still block progress, escalate with facts, not emotions. Example: a business head who rejected every design started supporting the project once he joined the fortnightly demos.

Q32. How many communication channels does a team of 10 have?

Use the formula n(n minus 1) / 2. For 10 people: 10 x 9 / 2 = 45 channels. If the team grows to 15, it becomes 105 channels. The point interviewers want: communication complexity grows much faster than team size, so plan communication carefully as the team grows.

Q33. What goes into a communication management plan?

It states who needs what information, when, in what format, through which channel and who sends it. For example: weekly status report to the sponsor by email, daily stand-up for the team, monthly steering committee with a dashboard, and an escalation path. It also covers language, time zones and confidentiality for distributed teams.

Q34. How do you resolve conflict in your team?

Common approaches are collaborate (problem solve), compromise, smooth (accommodate), force (direct) and withdraw (avoid). Collaborating gives the best long-term result when there is time. Start by meeting the people involved, separating facts from feelings and focusing on the shared project goal. Explain which approach you used in a real case and why.

Q35. How do you report project status to senior management?

Keep it short and visual: overall RAG status, key milestones, budget versus actual, top risks and issues, and decisions needed from them. Lead with the message, such as "we are two weeks behind, here is the recovery plan and here is what I need from you." Senior leaders want decisions and outcomes, not activity lists.

7. Agile and hybrid questions

Short answer: With 60% of the new exam on agile and hybrid approaches (PMI, July 2026), expect questions on Scrum roles, backlogs, velocity and how you combine agile with predictive governance. If you are moving between PM and Scrum roles, also read Scrum Master vs Project Manager.

Q36. When would you choose agile, predictive or hybrid?

Choose predictive when requirements are stable, regulation needs upfront documentation or the work is physical, like a building. Choose agile when requirements are uncertain and early feedback adds value, like a new customer app. Choose hybrid when parts of the work differ, such as a fixed-date regulatory release with agile development inside it. The choice depends on uncertainty, risk, team and organisation.

Q37. What is the role of a project manager in an agile team?

In pure Scrum, there is no project manager role: the Product Owner owns the backlog, the Scrum Master coaches the team and developers manage their own work. In practice, many Indian IT companies keep a project manager or delivery manager who handles budget, contracts, cross-team dependencies, reporting and stakeholder management, while respecting the team's self-management.

Q38. What is velocity, and how do you use it?

Velocity is the amount of work, usually in story points, a team completes per sprint. Use the average of the last three to five sprints to forecast. If the backlog has 300 points and velocity is 30, you need about 10 sprints. Never compare velocity between teams or use it as a performance target, because teams will inflate estimates.

Q39. How do you manage scope and change in agile projects?

Change is expected. New requests go into the product backlog, and the Product Owner prioritises them by value. The sprint goal is protected during the sprint. Time and cost are often fixed, so scope flexes. A burn-up chart shows clearly how added scope moves the expected finish date, which helps conversations with stakeholders.

Q40. How do you run a hybrid project?

Define which parts are predictive and which are agile, and how they connect. For example: milestones, budget and vendor contracts are managed predictively, while software is built in two-week sprints. Map releases to milestones, use one integrated risk register and report both burn-up charts and milestone status in a single dashboard.

Q41. How are you using AI in project management?

PMI's July 2026 update brought AI into project scenarios on the exam (PMI, October 2026), so this question is now common. Give practical, honest examples: drafting meeting minutes and status reports, summarising long documents, generating first-cut risk lists or test cases. Then explain your controls: you review all output, protect client data and never let AI make decisions on its own.

8. Behavioural questions with STAR examples

Short answer: Behavioural questions ask "tell me about a time when...". The panel is checking your judgement, leadership and honesty. Use the STAR method and your own real projects. The examples below show the structure; replace them with your own facts.

Q42. Tell me about a project that failed or went badly.

Pick a real case and own your part. Situation: a CRM rollout slipped by six weeks. Task: I was the project manager. Action: I found that we had skipped proper user acceptance planning, reset the plan with the client, added a UAT lead and introduced weekly demos. Result: we went live six weeks late but with high adoption, and I now plan UAT in week one of every project.

Q43. Tell me about a time you managed a project under a tight deadline.

Situation: a regulator moved a compliance deadline forward by a month. Task: deliver the reporting change on the new date. Action: I cut scope to the mandatory reports with the sponsor's approval, fast tracked testing alongside build and held a 15-minute daily risk check. Result: we met the deadline, and the optional reports followed in the next release.

Q44. Describe a time you handled an underperforming team member.

Situation: a strong developer started missing deadlines. Task: fix delivery without losing him. Action: I spoke to him privately, learned he was overloaded with support calls from another team, moved that work to a rota and agreed clear weekly goals. Result: his delivery recovered within a month. The lesson: look for the cause before judging the person.

Q45. Tell me about a time you had to say no to a client.

Situation: a client asked for a new dashboard two weeks before go-live. Task: protect the release without damaging the relationship. Action: I thanked them, showed the impact on date and cost in a one-page note and offered it as the first item in the next release. Result: the client agreed, the release went live on time and the dashboard shipped three weeks later.

Q46. What are your strengths and weaknesses as a project manager?

Pick a strength the role needs, backed by evidence: "I am strong at stakeholder management. On my last programme, I kept four business units aligned through fortnightly steering meetings." Pick a real, non-fatal weakness with a fix: "I used to take on too much myself. Now I delegate by work package and review outcomes, not every task."

9. Scenario questions

Short answer: Scenario questions describe a problem and ask what you would do first. Answer in order: understand and assess, involve the right people, act within your authority, communicate, and update plans and lessons learned. Avoid jumping straight to escalation.

Q47. Your sponsor wants to cut two weeks from the schedule. What do you do?

First analyse the critical path to see where time can come from. Present options with their trade-offs: fast tracking (more risk), crashing (more cost) or reducing scope (less value). Show the impact of each in numbers, recommend one and let the sponsor decide. Then update the baseline through change control and tell the team and stakeholders.

Q48. A key team member resigns in the middle of the project. What do you do?

Assess impact: which tasks, knowledge and dates are affected. Use the notice period for knowledge transfer and documentation. Check whether someone in the team can step up, and request a replacement early. Update the schedule and risk register, inform stakeholders if milestones move, and add a "key person dependency" risk with mitigation for future projects.

Q49. You discover a major defect one day before go-live. What do you do?

Get the facts quickly: severity, impact on users, root cause and fix time. Bring the product owner, test lead and technical lead together. Present options to the decision maker: delay the release, go live with a workaround and a hotfix plan, or remove the affected feature. Communicate the decision clearly, then hold a retrospective to see why testing missed it.

Q50. Two senior stakeholders give you conflicting requirements. What do you do?

Do not pick a side yourself. Meet each to understand the business need behind the request. Then bring them together with the data: cost, time and value of each option, and how each links to the project objectives in the charter. If they still disagree, escalate to the sponsor, who owns the business case, and record the decision.

10. How to prepare for a PMP interview in one week

Short answer: Revise the key concepts, practise the calculations, write your STAR stories and research the company. One focused week is enough if you already work on projects.

A few more tips:

Questions to ask the interviewer

11. How Brolly Academy helps

Short answer: Brolly Academy's PMP course in Hyderabad is exam preparation and skills training, with a trainer who has 15+ years of experience and modules that cover the topics interviewers ask about.

The PMP Certification Course in Hyderabad offers 35 contact hours of instructor-led training over 4 weeks, in classroom and online modes, with weekday and weekend batches. The trainer, Mr. Raju, is listed as a PMP trainer with 15+ years of experience. The 13 modules include predictive, agile, hybrid, AI in project management, risk, stakeholder and procurement management, and PMP exam preparation. Those are the same areas covered in the 50 questions above.

Fees on the course page start from ₹10,999 for the video recording plan, with the online course at ₹30,000 and classroom training at ₹40,000. EMI is available. The next batch starts on Monday, 2 November 2026.

One important note: from 1 December 2026, PMI counts live-class hours toward its 35-hour training requirement only when they come from a PMI Authorized Training Partner, a China Registered Education Provider or an eligible accredited programme, while self-paced courses from any organisation still count (PMI, October 2026). Check PMI's current rules for your own application before you choose any course for the training requirement.

Frequently asked questions