Questions on planning, risk management, stakeholder communication, and delivering projects on time and budget.
Show flexibility by naming different methodologies you have used and the specific context that made each one the right choice.
Strong answers show experience with multiple approaches (Agile, Waterfall, hybrid, Kanban) and a practical framework for choosing: fixed scope and regulatory requirements may suit Waterfall, evolving requirements suit Agile, ongoing operations suit Kanban. Best candidates adapt methodology to context rather than dogmatically following one approach.
Tests practical experience and adaptability. Red flag: only knowing one methodology or being dogmatic about Agile. Good sign: pragmatic approach that considers team, stakeholders, and project characteristics.
Show your change control process: document the request, assess impact on timeline and budget, present options to stakeholders, and get sign-off before proceeding.
Look for: clear scope definition upfront, change request processes, impact assessment before accepting changes, transparent communication with stakeholders about trade-offs (scope vs time vs budget), and ability to push back diplomatically. Strong candidates show that controlled scope changes can be positive when managed properly.
Core PM skill. Candidates who never push back on scope are not managing; candidates who always block changes are not serving stakeholders. Look for the balanced approach.
Show that you assess risks at the start AND review them regularly. A risk register that is only updated at kickoff is not risk management.
Strong answers include: proactive risk identification (brainstorming, pre-mortems, lessons learned from past projects), risk assessment (probability and impact matrix), mitigation strategies for top risks, contingency plans, regular risk reviews, and escalation criteria. Best candidates mention that some risks are opportunities.
Tests foresight and planning discipline. Ask for a specific example where early risk identification saved a project. Candidates who only manage risks reactively are firefighters, not project managers.
Present stakeholders with options and trade-offs, not just the problem. "We can do A with reduced scope, B with a delayed timeline, or C with additional resources."
Strong answers: assess the impact on timeline and deliverables, identify alternatives (redistribute work, bring in contractors, reduce scope), communicate the impact transparently to stakeholders, negotiate for replacement resources or timeline extension, and document the decision and its rationale.
Tests problem-solving and communication under pressure. Weak candidates panic or accept the situation passively. Strong candidates present options and facilitate a decision.
Tailor your format to the audience. Executives want a one-line status and decisions needed. Teams want detailed plans and blockers resolved.
Look for: tailored communication for different audiences (executives want outcomes, team wants details), regular cadence (weekly updates, monthly reviews), clear format (RAG status, key decisions needed, risks), and proactive bad news delivery. Best candidates mention the difference between informing and engaging stakeholders.
Communication is the PM's primary tool. Ask to see a sample status report or describe their format. Red flag: only communicating when there is a problem. Good sign: consistent, proactive, tailored communication.
Focus on when you recognised the problem, what you did about it, and what you changed for future projects. Recovery is more impressive than perfection.
Best answers show: early recognition of problems (not waiting until disaster), transparent communication with stakeholders, root cause analysis, corrective actions taken, and lessons learned. Look for accountability rather than blame-shifting. The recovery plan matters more than the failure.
Every PM has had a project go wrong. The question is how they handled it. Red flag: never having a project fail (either very junior or not honest). Good sign: honest reflection and systemic changes made.
First diagnose whether the issue is motivation, clarity, or capacity. Each requires a different intervention. Do not assume it is always about morale.
Strong answers show empathy and action: understanding the root cause (overwork, unclear direction, interpersonal conflict), addressing it directly, celebrating small wins, removing blockers, and protecting the team from external pressure. Best candidates distinguish between motivation problems and skill/resource problems.
Tests leadership and emotional intelligence. PMs who cannot motivate teams rely on authority, which does not scale. Look for genuine care and practical solutions, not just cheerleading.
Do not just say no - show them the impact. "We can add this, but it moves delivery by two weeks and costs X. Shall we proceed?"
Look for: understanding why they keep changing (unclear vision, political pressure, new information), structured change management, regular alignment meetings to reduce surprises, showing the impact of changes on timeline and budget, and building a relationship that allows honest pushback.
Tests diplomatic backbone. PMs who accept all changes are order-takers. PMs who block all changes are gatekeepers. The best PMs facilitate informed decisions by showing trade-offs.
Frame your answer around risk management: Waterfall reduces certain risks (scope uncertainty) while accepting others (late feedback). Show you understand the trade-off.
Strong answers identify valid Waterfall scenarios: regulatory compliance requiring documentation, fixed-scope contracts, hardware dependencies with long lead times, or projects where requirements are truly stable. Best candidates justify based on risk reduction and stakeholder needs, not personal preference.
Tests critical thinking and ability to challenge orthodoxy. In an Agile-dominant industry, can they think independently? Conversely, Waterfall purists who dismiss Agile are equally concerning.
Document everything, over-communicate in async channels, and make time zone differences an advantage (handoff workflows) rather than a friction.
Look for: intentional communication practices (over-communicate in async, regular video calls), virtual team-building activities that respect time zones, clear documentation and shared tools, trust-based management (outcomes over activity), and attention to inclusion for team members in different locations.
Increasingly important skill. Candidates who default to "everyone should be in the office" may struggle with modern distributed teams. Look for practical experience, not just theory.
Track your estimate accuracy over time. If you are consistently 30% over, build that into your buffer. Data-driven estimates beat optimistic guesses.
Strong answers include: breaking work into small tasks, using historical data and velocity, adding buffers for unknowns, distinguishing between effort and duration, involving the team in estimation, and tracking estimate accuracy over time. When estimates are wrong: communicate early, assess impact, propose options, and learn for future estimates.
Core PM skill. Candidates who always estimate optimistically are dangerous. Those who always pad excessively are wasteful. Look for evidence-based estimation and honest communication when things go wrong.
Build vendor delays into your risk register from day one. Have a contingency plan for the most critical vendor dependency - what do you do if they are two weeks late?
Look for: clear contracts and SLAs, regular communication cadence, risk mitigation for vendor delays, escalation paths, and contingency plans. Best candidates discuss how they protect the project from vendor failures while maintaining productive relationships and how they manage internal stakeholders' expectations around external dependencies.
Senior PM skill. Many projects fail because of unmanaged external dependencies. Candidates who treat vendors like internal teams (always available, always on time) will be caught off guard.
The value of a lessons learned session is zero if the lessons are not applied. Show how you turned a specific insight into a concrete process change for the next project.
Strong answers describe: structured retrospectives at project end (and at milestones), creating a safe space for honest feedback, capturing both what went well and what did not, converting insights into actionable changes, and actually applying lessons to future projects. Best candidates have examples of specific improvements that came from retrospectives.
Tests learning culture. Many teams do retrospectives but never change. Candidates who can trace a process improvement back to a specific lesson demonstrate genuine continuous improvement.
Make dependencies visible. A dependency that only exists in someone's head is a risk. Use a visual dependency map that is reviewed weekly.
Look for: dependency mapping at planning stage, regular cross-team sync meetings, buffer time at integration points, clear ownership of interfaces, and early warning systems when a dependency is at risk. Best candidates use visual dependency maps and integrate dependency risk into their status reporting.
Practical PM skill. Unmanaged dependencies are one of the top causes of project delays. Ask: "What do you do when a dependency team tells you they will be two weeks late?"
End the kickoff with three things: a shared understanding of success criteria, clear next steps for the first sprint, and agreement on how the team will communicate.
Strong answers cover: defining project vision and objectives, roles and responsibilities (RACI), timeline and milestones, communication plan, risk identification, decision-making process, and team norms. The right attendees include the project team, key stakeholders, and the sponsor. Best candidates make kickoffs engaging, not just administrative.
Fundamental PM skill. A bad kickoff sets the tone for a troubled project. Look for preparation, inclusivity, and focus on alignment rather than just information dumping.
Present options, not just the problem. "We are 20% over because of X. Our options are A, B, or C with these trade-offs" empowers stakeholder decision-making.
Best answers: analyse where the overrun is occurring (which categories, which phases), identify root causes (scope creep, poor estimates, resource changes), present options to stakeholders (reduce scope, extend timeline, increase budget, accept reduced quality), and implement corrective actions with monitoring. Best candidates discuss early warning indicators they should have caught sooner.
Tests financial management and stakeholder communication. Hiding budget problems is a serious red flag. Early, transparent communication with options is the hallmark of a mature PM.
Build quality checkpoints into every phase. Catching a requirements error costs 10x less than catching it in testing and 100x less than catching it in production.
Strong answers: define quality standards upfront, build reviews into each phase (not just final delivery), use checklists and acceptance criteria, involve stakeholders in progressive validation, and address quality issues immediately rather than accumulating them. Best candidates discuss the cost of quality versus the cost of rework.
Often overlooked PM responsibility. Candidates who only check quality at delivery are accepting unnecessary risk. Look for quality integration throughout the project lifecycle.
You do not need to write the code; you need to understand enough to ask good questions and recognise when technical risks are being underestimated.
Best answers: ask questions without pretending to know, learn enough to understand trade-offs, trust and empower technical leads, facilitate rather than dictate technical decisions, focus on what you bring (process, stakeholder management, risk awareness), and invest in continuous learning. Red flag: faking technical knowledge.
Relevant for many PM roles. Candidates who pretend to be technical will lose their team's respect. Those who lean into their strengths while genuinely learning are more effective.
Start by listening to the team. They know what is broken. Then reset stakeholder expectations honestly before creating a recovery plan with quick wins.
Strong answers follow a structured recovery approach: assess current state honestly (listen to the team), identify the root causes (scope, resources, communication), reset expectations with stakeholders, create a realistic recovery plan, quick wins to rebuild morale, and establish new cadences. Best candidates resist the urge to change everything at once.
Senior PM scenario. Tests composure, diagnostic skills, and leadership under pressure. Ask: "What if the sponsor does not accept the revised timeline?" to test stakeholder management skills.
Maintain a single prioritised list across all projects. When a new urgent request arrives, show stakeholders what it displaces rather than just saying yes to everything.
Strong answers describe: portfolio-level prioritisation frameworks (business value, urgency, dependencies), time management techniques (time-blocking, delegation), maintaining visibility across projects without micromanaging, communicating capacity constraints to leadership, and knowing when to escalate competing priorities. Best candidates discuss the difference between urgent and important and how they protect strategic work from reactive demands.
Common PM reality. Candidates who say yes to everything without trade-off conversations will burn out and under-deliver. Look for structured prioritisation and transparent communication about capacity.
Track action items from every retrospective and review them at the start of the next one. If the same issue appears three times with no progress, escalate it or change your approach entirely.
Strong answers cover: varying the format to prevent staleness, creating psychological safety for honest feedback, focusing on actionable outcomes rather than venting, tracking action items from previous retrospectives, and measuring whether retrospective actions actually improved team performance. Best candidates discuss what to do when the same issues keep surfacing.
Tests facilitation and continuous improvement skills. Retrospectives that produce no change are theatre. Candidates who can demonstrate measurable improvements from retrospectives are practicing genuine agile, not just following rituals.
Report budget status regularly, even when things are on track. When you spot a potential overrun, present options: reduce scope, extend timeline, or increase budget. Never surprise stakeholders with a cost overrun.
Strong answers cover: regular budget reviews against actuals, earned value management or simpler tracking methods, early warning indicators for budget overruns, communicating variances to stakeholders with options, and contingency reserves. Best candidates discuss the relationship between scope, timeline, and budget trade-offs.
Tests financial discipline. PMs who do not track budgets closely may be well-organised on timelines but miss financial warning signs. Ask: "What is the earliest you have detected a budget issue and what did you do?"
Define deliverables and acceptance criteria clearly in the contract. When issues arise, reference the agreement first, then work together on solutions. Documentation protects both parties.
Strong answers cover: clear contracts with defined deliverables and SLAs, regular performance reviews, building relationships alongside contractual enforcement, addressing issues early and directly, and having contingency plans if a vendor fails. Best candidates discuss the balance between partnership and accountability.
Practical PM skill for projects with external dependencies. Candidates who manage vendors purely through contract enforcement miss the relationship aspect. Those who are too lenient accept poor delivery.
Capture lessons at project milestones, not just at the end. And make them accessible - a lessons learned document nobody can find is the same as no lessons at all.
Strong answers describe a systematic approach: structured project reviews at milestones and completion, documenting lessons in an accessible format, sharing across teams, incorporating lessons into templates and checklists, and referencing past lessons during new project planning. Best candidates discuss the cultural challenge of making lessons learned a habit rather than a checkbox.
Tests learning culture and organisational thinking. PMs who do not capture lessons repeat mistakes. Those who capture but do not apply them are going through the motions. Ask: "Give me an example of a lesson from one project that directly improved another."
Map dependencies early and track them as actively as your own deliverables. A dependency that slips two weeks will cost your project two weeks. Build buffer around critical external dependencies.
Strong answers cover: dependency mapping during planning, regular check-ins with dependent teams, early warning systems for dependency risks, contingency plans for delayed dependencies, and escalation paths. Best candidates discuss how to manage dependencies when you have no authority over the other team.
Critical PM skill. Most project delays come from external dependencies, not internal work. Candidates who proactively manage dependencies prevent the most common cause of project failure.
Map stakeholders on a power/interest grid and tailor your engagement: high power and high interest need close management, high power and low interest need regular updates, and low power supporters can be valuable allies.
Strong answers describe: stakeholder identification techniques, power/interest grid mapping, tailored engagement strategies for each quadrant, regular reassessment as the project evolves, and managing the politics of competing stakeholder interests. Best candidates treat stakeholder management as an ongoing activity, not a one-off exercise.
Foundational PM skill. Candidates who do not systematically identify stakeholders get blindsided by unexpected opposition. Those who map and manage proactively prevent political surprises.
Technical delivery without change management is a project that nobody uses. Plan for training, communication, and resistance management alongside your technical milestones.
Strong answers cover: understanding the impact on affected people, communicating the why before the what, involving people early to build ownership, providing training and support, addressing resistance with empathy, and measuring adoption. Best candidates discuss the difference between project delivery (technical change) and change management (people change).
Senior PM skill. Many projects deliver technically but fail because people do not adopt the change. Candidates who understand change management deliver lasting results, not just completed Gantt charts.
Right-size your governance. A two-person project does not need a steering committee. A cross-departmental programme does. Define who decides what, and when to escalate. Keep it as simple as the project allows.
Strong answers scale governance to project complexity: lightweight for small projects, more structured for large initiatives. Key elements include clear decision rights (RACI), steering committee cadence, escalation criteria, and stage gates. Best candidates discuss the cost of both too much and too little governance.
Tests PM maturity. Over-governance slows projects; under-governance leads to chaos. Candidates who can calibrate governance to project size and risk demonstrate experienced judgment.
Show a specific example: "We used Waterfall for regulatory milestones and Agile sprints within each phase for the development work. This gave compliance the checkpoints they needed while giving the team flexibility."
Strong answers show pragmatism: using Agile for development iterations within a Waterfall-style programme plan, or combining Kanban for operations with Scrum for development. Best candidates discuss why pure approaches often fail in practice and how to get the benefits of both without the worst of each.
Tests practical judgment. Real-world projects rarely fit neatly into one methodology. Candidates who can blend approaches pragmatically while maintaining process integrity are the most effective PMs.
Never use velocity to compare teams or pressure for more output. It is a planning tool, not a performance metric. Track it over time to improve your forecasting accuracy.
Strong answers cover: tracking velocity over time, using historical data for planning, understanding that velocity is a planning tool not a performance metric, accounting for team changes and holidays, and avoiding the trap of comparing velocity across teams. Best candidates discuss how they have improved predictability over several sprints.
Tests agile practice depth. Candidates who weaponise velocity as a performance metric misunderstand its purpose. Those who use it for sustainable planning and forecasting demonstrate mature agile practice.