Project Manager
Interview Questions
18 practice questions across 13 skills — each with what the interviewer is really listening for. Prepare with intent, not guesswork.
Free · No signup · Grouped by skill
How to use this page
Don't memorise answers. For each question, read what the interviewer is looking for, then practise answering out loud in your own words with a real example. The notes describe strong answers and common red flags — they are for your prep, not a script.
Project Planning
2 questionsWalk me through how you create a project plan for a project you have never done before.
IntermediateWhat the interviewer is looking for: Strong answers start from clear goals and scope, break work into a WBS, identify dependencies and milestones, and build in buffer for the unknown. Jumping to a Gantt chart without defining scope is a red flag.
A stakeholder keeps adding requirements mid-project. How do you handle scope creep?
IntermediateWhat the interviewer is looking for: Look for a change-control process that assesses impact on time, cost, and quality, and renegotiates trade-offs transparently. Silently absorbing every request or flatly refusing are both red flags.
Risk Management
2 questionsHow do you identify and prioritise risks at the start of a project?
IntermediateWhat the interviewer is looking for: A strong answer builds a risk register, scores by likelihood and impact, and assigns owners and mitigation plans. Treating risk management as a one-time checklist rather than ongoing is a red flag.
Tell me about a risk that materialised despite your planning. What did you do?
IntermediateWhat the interviewer is looking for: Look for early detection, executing a contingency plan, transparent communication, and lessons captured afterward. Blaming others or claiming they have never had a risk hit are red flags.
Budget Management
1 questionYour project is trending 15% over budget at the halfway point. What are your options?
AdvancedWhat the interviewer is looking for: Strong candidates diagnose the cause, then weigh re-scoping, re-sequencing, adding budget, or escalating with a clear recommendation. Hiding the overrun or hoping it corrects itself is a serious red flag.
Agile Methodology
1 questionHow do you decide whether a project should run Agile or a more traditional waterfall approach?
IntermediateWhat the interviewer is looking for: Look for matching the method to requirement stability, feedback needs, and regulatory constraints rather than dogma. Claiming Agile is always superior regardless of context is a red flag.
Scrum
1 questionWhat are the key Scrum ceremonies, and what goes wrong when a team skips the retrospective?
BasicWhat the interviewer is looking for: A strong answer names sprint planning, daily standup, review, and retro, and explains that skipping retros stops the team from improving. Reciting ceremonies without understanding their purpose is a red flag.
Stakeholder Management
1 questionYou have two stakeholders with directly conflicting priorities. How do you manage them?
AdvancedWhat the interviewer is looking for: Look for understanding each stakeholder's underlying goal, making trade-offs explicit, and escalating to a decision-maker when needed. Simply picking a side or avoiding the conflict are red flags.
Communication
1 questionHow do you keep stakeholders informed without drowning them in status updates?
BasicWhat the interviewer is looking for: Strong answers tailor cadence and detail to each audience, lead with status and asks, and flag risks early. One giant email to everyone or going silent until problems explode are red flags.
Leadership
2 questionsDescribe a time you led a team through a project that was falling behind. What did you do?
IntermediateWhat the interviewer is looking for: Look for taking ownership, rallying the team, removing blockers, and making hard prioritisation calls without blame. Micromanaging or blaming the team are red flags.
How do you motivate a team member who is disengaged but technically capable?
IntermediateWhat the interviewer is looking for: Strong candidates seek the root cause through a conversation, connect the work to what the person cares about, and adjust rather than just applying pressure. Assuming laziness without investigating is a red flag.
Jira
1 questionHow do you use Jira to track progress, and what metrics actually tell you a sprint is healthy?
IntermediateWhat the interviewer is looking for: Look for burndown, velocity trends, and cycle time used to spot blockers, not to punish individuals. Treating story points as a productivity score is a red flag.
Conflict Resolution
1 questionTwo senior engineers are in open conflict over a technical decision that is blocking the project. How do you resolve it?
AdvancedWhat the interviewer is looking for: Strong answers separate people from the problem, focus on shared goals and objective criteria, and facilitate a decision rather than imposing one. Ignoring the conflict or taking sides emotionally are red flags.
Time Management
1 questionHow do you estimate timelines when your team gives you wildly different estimates?
IntermediateWhat the interviewer is looking for: Look for probing assumptions behind estimates, using ranges and historical data, and building in buffer for uncertainty. Averaging blindly or committing to the optimistic number are red flags.
Problem Solving
1 questionA critical project is late and something has to give across scope, time, and cost. How do you decide?
AdvancedWhat the interviewer is looking for: Strong candidates use the iron triangle explicitly, understand which constraint the business values most, and present options with trade-offs. Promising to deliver everything anyway is a red flag.
Negotiation
1 questionHow do you run a negotiation with a vendor who wants to reduce scope after signing?
IntermediateWhat the interviewer is looking for: Look for understanding their constraints, anchoring on the agreement, seeking win-win alternatives, and knowing the walk-away point. Purely adversarial or immediately caving are both red flags.
Behavioural & role-general
2 questionsTell me about a project that failed or was cancelled. What did you learn?
BasicWhat the interviewer is looking for: Strong answers show honest reflection, ownership of their part, and concrete changes made afterward. Blaming everyone else or claiming they have never had a failure are red flags.
How do you define success for a project beyond just shipping on time?
BasicWhat the interviewer is looking for: Look for outcome-based measures — business value, stakeholder satisfaction, team health — not just on-time delivery. Defining success solely as hitting the deadline is a red flag.