Project Manager Inter­view Questions: Your Role and Authority

Project management interviews may ask how you plan work, communicate, manage risk and work with stakeholders. This guide helps you describe your real role: what you decided, what you recommended and what other people decided. It includes role-specific prompts to practice.

The practice suggestions here are optional, so adapt them to the question and to any limit or instruction the interviewer gives. Honesty, confidentiality and permission are not optional. All examples are fictional and are not claims for you to copy. This guide gives no legal, contractual, pay or certification advice.

Questions you may be asked

Stakeholders and communication:

• Tell me about a time you had to deliver bad news to a stakeholder.
• Tell me about a conflict between two stakeholders and what you did.
• Describe your experience working with cross-functional or remote teams.

Planning and control:

• How do you prioritise when everything is marked urgent?
• How have you managed or tracked a project budget?
• How do you identify and manage risk?
• How do you handle requests to change the scope?

Learning from things that went wrong:

• Describe a project that did not go as planned. What did you learn?

Methods and tools:

• Which project management methods and tools have you used, and for what?
• How have you used AI tools in your work, if at all?

About you:

• Tell me about yourself, and why this role?

Map your authority before you practice

For each project you might discuss, make notes:

• What was the project, described in general terms? Leave out confidential figures unless you have permission to share them.
• What was your title, and what role did you actually perform, for example project manager, coordinator or team member covering planning?
• What did you decide yourself?
• What needed approval from a sponsor, client or manager, and who approved it?
• What did other people decide?
• What did you recommend or influence?
• What happened, including if the outcome is unknown?

Keep contribution and decision apart. Tracking a budget is not the same as controlling it, and escalating a risk is not the same as owning how it is handled. Choose verbs that match your role, such as tracked, coordinated, recommended, escalated, decided or approved, and use "decided" only for decisions that were yours. Do not describe a team's or a sponsor's decision as your own.

Role-specific prompts to practice

Use these prompts to find the real detail in your own examples.

• Bad news: Who needed to know, who decided how and when to tell them, what did you say and what happened?
• Priorities: Who set the priorities? What did you propose, and what did you do when you were asked for several things at once?
• Budget: Did you hold the budget, track it or only report on it? Who approved changes? What did you do when spending differed from the forecast?
• Risk: What risk did you notice, who owned it, what did you do and what happened? Keep what you recommended separate from what you decided.
• Scope changes: How were changes requested and approved on that project, and what was your part?
• Stakeholder conflict: What did each person want, what did you do and who made the final decision?
• Remote or cross-functional work: How did the team communicate, and what part of that did you set up or follow?
• Methods and tools: Which ones have you used, in what setting, and what did you personally do with them?
• AI tools: If you have used them in project work, say which, what for, what you checked and whether confidential information was involved and allowed. If you have not used them, say so.

Certifications and experience

Do not assume that any particular certification is required. Check the advert. If you hold one, say what it is and whether it is current. If the role asks for one you do not hold, say so, say what related experience you have and ask the recruiter what is required. Do not present related experience as the certification.

Do not use general process language to hide a gap. If you have not held a budget, led a team or managed a particular kind of risk, say so, and describe what you did do. Our guide on what to do when you don't know an answer covers questions you cannot answer fully.

Fictional examples of contribution and decision

Each example below is invented. Do not present any of them as your own experience, and do not copy them.

Fictional example, contribution and decision: "On a small internal project I was the coordinator. I kept the plan and the task list up to date and reported progress to the project manager. The project manager and the sponsor decided the priorities and approved any change to the date. I recommended moving one task earlier, and they decided not to. I don't know whether that would have made a difference."

Fictional example, tracking a budget: "I tracked spending against the forecast each month and told the project manager when it differed. I didn't hold the budget and I couldn't approve changes. My part was making sure the figures were accurate and explaining the differences when I was asked."

Fictional example, raising a risk: "I noticed that a supplier hadn't confirmed a delivery date. I raised it with the project manager and recorded it as a risk. They decided to contact the supplier. I don't know how it was resolved."

Fictional example, a limitation: "The advert asks for experience of holding a budget. I have tracked and reported on a budget, but I have not owned one. Tracking is not the same as holding a budget, so I would need training and supervision suited to the role before I could do that independently."

Questions to ask about decisions and process

• Who holds the budget, and who approves changes to scope on projects here?
• How are priorities set when several projects compete?
• Which decisions would be mine, and which would need approval?
• How are risks raised and escalated?
• Which methods and tools does the team use?

Practice explaining your decisions

Say your answers aloud, and record yourself if you wish. If you practice with another person, agree with them before recording and before sharing any recording, and respect confidentiality. Use true projects, and leave out confidential information about employers, clients and colleagues. Our STAR examples guide and our guide to explaining an unsuccessful project show ways to structure an example.

In a real interview, do not use any tool to generate answers unless the organiser has explicitly allowed it, and do not record the conversation unless the interviewer has agreed. Our interview preparation checklist covers the wider preparation.

This guide is published by Muqabala. You can visit our interview practice page for your next practice session. Use any method that suits you, and check how any tool handles your data first. Do not paste confidential employer, client or project information into a practice tool.