Use these project manager interview questions to find someone who can plan realistically, spot trouble early, and keep sponsors and teams honest about trade-offs. They're written for hiring managers, PMO leads and recruiters, and for project managers getting ready for interviews. The 22 questions cover planning and scope, schedule and budget control, risk and change, agile delivery, and STAR behavioral stories, each with what a strong answer shows. A 45-minute first round needs 6 to 8 of them. The best signal comes from follow-ups like "what did you tell the sponsor?" and "what would you do differently?"
What a strong project manager interview checks
- Planning: breaking work down, estimating honestly and building a schedule around real dependencies.
- Control: tracking progress against the plan, catching slippage early and knowing what the numbers mean.
- Risk and change: naming risks before they hit and handling scope changes through a clear process.
- Stakeholder communication: status reports that tell the truth, and the nerve to deliver bad news early.
- Team leadership: getting work done through people they often don't manage directly.
Project manager interview questions: planning and scope
1. You're handed a new project with a deadline already set. What do you do in the first two weeks?
What good looks like: confirm the goal, scope and success measures with the sponsor, identify stakeholders, break the work into a work breakdown structure, and get estimates from the people doing the work. Then they test the deadline against that plan and raise any gap right away, with options, rather than accepting it silently.
2. How do you write a scope statement that prevents arguments later?
What good looks like: clear deliverables, acceptance criteria, what is explicitly out of scope, assumptions and constraints. Strong candidates stress the out-of-scope list, because that's where most later disputes come from, and they get it signed off.
3. How do you get estimates you can trust?
What good looks like: estimates come from the people doing the work, broken into small pieces, with ranges rather than single numbers for uncertain tasks. They compare against past projects, add contingency for known risks, and track actuals so the next estimate is better.
Red flag: setting estimates alone and handing them to the team as commitments.
4. What is the critical path, and why does it matter?
What good looks like: the longest chain of dependent tasks from start to finish, which sets the shortest possible project duration. Tasks on it typically have zero total float, so any delay there delays the whole project. Strong candidates add that the critical path can shift as work progresses, so they recheck it.
5. How do you build a RACI chart, and when does it help?
What good looks like: for each deliverable or decision, name who is Responsible for doing it, the one person Accountable for it, who must be Consulted and who is kept Informed. It helps most where several teams overlap or decisions keep stalling. Exactly one Accountable person per item is the rule they shouldn't break.
Schedule, budget and risk
6. Planned value is $50,000, earned value is $40,000 and actual cost is $45,000. How is the project doing?
What good looks like: cost performance index is EV divided by AC, about 0.89, so the project is getting about 89 cents of work per dollar spent and is over budget. Schedule performance index is EV divided by PV, 0.8, so it's behind schedule. They'd then look for the cause rather than just reporting the numbers.
7. Your project is three weeks behind. What are your options?
What good looks like: they first find out why. Then options include fast-tracking (doing tasks in parallel, which adds risk), crashing (adding people or money to critical tasks, which adds cost and has limits), reducing scope, or moving the date. They present the trade-offs to the sponsor with a recommendation.
Red flag: "We'll just work weekends," with no plan beyond that.
8. How do you run a risk register so it doesn't become a forgotten spreadsheet?
What good looks like: each risk has an owner, likelihood and impact, a response (avoid, reduce, transfer or accept) and a trigger that tells you it's happening. They review the top risks in regular meetings and close or update them as the project changes.
9. What's the difference between a risk and an issue?
What good looks like: a risk is something that might happen; an issue is something that has happened and needs action now. A good register turns risks into issues when their triggers fire, and lessons from issues feed back into risk planning on the next project.
10. A sponsor wants a "small" addition mid-project. How do you handle it?
What good looks like: they log it as a change request, assess the effect on scope, schedule, cost and risk, and bring it to whoever approves changes. Small changes add up, so even quick yeses get recorded. Strong candidates keep it friendly and practical rather than bureaucratic.
11. How do you report status when the news is bad?
What good looks like: early, plainly and with options. They state the problem, its impact, what they're already doing and what decision they need. Strong candidates use status colors honestly and say a red project reported early is better than a green one that turns red overnight.
Agile and delivery
12. When would you choose an agile approach, and when a more plan-driven one?
What good looks like: agile when requirements are uncertain and users can give frequent feedback, as in most software work. Plan-driven when requirements are stable, work is sequential, or contracts and regulations demand fixed scope, as in construction or some compliance projects. Many real projects mix both.
13. What's the difference between a project manager and a scrum master?
What good looks like: a scrum master coaches the team on the process and removes blockers but doesn't assign work or own the plan. A project manager typically owns the overall plan, budget, risks and stakeholder reporting. In some organizations one person does both, and good candidates are clear about which hat they're wearing.
14. A team keeps missing sprint commitments. What do you look at?
What good looks like: whether work is too big or poorly defined, unplanned work interrupting sprints, dependencies on other teams, and whether the commitment is set by the team or pushed on them. They use the retrospective to agree on one or two changes and check whether they helped.
15. How do you manage dependencies on teams you don't control?
What good looks like: identify dependencies early, agree dates with the other team's lead in writing, check in before the date rather than after, and have a fallback for the critical ones. They escalate through leadership only when direct conversation fails.
16. How do you close a project well?
What good looks like: confirm acceptance of deliverables, hand over to operations with documentation and support, release people and budget, and run a lessons-learned session that produces specific changes, not just a list of complaints.
Behavioral project manager interview questions (STAR)
17. Tell me about a project that failed or came close to it.
What good looks like: a clear Situation, what went wrong and when they saw it, the Actions they took, and an honest Result. Strong candidates own their share and name what they'd do differently.
Red flag: a story where every problem was someone else's fault.
18. Describe a conflict between two team members that was hurting the project.
What good looks like: they addressed it early and privately, focused on the work and the shared goal, and agreed on how the two would work together. They involved line managers when needed and checked that the fix stuck.
19. Tell me about a time you had to tell a sponsor something they didn't want to hear.
What good looks like: they came prepared with facts and options, delivered the message directly, and helped the sponsor decide. The Result shows trust held or grew.
20. Describe a project where you had no authority over the people doing the work.
What good looks like: they built influence through clear goals, making others' work easier, recognizing contributions and agreeing commitments in the open. A specific example of turning a reluctant contributor around is a good sign.
21. Tell me about a time you improved how projects are run.
What good looks like: a concrete change, such as a lighter status template or a new intake process, why it was needed, how they got people to adopt it, and a measurable result.
22. How did you handle a project where priorities changed halfway through?
What good looks like: they reset the plan with the sponsor, communicated the change and its reasons to the team, protected work that still mattered, and recorded what was dropped. They kept morale up without pretending nothing changed.
A simple scoring rubric
Running this interview with AI
Project manager openings often draw candidates from very different backgrounds, from construction to software. An adaptive AI interviewer like NTRVSTA can run a consistent first round for all of them: it interviews candidates live, by video avatar or audio, at any hour, and adjusts difficulty to each answer. Someone who handles the earned value question cleanly gets pushed toward recovery options, while someone who struggles gets a simpler step and, if you allow it, a hint. Behavioral questions follow STAR, and the soft-skills library covers communication, problem-solving and leadership.
You can customize questions per role to add your own delivery method and industry scenarios. Hiring managers receive a score breakdown and video snippets of the strongest moments before choosing who meets the panel. See how AI interviews are scored and our comparison of AI interview software. To post the role, use the project manager job description template. Related: leadership interview questions and business analyst interview questions.
Questions
Does a project manager need a PMP to pass this interview?
No. A PMP or similar certification shows the candidate knows the standard vocabulary and processes, which helps on large or regulated programs. But plenty of strong project managers don't hold one. Score the answers and the real project stories, and only require the certification if a client or contract does.
How do I test project management skills without a long case study?
Give a 15-minute scenario: a project two weeks behind, a key person leaving and a sponsor asking for a new feature. Ask the candidate what they would do in the next 48 hours and what they would say to the sponsor. You will hear their priorities, risk thinking and communication in one exercise.
Should I ask agile or waterfall questions?
Ask about the way your teams actually work, plus one question on when the other approach fits. Many organizations run hybrids, such as fixed milestones with agile delivery inside them, so a candidate who can explain trade-offs is more useful than one loyal to a single method.
Want to watch an AI interviewer run a project manager screen? Book 20 minutes with us, or try a sample interview on your own time.
