Skip to content
Resume Studioby M2Toolkit

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. 1.

    Your project is behind schedule. What do you do?

    IntermediateSituational

    What 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

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. 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.

    Practise this question and get feedback
  2. 2.

    Compare agile and waterfall. When would you use each?

    BeginnerRole knowledge

    What 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

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. 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.

    Practise this question and get feedback
  3. 3.

    How do you identify and manage project risks?

    IntermediateRole knowledge

    What 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

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. 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.

    Practise this question and get feedback
  4. 4.

    How do you prevent and handle scope creep?

    IntermediateRole knowledge

    What 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

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. 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.

    Practise this question and get feedback
  5. 5.

    How do you keep stakeholders informed about a project?

    BeginnerRole knowledge

    What 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

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. 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.

    Practise this question and get feedback
  6. 6.

    Tell me about a time you managed a difficult situation with a team member.

    IntermediateBehavioural

    What 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

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. 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.

    Practise this question and get feedback
  7. 7.

    Which project management tools and techniques do you use?

    BeginnerRole knowledge

    What 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

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. 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.

    Practise this question and get feedback
  8. 8.

    How do you manage a project budget?

    IntermediateRole knowledge

    What 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

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. 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.

    Practise this question and get feedback

Behavioural & HR questions you'll also get

These come up in almost every project manager interview. Story questions are best answered with STAR — Situation, Task, Action, Result.

  • Tell me about yourself.

    BeginnerHR

    What the interviewer is evaluating

    Whether you can give a concise, relevant pitch that frames your experience around this job.

    Key points a strong answer covers

    • Present. Start with your current role and what you do.
    • Relevant past. Pick the most relevant past experience.
    • Strength / achievement. Include one strength or achievement with evidence.
    • Why this role. Finish with why this role is the next step.

    Suggested answer structure

    1. Present — your current role in one or two sentences.
    2. Past — the experience most relevant to this job.
    3. Proof — one achievement or strength with evidence.
    4. Future — why this role is the logical next step.

    Common mistakes

    • Reciting your whole CV chronologically.
    • Personal life story unrelated to the job.
    • Going over two minutes.

    Likely follow-up questions

    • Why are you looking to leave your current role?
    • What would your manager say is your biggest strength?
    Example strong answer

    I'm a front-end developer with four years' experience, currently at a fintech start-up where I build the customer dashboard in React and TypeScript. Before that I spent two years at an agency building e-commerce sites, which taught me to work fast with lots of different clients. The thing I'm proudest of recently is leading our move to a shared component library, which cut the time to build new screens by about a third. I'm now looking for a role where I can work on a larger product with a strong design system, which is exactly what drew me to this position.

  • Why should we hire you?

    BeginnerHR

    What the interviewer is evaluating

    Whether you understand the role and can match your strengths to its needs with evidence.

    Key points a strong answer covers

    • Role's needs. Show you understand what the role needs.
    • Matching strengths. Match two or three strengths to those needs.
    • Evidence. Back each with evidence.
    • Enthusiasm. Close with genuine enthusiasm.

    Suggested answer structure

    1. Name the two or three things the role needs most.
    2. Match each with your experience and evidence.
    3. Add what makes you different.
    4. Finish with genuine interest.

    Common mistakes

    • Generic claims like 'I'm hardworking' with no evidence.
    • Comparing yourself to other candidates you don't know.

    Likely follow-up questions

    • What would you do in your first 90 days?
    • What's one area where you'd need support?
    Example strong answer

    From the job description and our conversation, you need someone who can take ownership of the customer onboarding process, work with sales and product, and improve the numbers. I've done exactly that for three years: at my current company I redesigned onboarding for new accounts and cut the time to first value from 14 days to 6. I'm comfortable working across teams — I run a weekly session with sales and product on customer feedback — and I'm very data-driven, so I'd measure everything from day one. I'm also genuinely excited about your product, because it solves a problem I've seen customers struggle with.

  • Tell me about a time you disagreed with a teammate. How did you handle it?

    BeginnerBehavioural

    What the interviewer is evaluating

    Handling conflict constructively and keeping relationships.

    Key points a strong answer covers

    • Listened to their view. Show you listened to understand their view.
    • Used facts / common goal. Bring it back to facts or a shared goal.
    • Resolution & relationship. Resolve it and keep the relationship.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Making the other person the villain.
    • A story where you were simply right and they gave in.

    Likely follow-up questions

    • What if you couldn't reach agreement?
    • Have you ever been wrong in a disagreement?
    Example strong answer (a fictional story — use your own)

    On a website rebuild, a senior designer wanted an animated, image-heavy homepage, and I was worried it would hurt mobile load times and SEO. As the developer responsible for performance, I needed us to agree before the sprint started. I asked her to walk me through what she was trying to achieve — she wanted the brand to feel premium. I built two quick prototypes, one with her full design and one with lighter animations, and we tested both on a mid-range phone together. Hers took nearly six seconds to load. We agreed on a version that kept the key animation but lazy-loaded the rest. The page launched loading in under two seconds, and she later asked me to review designs earlier. I learned that testing together beats debating.

  • Tell me about a mistake you made and what you learned.

    BeginnerBehavioural

    What the interviewer is evaluating

    Honesty, accountability and learning.

    Key points a strong answer covers

    • Real mistake owned. Own a real mistake.
    • Fixed it. Show how you fixed it and who you told.
    • Changed behaviour. Show what you changed afterwards.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Choosing a fake mistake like 'I work too hard'.
    • Blaming others.

    Likely follow-up questions

    • How did your manager react?
    • How do you know you haven't repeated it?
    Example strong answer (a fictional story — use your own)

    In my first year as a marketing coordinator, I sent a promotional email to our whole list with the wrong discount code — I'd tested the email but not clicked the code itself. Within an hour customers were complaining that it didn't work. I told my manager immediately, set the wrong code to apply the discount too, and sent a short correction email with an apology. We lost very little revenue, and some customers replied thanking us for the quick fix. Since then I use a pre-send checklist that includes testing every link and code as a customer would, and I asked for a second person to check any campaign to more than 10,000 people.

  • Describe a situation where you worked under pressure or to a tight deadline.

    BeginnerBehavioural

    What the interviewer is evaluating

    Prioritisation, composure and delivery.

    Key points a strong answer covers

    • The pressure. Make the pressure concrete.
    • Prioritised. Show how you prioritised.
    • Communicated. Show how you kept people informed.
    • Delivered. Show the outcome.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Glorifying working all night as the solution.
    • No mention of prioritising.

    Likely follow-up questions

    • What would you do if it was clear you couldn't make the deadline?
    • How do you stop pressure affecting quality?
    Example strong answer (a fictional story — use your own)

    Two days before a client presentation, our analyst fell ill and I had to finish the market research report she'd been leading. I listed everything left and asked the account director which sections the client cared about most — pricing and competitor comparison. I focused on those, reused verified data from our previous report, and moved the appendix to a follow-up email. I sent a short update each evening so nobody was surprised. We delivered the core report on time, the client approved the next phase, and the appendix followed two days later. I learned to ask early what matters most rather than trying to do everything equally well.

  • What would you do if you realised you were going to miss a deadline?

    BeginnerSituational

    What the interviewer is evaluating

    Transparency and problem solving.

    Key points a strong answer covers

    • Tell people early. Flag it as soon as you know.
    • Assess the gap. Work out how far off you are.
    • Options. Offer options: reduced scope, help, a new date.
    • Prevent repeats. Learn why it happened.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Waiting until the deadline to say anything.
    • Promising you'll just work all night.

    Likely follow-up questions

    • What if your manager is unavailable?
    • Has this happened to you?
    Example strong answer

    I'd tell the person depending on it as soon as I realised, not at the deadline. Before that conversation I'd work out how far off I am and why, so I could offer options: delivering the most important part on time and the rest a few days later, getting help from a colleague, or agreeing a new date. Then I'd let them decide what works best for them, and keep them updated. Afterwards I'd look at why it slipped — usually underestimating something — so I plan better next time.

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.

Interview questions for related roles