Project Manager interview kit: questions and rubric

How to use this kit

1. Agree the competencies with the hiring manager before the job is posted.
2. Give each interviewer one or two competencies, so nothing is asked twice.
3. Ask every candidate the same core questions; follow up freely.
4. Rate each competency against the anchors straight after the interview, alone.
5. Debrief on quotes, not adjectives, then decide with the rule at the end.

First-round screen

Fifteen to twenty minutes, by phone, video or a disclosed AI screen. The aim is to confirm the basics before the panel spends its time.

1. What draws you to this role, and what kind of projects do you want to run next?
2. Tell me about the largest project you have managed end to end: the goal, the team or budget, the timeline, and how it finished against the plan.
3. Which delivery approaches and tools have you used at work (for example, plan-driven or agile methods, a scheduling tool, a work-tracking tool), and on what kinds of projects?
4. The job description sets out the location, working pattern, travel and start date. Do those work for you, what is your notice period, and what compensation range are you expecting?

1. Work sample (15 minutes): here is a one-page brief. A 40-person support team must move to a new ticketing tool in ten weeks, with data migration, training and no gap in service at go-live. Sketch the plan: the workstreams, the main milestones, the critical path, and what you would ask the sponsor before committing to the date.

   Follow up with

   • What does 'no gap in service' mean, and who decides?
   • Where is your contingency, and how much?
   • What is on the critical path?
   Strong answer

   Clarifies scope and success criteria first, splits the work into workstreams (configuration, migration, integrations, training, cutover), sequences the dependencies, and finds the critical path through the migration test cycles. Includes contingency, a cutover and rollback plan, and states the assumptions the date rests on.

   Weak answer

   Produces a task list with dates but no dependencies, accepts the ten weeks without question, leaves no contingency, or forgets training and cutover.

2. Tell me about a project where the scope was unclear at the start. How did you pin it down?

   Follow up with

   • What did you put out of scope, and how did you get agreement?
   • What happened when someone asked for more later?
   Strong answer

   Wrote down what was in and out of scope and how acceptance would be judged, got the sponsor to agree it, and set up a simple route for later requests. Gives an example of a request handled through it.

   Weak answer

   Started work without agreement and absorbed additions as they came, or wrote a charter nobody read and never used again.

1. Tell me about a risk you spotted early that would have hurt the project if you had not acted.

   Follow up with

   • How did you find it?
   • What did acting on it cost?
   • How did you know the risk had passed?
   Strong answer

   Names a specific risk, its likelihood and impact, an owner, and a mitigation that was actually carried out, with a trigger for escalating. Distinguishes a risk from an issue that has already happened.

   Weak answer

   Describes the risk log as paperwork, gives an example that was already an issue, or says 'we tracked it' with nothing done.

2. It is week three. Your project depends on another team's integration, due in week six. Their lead says it is 'on track', but you have seen nothing working. What do you do?

   Follow up with

   • What would you ask to see, and when?
   • What is your fallback if it is late?
   • When would you escalate, and to whom?
   Strong answer

   Asks for evidence such as a demo or a test environment, agrees interim checkpoints, plans a fallback (a stub, re-sequenced work), and agrees in advance when a missed checkpoint goes to the sponsors. Keeps the relationship cooperative.

   Weak answer

   Trusts 'on track' until week six, or escalates to the other team's manager at once and damages the relationship.

1. Tell me about a time you had to tell a sponsor something they did not want to hear.

   Follow up with

   • How soon after you knew did you tell them?
   • What did you recommend?
   • What happened to the relationship?
   Strong answer

   Told the sponsor early, with the facts, the impact on date or cost, and options with a recommendation. Kept their trust because nothing arrived as a second surprise.

   Weak answer

   Waited to see whether the team could recover, softened the message until it meant nothing, or brought the problem with no options.

2. A functional manager keeps pulling 'their' people off your project for day-to-day work. You have no line authority over them. What do you do?

   Follow up with

   • What would you say to the manager?
   • When does it go to the sponsor?
   Strong answer

   Understands the manager's pressures, shows the impact on the project's dates, agrees an allocation in writing, and escalates to the sponsor with the data only if that fails. Keeps it about the work, not the person.

   Weak answer

   Absorbs the loss quietly and lets the date slip, or goes over the manager's head before talking to them.

