Interview questions for project management skills: 14 questions and a 1–4 scale

Interview questions for project management skills are not only for project managers. Plenty of roles run projects without the title: a recruiter organizing a hiring event, a marketer running a launch, an operations lead moving to a new system. What these have in common is multi-week work involving other people, with a deadline and a definition of done. Below are fourteen questions, ten behavioral and four situational, with follow-up probes, plus a plan-review exercise, illustrative strong and weak answers, a 1–4 anchored scale and common interviewer mistakes.

This is a competency page, not a role screen. If you are hiring a dedicated project manager, the project manager phone screen questions cover methodology, budget ownership and certifications. Project management is also distinct from prioritization, which is choosing among competing work, and time management, which is how candidates run their own day.

Project management skills, defined as something you can observe

Definition: project management is delivering a defined outcome by a date, through other people's work, by scoping it, planning it, tracking it and handling change. Four behaviors make it visible:

• Defining done. Agreeing the outcome, scope and success measure with the people who care, before work starts.
• Planning dependencies and risks. Knowing which tasks depend on which, who owns each, where the schedule has no slack, and what is most likely to go wrong.
• Tracking and reporting honestly. Knowing early when the plan is slipping, and telling stakeholders while there is still time to act.
• Controlling change. Handling new requests by making the trade-off in time, scope or resources visible, rather than absorbing them silently.

Ten behavioral questions, with follow-up probes

1. Tell me about the most complex project you ran from start to finish.
   Probes: How did you define done at the start? Who agreed to that definition?
2. Describe planning a project with many dependencies.
   Probes: Which sequence of tasks had no slack? What did you do to protect it?
3. Tell me about a risk you spotted before it became a problem.
   Probes: How did you spot it? What did you do in advance, and what did that cost?
4. Describe a project that slipped.
   Probes: When did you first know? When did you tell stakeholders, and what did you say?
5. Tell me about a time the scope changed partway through.
   Probes: How did you handle the request? What was traded to make room?
6. Describe how you tracked progress on a recent project.
   Probes: What did you look at each week? What would have told you it was off track?
7. Tell me about a project that depended on people who did not report to you.
   Probes: How did you get commitments from them? What did you do when one was missed?
8. Describe recovering a project that was in trouble.
   Probes: What options did you put in front of the sponsor? Which did they choose, and why?
9. Tell me about a project you paused or stopped.
   Probes: What told you it should stop? Who did you have to persuade?
10. Describe what you did when a project finished.
    Probes: What did you hand over, and to whom? What did you change about how you run projects afterward?

Four situational questions, including a plan review

11. The plan-review exercise, described below.
    Probes: Which issue would you fix first? What would you ask the sponsor before changing anything?
12. "Two weeks before launch, a key person on the project goes on unexpected leave."
    Probes: What do you do on the first day? Who do you tell, and what do you tell them?
13. "In the final week, a senior stakeholder adds what they call a small requirement."
    Probes: What do you need to know about it? What do you say if it is not small?
14. "You are asked to commit to a launch date before the scope has been agreed."
    Probes: What would you commit to, if anything? How would you phrase it?

A plan-review exercise

Give the candidate a short plan with a few problems built in, and five minutes to review it. For example, a plan to run a campus hiring program in six weeks:

The planted issues: venue booking has no owner and comes late, when campus slots may already be gone; the materials cannot be finished without knowing the venues and dates; hiring managers' availability for week 5 has not been confirmed; there is no headcount or offer approval step; there is no buffer; and "done" is never defined, such as how many hires or accepted offers. Strong candidates find most of these, ask what success means before suggesting fixes, and reorder the plan around the dependencies. Weaker candidates comment on formatting or add tasks without questioning the sequence. Swap in a plan from your own team's work for a more realistic version.

What strong and weak answers sound like

These are illustrative answers to question 4, written to show the difference in shape rather than quoted from real candidates.

Weak: "We had a system migration that ran late because the vendor kept missing deadlines. We worked really hard in the last few weeks, pulled some late nights and got it over the line only a couple of weeks behind."

The slip is blamed on someone else, there is no sign of when it was first visible, and the recovery was effort rather than a decision. Probe when the first vendor deadline was missed and who was told.

Strong: "Three weeks into an eight-week migration, the vendor missed the first data export date. On its own it was only a few days, but every later step depended on it, so I treated it as a warning. I told the sponsor that week that we were at risk of slipping two weeks and gave her two options: keep the date and launch without historical reports, or move the date. She chose to move it. I also added a weekly check-in with the vendor's technical lead rather than the account manager. We launched on the revised date."

The strong answer recognizes an early signal on the critical path, reports it while there is still a choice, frames the trade-off for the decision-maker, and changes how the dependency is managed.

A 1–4 anchored rating scale for project management skills

For the reasoning behind anchored scales, see our guide to interview rating scales. The behavioral anchors library includes planning and delivery wording you can adapt, and the free scorecard builder will put this next to prioritization as separate lines.

Common interviewer mistakes with project management skills

• Scoring methodology vocabulary. Sprints, stand-ups and status colors are easy to describe. Ask what the candidate did when the status should have changed color.
• Scoring on-time delivery alone. On-time can mean a padded schedule or quietly dropped scope. Probe what changed between the original plan and the final delivery.
• Accepting "we delivered." Many candidates worked on well-run projects without running them. Ask who built the plan and who told the sponsor when it slipped.
• Treating a certification as the competency. Record it if the role requires it, but score what the candidate did on real projects.
• Mixing it with prioritization. Agree in advance which questions feed which line, so one story about a busy quarter is not scored twice.