8 role-specific questions
Project Manager Interview Questions & Answers
Project management interviews test how you plan, control scope, budget and risk, keep stakeholders informed, choose a delivery approach, and recover projects that are slipping.
Free, no sign-up. 61 questions in this role's practice pool, including behavioural, HR and situational questions.
Project management interview questions
Planning, scope, risk, agile and waterfall delivery, stakeholders and recovering projects.
1.
Your project is behind schedule. What do you do?
IntermediateSituationalPractise this question and get feedbackWhat the interviewer is evaluating
Recovery planning and transparency.
Key points a strong answer covers
- Diagnose. Understand why and by how much.
- Options. Options: reduce scope, add resources, fast-track, move the date.
- Stakeholders early. Tell stakeholders early with options.
- Re-plan & monitor. Re-plan, re-baseline and monitor closely.
Suggested answer structure
- Clarify the situation and what's at stake.
- Say what you'd do first, and why.
- Explain who you'd involve and how you'd communicate.
- Describe how you'd check the outcome and prevent a repeat.
Common mistakes
- Hiding the delay until the deadline.
- Adding people late without considering ramp-up.
Likely follow-up questions
- Why can adding people to a late project make it later?
- How do you decide between cutting scope and moving the date?
Example strong answer
First I'd find out how far behind we are and why — underestimated tasks, scope creep, a blocked dependency, people pulled onto other work — because the fix depends on the cause. Then I'd look at the options: cut or defer lower-priority scope, run tasks in parallel, remove blockers, add people where ramp-up is short, or move the date. I'd go to the sponsor and key stakeholders early, with the facts and those options and their trade-offs, not just the bad news. Once we agree, I'd re-baseline the plan, communicate it to the team, and track progress more frequently, watching the risks that caused the slip.
2.
Compare agile and waterfall. When would you use each?
BeginnerRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Methodology judgement.
Key points a strong answer covers
- Waterfall sequential. Waterfall runs in sequential phases with upfront planning.
- Agile iterative. Agile delivers in short iterations with frequent feedback.
- When waterfall. Waterfall fits fixed, well-understood requirements.
- When agile. Agile fits uncertain or changing requirements.
- Hybrid. Many organisations use hybrids.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Treating agile as 'no planning'.
- Saying one is always better.
Likely follow-up questions
- What does a hybrid approach look like in practice?
- How do you handle fixed-price contracts in agile?
Example strong answer
Waterfall moves through sequential phases — requirements, design, build, test, deploy — with most planning done upfront and change controlled formally. It works when requirements are stable and well understood, or change is expensive: construction, hardware, regulated or fixed-scope contracts. Agile delivers in short iterations, gets feedback from users each sprint and adapts the plan, which suits software and anything where requirements are uncertain or will evolve. In practice many organisations use a hybrid — a phased plan with milestones and budget for governance, with agile delivery inside. Agile still involves planning, just more often and in smaller pieces.
3.
How do you identify and manage project risks?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Proactive risk management.
Key points a strong answer covers
- Identify. Identify risks with the team, from assumptions, dependencies and past projects.
- Assess. Assess likelihood and impact.
- Responses. Plan responses: avoid, mitigate, transfer, accept, with contingencies.
- Owners & register. Each risk has an owner in a risk register.
- Review regularly. Review regularly and watch triggers.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- A risk register created once and never updated.
- Confusing risks with existing issues.
Likely follow-up questions
- What's the difference between a risk and an issue?
- Give an example of a risk you mitigated.
Example strong answer
I identify risks at the start with the team and stakeholders — reviewing assumptions, dependencies, constraints and lessons from similar projects — and keep adding them throughout. Each is assessed on likelihood and impact, so we focus on the ones that matter. For each significant risk we choose a response: avoid it by changing the plan, mitigate it, transfer it — for example through a contract — or accept it with a contingency. Every risk has an owner and is tracked in a register that we review in regular meetings, along with early-warning triggers. A risk is something that might happen; an issue is something that already has, and it gets handled through the issue log.
4.
How do you prevent and handle scope creep?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Change control without rigidity.
Key points a strong answer covers
- Clear baseline. Define and agree the scope baseline upfront.
- Change control. Route changes through a simple change control process.
- Impact analysis. Assess impact on time, cost and quality.
- Decision by sponsor. The sponsor decides, with trade-offs explicit.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Saying yes to every small request.
- Being so rigid that valuable changes are blocked.
Likely follow-up questions
- How do you handle a senior stakeholder adding requirements informally?
- Is all scope change bad?
Example strong answer
Prevention starts with a clear, agreed scope — what's in and explicitly what's out — signed off by the sponsor. Then any new request, however small, goes through a lightweight change process: I log it, assess its impact on time, cost, quality and risk with the team, and present the trade-off — 'we can add this report, but it moves launch by a week or we drop the export feature'. The sponsor decides. Not all change is bad — some is exactly what the business needs — so the aim isn't to block change but to make its cost visible. When a senior stakeholder adds requirements in a hallway conversation, I thank them and route it through the same process.
5.
How do you keep stakeholders informed about a project?
BeginnerRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Communication planning.
Key points a strong answer covers
- Communication plan. A communication plan: who needs what, how often.
- Concise status. Concise status (RAG), milestones, risks and decisions needed.
- Tailor. Tailor detail to the audience.
- Honesty & bad news early. Share bad news early — no surprises.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Long reports nobody reads.
- Always-green status that hides problems.
Likely follow-up questions
- What would you do if your report was always green but the project felt troubled?
- How do you report to an executive with five minutes?
Example strong answer
I start with a simple stakeholder map: who's affected, what they need to know and how often. Executives and the sponsor get a short regular status — overall RAG rating with a reason, progress against milestones, top risks and any decisions needed from them — on one page or dashboard. The team gets more detail in stand-ups and planning. Other stakeholders get updates at milestones. The most important rule is no surprises: if something turns amber or red, I tell the sponsor straight away with what we're doing about it, rather than waiting for the next report. A status that's always green usually means it isn't telling the truth.
6.
Tell me about a time you managed a difficult situation with a team member.
IntermediateBehaviouralPractise this question and get feedbackWhat the interviewer is evaluating
People skills and constructive conflict handling.
Key points a strong answer covers
- Situation. The situation.
- Private conversation. A private conversation to understand.
- Root cause & support. Understanding the cause and offering support.
- Result. The outcome.
- Learning. What you learned.
Suggested answer structure
- Situation — one or two sentences of context.
- Task — what you were responsible for.
- Action — what you did, step by step (say “I”).
- Result — what changed, with a number if you can back it up.
- Reflection — what you learned or would do differently.
Common mistakes
- Describing the person negatively without your actions.
- Escalating to their manager first.
Likely follow-up questions
- What would you have done if nothing improved?
- How did it affect the rest of the team?
Example strong answer (a fictional story — use your own)
On a CRM migration, one of our senior developers kept missing sprint commitments and became short with others in stand-ups. I asked him for a one-to-one coffee and asked how the project felt from his side, rather than starting with the missed tasks. It turned out he was also supporting the old system for urgent client issues, which nobody had accounted for, and he felt he was being judged for delays he couldn't control. I made the support work visible on our board, agreed with his manager to rotate it between two people, and re-planned his tasks. Within two sprints he was delivering reliably and was more engaged. I learned to look for hidden workload before assuming a performance problem.
7.
Which project management tools and techniques do you use?
BeginnerRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Your practical toolkit, and whether you use it to help the project rather than for its own sake.
Key points a strong answer covers
- Planning techniques. WBS, Gantt charts, critical path, milestones.
- Agile practices. Scrum/Kanban boards, backlogs, burndown.
- Tools. Tools like Jira, MS Project, Asana, Confluence.
- Tracking & governance. RAID logs, budgets, RACI.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Listing tools without saying how you use them.
- Process for its own sake.
Likely follow-up questions
- What is the critical path?
- How do you choose between Scrum and Kanban?
Example strong answer
For planning I break the work into a work breakdown structure, identify dependencies and the critical path — the longest chain of dependent tasks, which sets the earliest finish date — and turn it into a timeline with milestones, in MS Project or Smartsheet for complex plans. For delivery with software teams I use Scrum or Kanban in Jira, with a prioritised backlog and burndown or cycle-time charts. A RAID log tracks risks, assumptions, issues and dependencies, and a RACI chart clarifies who decides what. Confluence holds decisions and documentation. I keep the process as light as the project allows.
8.
How do you manage a project budget?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Financial control: forecasting, contingency and acting early on variances.
Key points a strong answer covers
- Estimate & baseline. Build a bottom-up estimate and baseline.
- Contingency. Include contingency for risks.
- Track actuals. Track actuals against plan and forecast to completion.
- Act on variance. Act early on variances and escalate.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Only looking at spend so far, not forecast to complete.
- No contingency.
Likely follow-up questions
- What is earned value?
- What would you do if you'll overrun by 15%?
Example strong answer
I build the budget bottom-up from the work breakdown — people's time, vendors, licences, hardware — and add a contingency reserve sized to the risks, agreed with the sponsor as the baseline. During the project I track actual spend and, more importantly, the forecast to completion, because spend-to-date alone can look fine until it's too late. Earned value helps on bigger projects by comparing the value of work completed with what it cost. If a variance appears — say we're trending 15% over — I find the cause, look at options like descoping or renegotiating with a vendor, and take it to the sponsor early, with a recommendation.
Ready to answer them out loud?
Run a timed project manager mock interview, type or speak your answers, and get a score breakdown with what to improve.