Project Manager Interview Questions
20 questions
Question 1: Describe a time you helped project stakeholders agree on requirements when they wanted different things.
What interviewers listen forA strong example shows how they surfaced the disagreement, clarified project requirements, and reached agreement. Blaming a stakeholder without explaining their own actions is a warning sign.
Candidate tipChoose one disagreement over project requirements. Focus on the questions you asked, the agreement you helped reach, and what it meant for the project.
Question 2: Tell me about a time you adjusted a project schedule after a task slipped and put later work at risk.
What interviewers listen forThe example should connect the slipped task to dependent work and explain the revised sequence. Simply moving the final date without checking downstream effects is a warning sign.
Candidate tipPick a delay that affected later project activities. Walk through the dependencies, the schedule choices you made, and whether the revised schedule held.
Question 3: How do you work out the staffing and funding a project needs from its objectives and schedule?
What interviewers listen forListen for a link between the work, required skills, staff availability, and cost assumptions. Guessing a head count without checking the schedule leaves the estimate unsupported.
Candidate tipWalk through how you turn project work and deadlines into staffing and funding needs. Name the availability checks and assumptions behind your estimate.
Question 4: Walk me through a time you worked with project team members to resolve a problem they could not fix on their own.
What interviewers listen forListen for how they drew on the team's knowledge to find the cause and remove the obstacle. Taking all the credit without showing the team's part weakens the example.
Candidate tipSet out the problem blocking the team. Describe your part in getting the right people together, testing possible fixes, and checking that work could continue.
Question 5: How do you build a project plan that shows task owners how their work supports the project's objectives?
What interviewers listen forListen for objectives broken into deliverables and tasks, with owners, dates, and resource needs tied to the work. A task list with no link to the project's objectives leaves the team without a clear purpose.
Candidate tipWalk through how you turn project objectives into a usable plan. Explain how you connect deliverables, tasks, owners, dates, and resource needs so team members can see their part.
Question 6: Give an example of how you evaluated a requested change to a project that was already underway.
What interviewers listen forA strong example weighs the change against scope, time, resources, and cost before a decision. Starting extra work while bypassing required approval is a warning sign.
Candidate tipUse one change request. Explain the effects you checked, your recommendation, and how the decision was reflected in the project plan.
Question 7: Share an example of a time a project update was too vague for you to tell whether a deadline was still realistic.
What interviewers listen forA useful example names the missing facts, the candidate's follow-up, and what the clearer update revealed. Treating 'on track' as enough despite missing evidence is a red flag.
Candidate tipRecall a vague update from a project task owner. Explain what you asked them to clarify and how that changed your view of the deadline.
Question 8: How do you check that a project milestone is actually complete rather than just reported as complete?
What interviewers listen forLook for agreed completion criteria, evidence of the finished work, and confirmation of unresolved items. A status label alone does not prove the milestone is complete.
Candidate tipExplain the evidence you compare with the milestone's completion criteria. Describe how you record work that remains open rather than counting it as finished.
Question 9: Tell me how you handled pressure from a project sponsor to send a client deliverable before it passed an agreed quality check.
What interviewers listen forA strong example shows how they explained the failed check, weighed the deadline pressure, and handled client delivery. Claiming the deliverable passed while hiding a failed check is a red flag.
Candidate tipChoose a real delivery decision involving sponsor pressure and a failed quality check. Focus on your actions, what was agreed about sending the deliverable, and the result for the client.
Question 10: How do you prepare a project budget estimate when some costs are still uncertain?
What interviewers listen forLook for a basis for the estimate, clearly stated assumptions, and visible uncertainty. Presenting an unsupported guess as a firm cost is a red flag.
Candidate tipDescribe how you build the estimate from expected project costs. Explain how you document assumptions and show which costs still need firmer figures.
Question 11: Tell me about a time you spotted project staff costs rising faster than planned.
What interviewers listen forA strong case traces the cost increase to staff time or rates and shows what the candidate did with that finding. Ignoring recorded costs to keep the budget looking healthy is a red flag.
Candidate tipUse a real staff cost increase. Explain the records you checked, what caused the gap from the plan, and the action you took before describing the result.
Question 12: Give an example of how you cleared up overlapping responsibilities on a project team.
What interviewers listen forThey should show how they resolved competing ownership and made responsibilities clear to the people doing the work. Leaving two people assuming the other owns a task is a warning sign.
Candidate tipChoose a project where ownership overlapped. Describe how you clarified the work, assigned responsibility, and checked that team members understood their roles.
Question 13: Talk about a time you negotiated for project resources that another team or project also needed.
What interviewers listen forThe answer should show the competing needs, the candidate's negotiation, and the resource agreement reached. Promising staff time they had no authority to commit is a warning sign.
Candidate tipSet up the resource conflict and your project's need. Focus on the options you offered, the agreement you reached, and whether it gave the project usable support.
Question 14: Walk me through a time you had to report a project risk to a manager who expected the project to be on track.
What interviewers listen forThey should give the manager a clear risk, its likely effect, and any decision needed. Withholding a known risk to avoid an uncomfortable conversation is a red flag.
Candidate tipPick a real status report with unwelcome news. Focus on how you explained the risk, the support or decision you needed, and the manager's response.
Question 15: Describe a time you made a project status presentation clear for a customer who did not know the technical details.
What interviewers listen forListen for changes to the presentation that helped the customer understand progress and open issues. Hiding a problem behind technical language is a red flag.
Candidate tipUse one customer presentation. Explain which technical details you translated or left out, how you made the project status clear, and what showed the customer understood.
Question 16: Share an example of how you evaluated a vendor's proposal when you doubted they could meet your project's requirements.
What interviewers listen forListen for the checks they personally made on the vendor's claims and how those findings shaped the selection decision. Accepting an unsupported promise as proof of capacity is a red flag.
Candidate tipUse one proposal that raised doubts. Describe the project requirement at stake, the evidence you sought from the vendor, and how your findings affected the selection decision.
Question 17: Share an example of a time you gave a project team member feedback about missed commitments.
What interviewers listen forListen for feedback grounded in specific commitments, a chance for the team member to explain, and follow-up. Attacking the person's character instead of addressing the work is a red flag.
Candidate tipChoose a real feedback conversation. State the missed commitments, the feedback you personally gave, and what happened when you followed up.
Question 18: Describe a time you brought a project meeting back on track when the team was not reaching a needed decision.
What interviewers listen forListen for how they clarified the decision, focused the discussion, and recorded an outcome or next step. Recording agreement that team members did not give is a red flag.
Candidate tipRecall a meeting that was going in circles. Explain how you focused the discussion and what decision or clear next step the team left with.
Question 19: How do you keep project team members working from the current version of project documents?
What interviewers listen forA competent answer covers version identification, a clear place for current documents, and notice of changes. Circulating conflicting copies with no way to identify the current one is a red flag.
Candidate tipWalk through how you label, store, and distribute project documents. Explain how team members learn about changes and avoid using an outdated copy.
Question 20: How do you assess whether a candidate has the skills needed for a role on a project with a fixed end date?
What interviewers listen forListen for assessment against the actual project work, evidence of the needed skills, and availability for the assignment. Choosing solely on a job title leaves their ability untested.
Candidate tipLink the project role to specific work and skills. Explain how you would gather evidence of those skills and check that the candidate can cover the assignment.