Project Manager Interview Questions (With Sample Answers)

Project manager interview questions test one thing from several angles: can you get a project finished when it doesn't go to plan? Expect questions about your experience ("Walk me through a project you managed"), your methods ("How do you handle scope creep?") and realistic scenarios ("You're three weeks behind with six to go. What do you do?"). The strongest answers are specific: a real project, a real trade-off, and what you decided.

Below: what interviewers are scoring, 24 project manager interview questions with sample answers grouped by type, the questions to ask them back, and a one-evening prep plan.

What interviewers are scoring

Experience questions

1. "Walk me through a project you managed from start to finish."

What it tests: whether you can tell a project story with a shape: goal, plan, problem, result.

"I ran our move from an old CRM to a new one: 14 people across sales, support and IT, and a fixed four-month deadline because the old contract was ending. First I agreed what 'done' meant with the sales director: every active account moved, three years of history, no more than a day of downtime. I planned backwards from the contract date. Halfway through we found a lot of duplicate records, which put the date at risk, so I moved two support staff onto clean-up for three weeks and pushed a reporting feature into a second phase. We went live a week early."

Keep it to about two minutes.

2. "Tell me about a project that didn't go to plan."

What it tests: honesty, and whether you learn.

"I launched an internal training portal that hardly anyone used for three months. We were on time and on budget, but I'd taken requirements from managers and never spoken to the people who'd use it. When I interviewed ten of them, they said it took too many clicks to find anything. We rebuilt the home page around the most-searched topics and usage picked up. Now I talk to end users in the first fortnight of every project."

Pick a real failure with a real lesson. "I cared too much" is a boast in disguise, and interviewers know it.

3. "What's the biggest project you've managed?"

Give the numbers (team size, budget, length) and be precise about your role. If you tracked the budget but didn't own it, say so: "I didn't hold the budget, but I reported spend against it every week and flagged when we were heading over."

4. "Which project management tools have you used?"

Name the tools and what you used them for: "Jira for the developers' sprint board, a spreadsheet for the budget, and a one-page weekly update for leadership, who never logged in to Jira." The tool matters less than whether people used it.

5. "Do you prefer Agile or Waterfall?"

What it tests: that you choose a method to fit the work, rather than defend one on principle.

"It depends on how much we know up front. For an office fit-out, the requirements were fixed and the work was sequential, so a phased plan with milestones made sense. For an app redesign, nobody knew exactly what users wanted, so we worked in two-week sprints and showed something every fortnight. Plenty of my projects end up as a mix: milestones for leadership, short iterations inside them."

Process and method questions

6. "How do you plan a new project?"

"I start with the goal and the constraints: what done looks like, by when, with what budget, and who makes decisions. Then I break the work into deliverables, ask the people doing the work to estimate it, and map dependencies to find the critical path. I agree roles, often with a simple RACI chart, start a risk log, and run a kick-off so everyone hears the same plan at the same time."

7. "How do you handle scope creep?"

"I don't treat every new request as a problem; some turn out to be the most valuable thing we build. I just don't let them in quietly. Each change gets written down with its effect on time, cost and risk, and the sponsor decides: add it and move the date, swap it for something else, or save it for a later phase. The worst outcome is a team absorbing changes for free until the deadline gives way."

8. "How do you estimate how long work will take?"

"I ask the people who'll do it, and I ask for a range rather than a single number. For anything new, I break it down until each piece is a few days, because big estimates hide surprises. I compare with similar past work where we have it, and add contingency for the risks we've actually named. Then I track actuals against estimates so the next plan is better."

9. "How do you manage risk?"

"A short risk log: the risk, how likely it is, how bad it would be, an owner, and what we're doing about it. We review it every week, not once at kick-off. I concentrate on the top five, because a 60-row register is one nobody reads. For each one we decide to avoid it, reduce it, accept it or hand it to someone better placed to deal with it."

10. "How do you report project status?"

"One page, same format every week: overall status, what's done, what's next, the top risks, and any decisions I need. I use red, amber and green honestly. An amber two weeks early is far more useful to a sponsor than a red the week before launch. For executives I lead with the decision; for the team I lead with what's changed."

11. "What is the critical path, and why does it matter?"

"It's the longest chain of dependent tasks, and it sets the earliest date the project can finish. A delay on it delays everything; tasks off it have some slack. If a critical task slips, I act that day. If a task with two weeks of slack slips by two days, it may not matter."

12. "How do you know whether a project succeeded?"

Go beyond "on time and on budget". A system delivered on time that nobody uses isn't a success. Agree success measures with the sponsor at the start (fewer support calls, a faster month-end close) and check them a few months after go-live.

Scenario questions

These put you in a situation and ask what you'd do. They want your reasoning, not a perfect answer. If the company runs structured interviews, expect several of these, asked the same way to every candidate.

13. "Your project is three weeks behind with six weeks to go. What do you do?"

"First I'd find out why, because the fix depends on the cause: a bad estimate, a blocked dependency, or people pulled onto other work. Then I'd go to the sponsor with options, not just bad news: cut or defer scope, add people where that genuinely helps, run tasks in parallel, or move the date. I'd recommend one and say what it costs. What I wouldn't do is keep reporting amber and hope the team catches up."

