Project manager interviews test your process knowledge, your people skills, and your ability to keep a project moving when things go wrong. The candidates who struggle most are those who can describe PM methodology perfectly but can't give a concrete example of how they handled a real crisis. Methodology is the floor, not the ceiling. What wins interviews is specificity.
What PM interviews test
Interviewers want to know: Can this person keep a project on track when scope, timelines, and resources are all under pressure? Can they manage up to sponsors and down to delivery teams at the same time? And do they have the communication skills to keep everyone aligned without micromanaging?
Planning and delivery questions
"How do you handle scope creep?"
"The best time to prevent scope creep is in the charter, by defining what's in and explicitly what's out. When new requests come in, I use a formal change control process: document the request, assess the impact on timeline, budget, and resources, present the trade-offs to the sponsor, and get a decision. I never say no to a request, I say 'yes, here's what it costs.' That framing changes the conversation from 'PM is blocking us' to 'business is making a trade-off decision.'"
"How do you build a project plan for a project with a lot of unknowns?"
Talk about discovery phases, progressive elaboration, rolling wave planning, and building in buffer for unknowns. Show you don't try to plan 12 months in detail on day one. A good PM builds enough structure to get started, then refines as they learn.
Risk and issue management questions
"How do you manage risks?" The answer is a risk register: identify, assess (probability and impact), decide on response (avoid, mitigate, transfer, accept), assign an owner, and review regularly. Show that your risk register is a live document, not something you fill in at the start and ignore.
"Tell me about a project that went off track. What did you do?" This is the question that separates experienced PMs from theory-trained ones. Be specific, take ownership of your role, and show what you did to recover.
Stakeholder and communication questions
"How do you keep stakeholders informed without overwhelming them?" Show that you tailor communication to the audience: sponsors get executive summaries and red/amber/green status. Team members get detailed task-level updates. You don't send the same update to everyone.
"How do you handle a stakeholder who keeps changing their mind?" Structure your answer around: understanding the root cause (unclear requirements vs. changing business context), documenting decisions formally so they're harder to reverse casually, and escalating when changes threaten the project objective.
Behavioral questions with sample answers
"Tell me about a time you had to deliver a project with insufficient resources"
S/T: "I was handed a system implementation with a six-month deadline and a team that was two developers short because the company had a hiring freeze."
A: "I did three things. First, I re-prioritised the feature set with the product owner to identify what was truly must-have for go-live vs. what could follow in phase two. That freed up about 20% of the development effort. Second, I brought in two contractors for six weeks to cover the specific build that was on the critical path. Third, I restructured the testing phases to run in parallel with late-stage development rather than sequentially."
R: "We delivered on the original deadline. The phase two backlog was documented and scoped before go-live, so there was no perception of the project being incomplete. The contractor cost was covered by avoiding the cost of a delayed launch, which I pre-calculated and presented to the sponsor."