1. Scenario (15 minutes), 'the plan just slipped': it is week seven of the ten-week ticketing project. The migration test has failed: 18% of historical tickets lost their attachments, and the vendor says a fix needs two weeks. The contract for the old tool ends in week eleven. Talk me through the next 48 hours. (Interviewer brief: if asked, the old tool can be extended month by month at a cost, attachments older than two years are rarely opened, and training is on track.)

   Follow up with

   • What do you tell the sponsor today, and what do you need from them?
   • Which options would you put in front of them?
   • What would you change so the next slip is not a surprise?
   Strong answer

   Confirms the facts and the impact first (which tickets, how many matter, whether the vendor estimate is credible). Builds options, such as going live with recent tickets and migrating the archive later, extending the old tool for a month, or adding vendor effort, each with its cost, risk and date. Tells the sponsor the same day with a recommendation, re-baselines through change control, and tells the support team what changes for them.

   Weak answer

   Promises to make up the time by squeezing testing or adding overtime, waits for the next steering meeting, or moves the date at once without exploring scope options.

2. Tell me about a project that missed its original date or budget. What happened, and what did you do once you knew?

   Follow up with

   • When did you first see the signs?
   • What would you do differently at the start?
   Strong answer

   Owns their part, says when the warning signs appeared and how quickly they acted, describes the options considered and the re-plan, and names a practice they changed afterward.

   Weak answer

   Blames the vendor or the team, describes no early warning, or claims never to have missed a date.

1. Work sample (10 minutes): here are this week's notes: two tasks late, a vendor invoice dispute, the test environment down for three days, and training ahead of plan. Write the three-line summary that opens the weekly status report for the sponsor, and give it a status color.

   Follow up with

   • Why that color?
   • What do you need from the sponsor, and by when?
   Strong answer

   Leads with the overall status and what it means for the date, picks an honest color and explains it, names the one decision or help needed from the sponsor and by when, and leaves out detail that changes nothing.

   Weak answer

   Marks it green with the bad news buried in bullets, lists activity rather than impact, or makes no request of the sponsor.

2. Your weekly project meeting has 14 attendees, runs past an hour, and decisions keep being reopened. What would you change?

   Follow up with

   • How would decisions be recorded?
   • What would you move out of the meeting entirely?
   Strong answer

   Gives each meeting one purpose, moves routine status to a written update, keeps a smaller decision meeting for the people who own decisions, sends an agenda listing the decisions needed, and records decisions, owners and dates the same day.

   Weak answer

   Adds another meeting, or cancels the meeting without replacing what it did. Has no way to stop decisions being reopened.

Never ask

• Don't ask a candidate's age, or their graduation year to work it out. Why: age says nothing about delivery skill, and age-based decisions are unlawful in many places.
• Don't ask about marital status, children, pregnancy or family responsibilities to judge whether they can handle long hours or travel. Why: none of it is job-related. Describe the hours and travel and ask every candidate whether they can meet them.
• Don't ask about religion, caste, community or the origin of a surname, directly or by proxy ('What does your father do?'). Why: in India these questions signal caste and religion, which have no bearing on the job.
• Don't ask 'Where are you from originally?' or 'What is your native place?'. Why: it invites judgments about region and community. If location matters, ask whether the candidate can work from the job's location.
• Don't ask about health conditions, disabilities or past medical leave. Why: the only relevant question is whether the candidate can perform the essential functions of the job, with or without reasonable accommodation.
• Don't ask whether the candidate has ever been arrested. Why: an arrest is not a conviction, and many US states and cities restrict criminal-history questions until after a conditional offer. Where the law requires a background or police verification check for the role, run it through that process after the offer.
• Don't ask for salary history where the law restricts it, as many US states and cities do. Why: it carries past pay gaps into the new offer. Ask for the expected compensation range instead.
• Don't make a PMP, PRINCE2 or Scrum certificate a pass-or-fail screen unless a client contract requires it. Why: certificates show study of a method, not delivery. The planning exercise and the slipped-plan scenario show the skill directly.

Questions people ask

What is the difference between a project manager, a product manager and an operations manager?

A product manager decides what to build and why. An operations manager runs an ongoing operation and its team. A project manager delivers a defined result to an agreed date, budget and scope through people from other teams, then closes the project, so this kit tests planning, risk and delivery under change.

Should we require a PMP or PRINCE2 certification for a project manager?

Only if a client contract or a regulator requires it. PMP is common in the US and India, PRINCE2 in the UK and parts of Europe, and both show knowledge of a method. Neither shows whether someone can deliver, so assess that directly with the exercises.

How do we interview a project manager for agile teams?

Keep the competencies and change the examples. In agile delivery, planning looks like release goals and an ordered backlog, and status shows progress against outcomes rather than a task list. Ask how the candidate handled fixed dates or budgets alongside iterative delivery, since most organizations combine the two.

Does a project manager need technical or industry knowledge?

Enough to judge whether an estimate is credible and which risks are likely. A project manager for a data migration should know what a test cycle involves; one for an office move should know leases and suppliers. Decide the depth before the loop and test it inside the scenarios, not with a quiz.