14. "Two senior stakeholders want opposite things. How do you handle it?"

"I'd meet each one separately to understand what they actually need, because positions are often further apart than needs. Then I'd bring them together with the trade-off written down: the options, what each costs, and what it means for the project's goal. If they still disagree, the sponsor decides, and I record the decision and the reason so it doesn't get reopened every week."

15. "A key team member keeps missing deadlines. What do you do?"

"Talk to them privately and early, and ask before assuming. It's often work from another manager, unclear requirements, or something personal. If it's workload, I'd talk to their line manager about priorities. If it's clarity, I'd break the task down with them and check in more often. If nothing changes, I'd raise it with their manager, with specifics, because the project can't keep absorbing the delay."

16. "A supplier tells you they'll deliver two weeks late. What's your first step?"

"Check whether their delivery is on the critical path. If it isn't, I'd adjust the plan and tell the team. If it is, I'd ask for a recovery plan or a partial delivery, see what we can do in parallel, check what the contract says about delays, and tell the sponsor the same day."

17. "Halfway through, you realise the project won't deliver the benefit it was approved for. What do you do?"

"Raise it with the sponsor, with evidence. Stopping or reshaping a project isn't failure if the reason for it has gone; finishing it anyway is usually the expensive option. I'd explain what changed and lay out the options: continue, change scope, pause or stop."

Behavioural questions

Answer these with STAR: Situation, Task, Action, Result. There are 30 more in our guide to behavioral interview questions.

18. "Tell me about a time you influenced people who didn't report to you."

"On a website relaunch, legal sign-off was the bottleneck: reviews were taking two weeks a page. I couldn't tell legal what to do, so I asked their lead what slowed reviews down. Pages were reaching them half-finished and then changing. We agreed I'd only send final drafts, in two batches a week, with changes highlighted. Reviews dropped to about three days."

19. "Tell me about a time you had to give a sponsor bad news."

"Two months into an eight-month programme, I realised our testing estimate was far too low. I told the sponsor at our next one-to-one instead of waiting for the monthly board, and brought the revised estimate, the reason, and two options: move the date by five weeks, or leave one of three regions out of the first release. She chose the second, and the rest of the plan held."

20. "Describe a time you ran several projects at once."

"Last spring I had an office move, a payroll system change and a training rollout running together. I ranked them by deadline risk and impact, gave the payroll change first call on my time, and sent one combined weekly update instead of three. The training rollout moved by two weeks, by agreement, and the other two landed on time."

21. "Tell me about a conflict in your project team."

"Two developers disagreed about whether to rebuild a module or patch it, and the argument was holding up the sprint. I asked each of them for half a page on cost, risk and time, then we met for 30 minutes and the tech lead decided: patch it now, rebuild next quarter. The point wasn't picking a winner; it was a decision both could live with."

Questions for senior and programme roles

• "How would you govern a programme of five related projects?" A steering group that actually decides things, one view of shared risks and dependencies, and a single reporting format.
• "How would you build project skills in a team that has none?" Templates people want to use, and pairing on the first project.
• "How do you decide which projects not to do?" Tie each one to the organisation's goals, compare value with effort, and stop work that no longer earns its place.

Questions to ask them at the end

Try "How are projects prioritised here, and who has the final say?" or "What happened on the last project that went badly?" The answers tell you how much authority the role really has. More in questions to ask at the end of an interview.

How to prepare in one evening

1. Read the job ad closely. Note the type of project, the methods and who you'd report to. The job description match tool shows which requirements your experience already covers.
2. Pick five project stories: one delivered end to end, one that went wrong, a stakeholder conflict, a change of scope, and a time you led people who didn't report to you.
3. Write them in STAR form with the STAR story builder, with the numbers: team size, budget, length, result.
4. Prepare your opener. Here's how to answer "Tell me about yourself".
5. Run a mock interview with two experience questions, two scenarios and one behavioural question. (How to run one on your own in 30 minutes.)
6. Afterwards, send a short thank-you email that mentions something you discussed.

Moving sideways? There are also practice sets for operations coordinators and business analysts.

Frequently asked questions

What are the most common project manager interview questions?

"Walk me through a project you managed", "How do you handle scope creep?", "Tell me about a project that didn't go to plan" and "How do you deal with stakeholders who disagree?", plus scenarios such as a project that's running late.

How do I answer if I've never had the job title?

Use projects you ran without the title: an event, a system rollout, an office move, a university project. Interviewers care about what you planned, decided and delivered.

Do I need a certification such as PMP or PRINCE2?

Not always. Some employers ask for one; many care more about evidence that you've delivered. Check the job ad, and if a certification is listed as preferred rather than required, strong project stories can still carry you.

What's the difference between project manager and project coordinator interviews?

Coordinator interviews focus on organisation, tracking and communication. Project manager interviews add decisions: trade-offs, budgets, risk and senior stakeholders. Prepare for both if you're stepping up.