Skip to content

21 interview questions

Project manager interview questions and answers

Project manager interviews focus on how you plan, how you react when plans fail and how you keep people aligned. Expect questions on methods and tools, scenario questions about slipping schedules and scope creep, and many behavioral questions about projects you have run.

Updated

Planning and methodology

01Walk me through how you start a new project.

What they want to hear: A repeatable approach that defines the goal and scope before work begins.

Answer outline

  1. Clarify the objective, success criteria and sponsor.
  2. Identify stakeholders and agree scope, including what is out of scope.
  3. Break the work down (a work breakdown structure), estimate it and build a schedule with dependencies.
  4. Agree roles, communication rhythm and how changes will be handled, then hold a kickoff.

02When would you use agile and when would you use a waterfall approach?

What they want to hear: That you choose the method to fit the work instead of following one by habit.

Answer outline

  1. Waterfall suits work with stable, well-understood requirements and fixed dependencies, such as regulated or construction-style projects.
  2. Agile suits work where requirements will change and early feedback is valuable, such as software products.
  3. Many projects use a hybrid: fixed milestones with iterative delivery inside them.
  4. Give an example of a choice you made and why.

03How do you estimate a project's timeline?

What they want to hear: Realism, involvement of the people doing the work, and honest handling of uncertainty.

Answer outline

  1. Estimate with the people who will do the work, at the task level.
  2. Use past projects as a reference and ranges rather than single numbers for uncertain tasks.
  3. Map dependencies and find the critical path.
  4. Add contingency based on identified risks, and state the assumptions behind the estimate.

04What is the critical path, and why does it matter?

What they want to hear: A basic scheduling concept every project manager should explain clearly.

Answer outline

  1. The longest chain of dependent tasks from start to finish; it sets the shortest possible project duration.
  2. Tasks on it have no float: any delay delays the whole project.
  3. It tells you where to focus attention, resources and risk management.
  4. It can change as tasks finish early or late, so you recheck it during the project.

Scope, risk and change

05How do you handle scope creep?

What they want to hear: A change control habit that protects the project without making you the department of no.

Answer outline

  1. Have a clear, agreed scope baseline from the start.
  2. Route every new request through a simple change process.
  3. Assess impact on time, cost and quality, and present options to the sponsor.
  4. Record the decision and update the plan and stakeholders.

06How do you identify and manage project risks?

What they want to hear: Proactive risk management, not a register filled in once and forgotten.

Answer outline

  1. Identify risks with the team and stakeholders early, and keep doing it.
  2. Assess likelihood and impact and give each important risk an owner.
  3. Choose a response: avoid, reduce, transfer or accept, with a trigger for action.
  4. Review the register in regular meetings and report the top risks.

07Tell me about a risk that became a real problem. What did you do?

What they want to hear: How you act when a risk materialises and what you learn from it.

Answer outline (STAR)

  1. The risk and whether it had been identified.
  2. The impact when it happened.
  3. Your response: who you told, what you changed, how you recovered.
  4. What you changed in your risk process afterwards.

08Your project is two weeks behind schedule. What do you do?

What they want to hear: Calm diagnosis, real options and early, honest communication.

Answer outline

  1. Find the cause and confirm the real size of the delay.
  2. Look at options: re-sequence work, fast-track tasks in parallel, add resources where they help, or reduce scope.
  3. Present the options with trade-offs to the sponsor, with a recommendation.
  4. Update the plan and track recovery closely.

Stakeholders and communication

09How do you keep stakeholders informed?

What they want to hear: A communication plan that fits each audience, not one status email for everyone.

Answer outline

  1. Map stakeholders by interest and influence.
  2. Agree format and frequency with each group: executive summaries, detailed team updates, steering meetings.
  3. Report status honestly with clear red, amber and green criteria.
  4. Raise bad news early with a plan attached.

10Tell me about a time you managed a difficult stakeholder.

What they want to hear: Your ability to understand what drives someone and work with them productively.

Answer outline (STAR)

  1. Who they were and what made the situation hard.
  2. How you found out what they cared about.
  3. What you changed in how you worked with them.
  4. The result for the project and the relationship.

11Two senior stakeholders want conflicting things. How do you resolve it?

What they want to hear: Facilitation and escalation skills, and knowing who has the authority to decide.

Answer outline

  1. Understand each position and the goal behind it.
  2. Show the impact of each option on the project objectives.
  3. Look for a solution that meets both goals; if none exists, take it to the sponsor or steering group to decide.
  4. Record the decision and communicate it.

12How do you report a project in trouble to an executive sponsor?

What they want to hear: Courage and clarity. Hiding problems is the main thing they want to avoid.

Answer outline

  1. Lead with the status and the impact in one or two sentences.
  2. Explain the cause briefly.
  3. Give options and your recommendation.
  4. Say what decision or support you need and by when.

Team and delivery

13How do you motivate a team you do not directly manage?

