Project manager interview questions

Project manager interviews are mostly behavioural: the interviewer wants evidence that you deliver on time and on budget, manage stakeholders and handle problems before they escalate. Bring three or four STAR stories with numbers (budget, team size, deadline, outcome) and expect to be asked how you would run their kind of project.

8 questions with sample answers

  1. Describe a project you delivered from start to finish.

    Sample answer

    I led the move of a 300-person company to a new CRM. It had a 9-month timeline, a budget of 450,000 EUR and a team of eight across IT, sales and an external vendor. I split the rollout into three waves by department so problems surfaced in the smallest group first. We went live two weeks early and 4% under budget, and 92% of sales reps were using the new system daily after the first month.

    What the interviewer is checking: Scale, your role and concrete outcomes. Vague answers about "helping coordinate" do not show ownership.

  2. How do you handle scope creep?

    Sample answer

    Every change request goes through the same short process: what is being asked, why, and what it costs in time and money. Then the sponsor decides whether to add it, swap it for something else or park it for phase two. On my last project that turned 23 requests into 6 approved changes, and the deadline held.

    What the interviewer is checking: Whether you protect the plan without simply saying no to stakeholders.

  3. Tell me about a project that went off track and what you did.

    Sample answer

    Situation: halfway through a website rebuild, our agency missed two milestones in a row. Task: launch was tied to a product release and could not move. Action: I ran a re-planning session, cut two nice-to-have features with the sponsor's approval and moved to weekly demos instead of monthly reports. Result: we launched on the original date, and the cut features shipped six weeks later.

    What the interviewer is checking: How you react to bad news: early escalation, clear trade-offs and keeping the sponsor informed.

  4. How do you manage a difficult stakeholder?

    Sample answer

    I try to understand what they're worried about first. A finance director kept blocking decisions on a project of mine; it turned out she had been surprised by costs on a previous project. I set up a fortnightly 15-minute budget review just for her. After the second one, her objections stopped and she became one of the project's strongest supporters.

    What the interviewer is checking: Empathy and influence. Going around a stakeholder or escalating at once suggests weak relationship skills.

  5. How do you identify and manage risks?

    Sample answer

    I run a risk workshop at kick-off and keep a simple register: each risk has an owner, a likelihood, an impact and a next action. We review the top five every week rather than the whole list. On a data centre migration, that review flagged a vendor's staff shortage a month early, so we booked backup engineers before it became a delay.

    What the interviewer is checking: That risk management is a habit you practise, not a document you write once.

  6. Agile or waterfall: which do you prefer?

    Sample answer

    It depends on how well the requirements are known. For a regulatory reporting change with a fixed deadline and fixed rules, I plan it waterfall-style with clear stage gates. For a new customer app where we're still learning what users want, I run two-week sprints with a demo at the end of each one. Most of my projects end up as a hybrid.

    What the interviewer is checking: Flexibility and understanding of when each method fits, not loyalty to one framework.

  7. How do you keep a team motivated under pressure?

    Sample answer

    I make the goal and the trade-offs visible, protect the team from new requests during the crunch, and celebrate small milestones rather than only the launch. During a three-week push before a trade fair, I took over all status reporting so the engineers could focus, and nobody worked a weekend.

    What the interviewer is checking: Leadership without formal authority, and whether you look after people as well as the plan.

  8. Which tools do you use to run projects?

    Sample answer

    Jira for delivery tracking, a shared roadmap in Confluence, and a one-page status report every Friday with milestones, budget, top risks and decisions needed. The tool matters less than the rhythm: everyone knows where to look and when it's updated.

    What the interviewer is checking: Practical habits and whether you can adapt to their tools quickly.

How to prepare

  • Prepare four STAR stories: a delivery, a failure you recovered, a stakeholder conflict and a scope decision.
  • Know the numbers of your main projects: budget, team size, timeline and results.
  • Read the posting for the methodology and tools they use and map your experience to them.
  • Be ready to sketch a plan for a project like theirs on a whiteboard.

Questions to ask the interviewer

  • What is the biggest project this role would own in the first year?
  • How are priorities decided when two projects compete for the same people?
  • What happened to the last project that ran late here?