Interview Prep · Project Management
Project Manager Interview Questions & Answers 2026
Comprehensive PM interview preparation covering project planning, risk management, stakeholder scenarios, and behavioural questions — with detailed model answers from PMAISM's placement coaches.
Project Planning & Lifecycle
Project Planning Questions
-
I would begin with project initiation: defining the project charter, securing stakeholder sign-off, and establishing the project objectives, scope, and success criteria. From there, I move into planning: creating the project plan with a WBS (Work Breakdown Structure), identifying the project team and RACI, developing the risk register, setting up the communication plan, and aligning on timeline and budget with the sponsor. Once the plan is approved, execution begins with regular status meetings, progress tracking, and proactive risk management. I run structured project reviews at key milestones and ensure proper closure documentation — lessons learned, benefits realisation review, and resource release — at the end.
-
Scope creep is best prevented, not just managed. Prevention starts with a clear, agreed scope definition in the project charter and a formal change control process. When a new requirement comes in, I assess its impact on time, cost, and risk — and present that impact to the sponsor before accepting it. If the change is approved, the scope, timeline, and budget are formally updated. If it is not approved, I document the decision. The key phrase is "nothing changes without a change request." In practice, I have a standing agenda item in stakeholder meetings for "open change items" — which keeps the conversation structured rather than reactive.
-
A project is a temporary endeavour with a defined start and end, producing a specific deliverable. A programme is a group of related projects managed in a coordinated way to achieve strategic benefits that could not be realised by managing them individually. For example, a digital transformation initiative might be a programme comprising separate projects for CRM implementation, data migration, process automation, and employee training. The Programme Manager coordinates dependencies, shared resources, and benefits realisation across all these projects.
Risk & Stakeholders
Risk Management and Stakeholder Questions
-
Risk management is continuous throughout the project lifecycle. I maintain a risk register that captures each risk's probability, impact, owner, and mitigation/contingency plan. I use a risk matrix (probability × impact) to prioritise which risks need active management vs. monitoring. Risks are reviewed weekly in project status meetings and updated at each milestone gate. For high-priority risks, I develop both mitigation plans (reducing probability) and contingency plans (reducing impact if the risk materialises). I also track trigger events — early warning signals that a risk is about to materialise — so I can activate contingency plans proactively rather than reactively.
-
Use the STAR method: Situation (describe the stakeholder and the challenge), Task (your role and what needed to be achieved), Action (what you specifically did — building trust through regular check-ins, understanding their underlying concerns, involving them in decisions, escalating where needed), Result (what changed and what the outcome was). Common difficult stakeholder scenarios: a sponsor who kept changing priorities, a business SME who was unresponsive, an external client with unrealistic expectations. Pick a real example and structure it tightly. Do not frame the stakeholder as the villain — frame it as a relationship you successfully managed.
-
First, I diagnose the root cause: is it resource constraints, scope additions, technical complexity, dependency delays, or estimation errors? The response depends on the cause. Options include: fast-tracking (running tasks in parallel that were sequentially planned), crashing (adding resources to critical path tasks), descoping low-priority features, or re-baselining the plan with stakeholder agreement. I always communicate proactively — I do not wait for a milestone gate to surface a schedule risk. Stakeholders handle bad news much better when they hear it early, with options, than late with only one choice.
Behavioural Questions
Behavioural & Situational PM Questions
-
This question is not a trap — every experienced PM has a failure. The interviewer wants to see self-awareness, accountability, and learning. Structure your answer: describe the project and what went wrong, take ownership of your role in the failure, describe what you would do differently, and close with what you changed in your practice as a result. Avoid blame, avoid minimising the failure, and avoid choosing a "failure" that was actually a success with one hiccup. Real, honest failures handled with professional maturity are far more impressive than polished non-answers.
-
I escalate to the appropriate governance level — usually a Portfolio Manager or Steering Committee — with a clear analysis of the impact of each prioritisation scenario. I do not make unilateral resource allocation decisions that cut across project boundaries; I present the trade-offs and let the business decide. Within my own project, I use a capacity-based approach: I understand each team member's committed hours and match task assignments to realistic availability, flagging any overload immediately rather than hoping it resolves itself.
-
This is your opportunity to tell a compelling story. The strongest answers are specific and genuine: "I have been the informal coordinator in my team for two years — managing timelines, communicating with stakeholders, and tracking deliverables — and I want to formalise that into a PM role where I can have greater impact." Avoid generic answers like "I'm a natural leader" or "I like organising things." Connect it to your specific experience, show that you understand what the role involves, and demonstrate genuine enthusiasm for the work rather than just the title.