What they want to hear: Influence without authority, which is most of the job.

Answer outline

  1. Make the goal and its importance clear.
  2. Agree responsibilities and deadlines with people rather than for them.
  3. Remove blockers quickly and give credit openly.
  4. Work with line managers when there is a capacity or performance issue.

14A team member keeps missing deadlines. What do you do?

What they want to hear: Fairness and directness: understanding the cause before acting.

Answer outline

  1. Talk to them privately and find out what is happening.
  2. Check whether the estimates, priorities or workload are the real problem.
  3. Agree a plan and check in more often.
  4. If it continues, involve their line manager and adjust the plan.

15How do you track progress on a project?

What they want to hear: Concrete tools and measures, not just 'regular meetings'.

Answer outline

  1. Milestones and deliverables with clear definitions of done.
  2. A schedule or board updated by the team, plus burn-down or earned value where it fits.
  3. Budget tracking against plan.
  4. Short regular check-ins focused on blockers and risks.

16Which project management tools have you used, and how?

What they want to hear: Practical experience, and the sense to use tools to serve the work.

Answer outline

  1. Name the tools you have used for planning, tracking and documentation.
  2. Explain how you set them up for a specific project.
  3. Show you can adapt to the team's tools rather than forcing your own.

17How do you close a project?

What they want to hear: Discipline at the end of the project, when attention usually drops.

Answer outline

  1. Confirm deliverables are accepted against the success criteria.
  2. Hand over to operations or support with documentation.
  3. Close contracts and budgets and release the team.
  4. Run a lessons learned session and share the results.

Experience and judgment

18Tell me about the most complex project you have managed.

What they want to hear: The scale you can handle and how you deal with complexity.

Answer outline (STAR)

  1. Scope, budget, team size and duration.
  2. What made it complex: dependencies, vendors, stakeholders, technology.
  3. The approach you took to keep it under control.
  4. The outcome against time, budget and goals.

19Tell me about a project that failed or went badly.

What they want to hear: Honesty and learning. Every experienced project manager has one.

Answer outline (STAR)

  1. What the project was and what went wrong.
  2. Your part in it, stated plainly.
  3. What you did to limit the damage.
  4. What you do differently now.

20Describe a time you had to deliver with a cut budget or fewer people.

What they want to hear: Prioritisation and negotiation under constraint.

Answer outline (STAR)

  1. The constraint and when it arrived.
  2. How you re-planned and agreed what to cut with the sponsor.
  3. How you kept the team focused.
  4. What you delivered and how it was received.

21Tell me about a time you had to make a decision without all the information.

What they want to hear: Judgment, timing and willingness to own a decision.

Answer outline (STAR)

  1. The decision and the deadline.
  2. What you knew, what you did not, and the risk of waiting.
  3. How you decided and who you consulted.
  4. The result and how you followed up.

How to prepare

  • Prepare three or four project stories with real numbers: budget, team size, duration and how the result compared with the plan.
  • Be ready to explain the terms you use, such as critical path, RACI, earned value, sprint and change control, in plain language.
  • Show both sides of the job in your answers: the plan and the people. Interviewers want to hear about both.
  • Have a clear example of delivering bad news early. It is one of the most common things project managers are judged on.
  • If you hold a certification, connect it to how you work rather than just naming it.

Practice these questions out loud with NORDON

Reading answers is not the same as saying them. NORDON's interview practice asks you questions written for the role, listens to your spoken answer and shows you how to make it stronger.

  1. Upload your CV in the Knowledge base, so questions and feedback use your real background.
  2. Open Practice, enter the role (for example project manager), paste the job ad if you have it, and choose 3, 5, 8 or 10 questions and the answer language.
  3. Listen to each question and answer out loud, as you would in the room. You can also type an answer.
  4. Get a score from 1 to 10, what worked, what to improve and a stronger answer to rehearse. It uses only what you said and your documents, and leaves a [placeholder] where a fact about you is missing.
  5. Try the question again, or move on. For a dress rehearsal, run a mock call where an interviewer voice asks the questions out loud.

The free plan includes 10 scored practice answers a month and mock calls of up to 10 minutes, no card needed. Paid plans include more practice and mock calls of up to 30 minutes. How practice works

Practice is for preparing. Use live help in a real interview only where the interviewer allows AI assistance, never in an interview, test or assessment whose rules forbid it.

NORDON for job interviews

Preparing for your project manager interview

Do I need a certification to get a project manager job?

Not always. Some employers and industries ask for one, others value proven delivery more. If the job ad lists one, mention yours or explain how your experience covers the same ground.

What should I bring to a project manager interview?

Copies of your CV, a short list of the projects you plan to talk about with key figures, and questions about how the company runs projects. Some candidates bring an example plan or status report with confidential details removed.

How technical do I need to be for an IT project manager role?

Enough to understand the work, ask good questions and judge estimates and risks. You are rarely expected to do the technical work yourself, but you should speak the team's language.