Project Manager Interview Questions & Answers

Tell us about a time you managed a difficult stakeholder.

On a system migration, a senior stakeholder kept changing requirements late, which threatened the timeline. Rather than push back defensively, I set up a short weekly call with him specifically to understand what was driving the changes — it turned out he was worried about a compliance deadline I hadn't been told about. Once I understood the real concern, I re-prioritised the backlog so the compliance-critical pieces came first and agreed a clear change-control process for anything new. That gave him confidence and protected the timeline. We delivered the compliance scope two weeks early. The lesson was that 'difficult' stakeholders usually have an unspoken pressure, and surfacing it turns conflict into a shared plan.

How do you identify and manage risk on a project?

I treat risk as an ongoing process, not a one-off document. At kickoff I run a risk workshop with the team to capture what could go wrong, then log each risk with an owner, a likelihood/impact rating, and a mitigation. The key is keeping it live — I review the top risks in every status meeting rather than letting the register gather dust. For example, on one project we flagged early that a third-party API was a delivery risk, so we built a fallback and started integration testing sooner; when their release slipped, we weren't blocked. Good risk management is mostly about visibility and acting early, before a risk becomes an issue.