Interview questions by role
Project manager interview questions
Project manager interviews check whether you can deliver to scope, time and budget when things go wrong. Expect questions on how you plan, track and report progress, manage risks and changes, handle a project that is running late, deal with difficult stakeholders, and lead a team you may not directly manage.
How the interview usually runs
Interviews are usually competency-based, with a hiring manager and sometimes a senior stakeholder from the business. Some employers ask you to present a past project or run through a scenario: the project is behind schedule and the sponsor wants it on time, what do you do? Questions about methodologies such as Agile, Scrum, PRINCE2 or PMP-style approaches come up, but they are rarely the deciding factor.
Interviewers listen for control and communication. They want to hear you spot problems early, bring options to decision-makers rather than surprises, and keep the team motivated under pressure.
Common questions and what the interviewer is checking
Tell me about a project that was going off track. What did you do?
What they are checking: Early detection, honest reporting, options with trade-offs (scope, time, cost, quality), and a decision made by the right person.
How do you plan a new project?
What they are checking: Understanding objectives and success criteria, scope, stakeholders, breakdown of work, dependencies, risks, resources and a realistic schedule.
How do you handle scope creep?
What they are checking: A change process: assess impact, document it, get approval, and adjust the plan, without being rigid about genuine improvements.
Tell me about a difficult stakeholder.
What they are checking: Understanding their concerns, adjusting communication, and keeping them engaged without giving in on everything.
How do you manage risks?
What they are checking: A living risk log, owners, mitigation plans, and examples of a risk you caught before it became an issue.
How do you report progress to senior leaders?
What they are checking: Clear, honest summaries: status, key risks, decisions needed, focused on what they need to act on.
How do you motivate a team you do not line-manage?
What they are checking: Building relationships, clarity of goals, recognising work, and resolving blockers quickly.
Agile or waterfall: which do you prefer?
What they are checking: Pragmatism. Good answers explain which suits which kind of project and how you have adapted.
Tell me about a project that failed or did not meet its goals.
What they are checking: Ownership, what you learned, and what you now do differently.
How to structure a strong answer
Project stories work best with STAR, but spend most of the time on your actions and choices: what you noticed, what options you put forward, how you communicated and what you changed. End with the outcome and the lesson.
- Situation: the project, its goal and constraints.
- Problem: the risk or issue, and when you spotted it.
- Action: the options you presented and what you did.
- Result: delivery outcome, and what you do differently now.
Example answer
Tell me about a project that was going off track. What did you do?
I was managing the move of a customer support team to a new ticketing system with a fixed go-live date before the busy season. Halfway through, I could see from the tracker that data migration testing was taking much longer than planned, because the old data had far more inconsistencies than expected.
I raised it at the next steering meeting with three options: delay go-live, add a contractor to help with clean-up, or go live with only the last two years of history and archive the rest. I set out the cost and risk of each. The sponsor chose the reduced history option. We went live on the original date, and the archive stayed searchable for the few cases that needed older tickets. Since then I build data quality checks into the first weeks of any migration.
Mistakes to avoid
- Describing only processes and templates, with no example of a real problem.
- Hiding bad news or presenting problems without options.
- Taking all decisions yourself that should sit with the sponsor.
- Using methodology jargon instead of explaining what actually happened.
- Ignoring the people side: team morale, conflict and communication.
Frequently asked questions
What questions are asked in a project manager interview?
Expect questions about a project that went off track, how you plan, manage scope creep and risks, report to senior leaders, deal with difficult stakeholders, motivate a team, choose a methodology and learn from a failed project.
How do I answer "tell me about a project that failed"?
Choose a real setback, explain your role in it honestly, focus on what you did once it was clear things were going wrong, and finish with what you changed in how you work.
Do I need a certification to pass a project manager interview?
Some employers list certifications, but interviews focus on what you have delivered. Be ready to show how you applied the method rather than reciting it.
How technical do project managers need to be in interviews?
Enough to understand the work, the dependencies and the risks in that field. In technical industries, expect questions about how you worked with specialists and understood their estimates.