Top Project Manager Interview Questions & Answers

Waterfall is a sequential methodology: requirements → design → development → testing → delivery, with each phase completed before the next begins. Agile is iterative: work is completed in short sprints with continuous stakeholder feedback. Waterfall works best for projects with fixed, well-understood requirements. Agile works best when requirements evolve or user feedback is essential.

Prevent it with a clear project charter, RACI matrix, and formal change control process at the start. When it occurs, document the new request, assess its impact on time, cost, and resources, present the tradeoffs to the sponsor, and require written approval before any work begins. Never absorb scope changes silently.

Start with a scope statement and deliverables list from the project charter. Break them into a Work Breakdown Structure (WBS). Sequence tasks, identify dependencies, assign owners, and estimate durations. Build the critical path to identify tasks with zero float. Add buffer for risk items. Baseline the schedule and track against it weekly.

The critical path is the longest sequence of dependent tasks that determines the minimum project duration. Any delay on the critical path delays the project. Non-critical-path tasks have float — they can slip without affecting the end date. Identifying the critical path lets you focus management attention where delays would actually hurt.

First, understand their concern: are they worried about losing control, budget, visibility, or timeline? Schedule a one-on-one, listen actively, and restate their concern to confirm you understand it. Involve them in decisions where they have legitimate input. Escalate to the sponsor only if direct engagement fails and their behavior is blocking the project.

Identify risks in a kickoff workshop with the team. Score each by probability and impact (P×I matrix). For high-scored risks, build a response plan: avoid, mitigate, transfer, or accept. Assign a risk owner for each item. Review the risk log weekly and update scores as conditions change. Never let risks sit in a log without owners.

Executives want headlines, not detail. Use a traffic-light dashboard (RAG status) with a one-paragraph summary per project: schedule status, budget status, top risk, and the one thing needed from leadership. Prepare detail for Q&A but lead with the summary. Deliver bad news proactively — surprises destroy trust.

Be specific and honest. Describe the project, the failure mode (missed deadline, over budget, quality issue, stakeholder misalignment), and your role in it. The key is to show self-awareness and what process improvement you implemented afterward. Interviewers are testing for accountability and learning agility.

Use the STAR format. Be specific about what the pressure was (tight deadline, reduced team, scope change), the actions you took (re-prioritized scope, added resources, negotiated timeline), and the outcome. Quantify where possible: "Delivered 3 weeks early" or "Reduced budget by 15%."