Project manager interview questions, with worked answers

How to use these questions

Read the short answer and say it out loud. That is your first thirty seconds. Then read the full answer and pick two or three points to add, with an example from your own projects: the size, the people, the problem and the result. Interviewers want proof that you have done it, not a textbook.

The examples mix IT projects, such as a new system or a move to the cloud, with business projects, such as an office move, a construction site, a marketing campaign or a business change. The method is the same; use the examples from your own field.

What a project manager is expected to know

• The basics: scope, schedule, budget, quality, risk, and the trade-offs between them.
• Methods: classic plans in stages (waterfall), AgileAsked in 7% of project manager ads (as of 5 Nov 2026).Run work in short cycles with a team that plans, delivers and adjusts every few weeks. and ScrumAsked in 8% of project manager ads (as of 5 Nov 2026).Know the roles and meetings; many project managers work with Scrum teams or as their scrum master., and hybrids that mix both, with frameworks such as PRINCE2Asked in 5% of project manager ads (as of 5 Nov 2026).A method and certificate for running projects in stages, common in the UK, Europe and the public sector. or the body of knowledge behind the PMPAsked in 2% of project manager ads (as of 5 Nov 2026).The PMI's project management certificate; named in many ads in the US, India and at large companies..
• Tools: a planning tool such as MS Project or JiraAsked in 6% of project manager ads (as of 5 Nov 2026).Plan and track the team's work, read a board to spot risks, and report progress from it., ExcelAsked in 6% of project manager ads (as of 5 Nov 2026).Budgets, plans, risk lists and quick reports; many projects still run on spreadsheets. for budgets and lists, and a shared place for documents such as SharePointAsked in 2% of project manager ads (as of 5 Nov 2026).Project sites and document stores; the place where plans and decisions are kept..
• People: stakeholder managementAsked in 11% of project manager ads (as of 5 Nov 2026).Find everyone a project affects, agree what each needs, and keep them informed and on side., clear communicationAsked in 33% of project manager ads (as of 5 Nov 2026).Clear status reports, short meetings with decisions, and bad news shared early., negotiationAsked in 4% of project manager ads (as of 5 Nov 2026).Agree scope, dates and money with sponsors, suppliers and teams without losing trust. with sponsors and suppliers, and leading people you do not manageAsked in 2% of project manager ads (as of 5 Nov 2026).Lead people you do not manage: set direction, settle conflicts, and keep the team going..
• Governance: who decides what, steering committees, status reports and the approvals at each stage.
• For IT projects: how systems are built, tested and handed over to operations, often under ITILAsked in 1% of project manager ads (as of 5 Nov 2026).The common framework for IT services; useful for projects that hand a system over to operations. rules.
• Law and trust: projects that handle personal data follow GDPRAsked in 2% of project manager ads (as of 5 Nov 2026).EU data protection: projects that touch personal data need privacy checks built into the plan. (EU) and similar laws.

Starting and planning a project

You are given a new project. What do you do in the first two weeks?

What they check: that you get the goal, the scope and the people clear before planning in detail.

Short answer: "I meet the sponsor to agree the goal, the success measures and the limits on time and money. I find the stakeholders and talk to the main ones. I write a short project charter with the scope, what is out of scope, the risks I already see and how decisions will be made, and get it signed off. Then I build the first plan with the team."

The full answer, in six steps:

1. The sponsor. The sponsor is the senior person who wants the result and pays for it. Agree with them why the project exists, what success looks like in numbers, the deadline and the budget.
2. Stakeholders. List everyone affected or with a say, and how much each one matters. Meet the important ones early, one by one.
3. Scope. Write what will be delivered and, just as important, what will not. Vague scope is the first cause of late projects.
4. Charter. A project charter, or project initiation document, puts goal, scope, budget, roles, first risks and decision rules on a few pages, signed by the sponsor.
5. First plan. With the team, break the work into parts, estimate them, and set milestones (points where something visible is finished).
6. Rhythm. Agree the meetings, the status report and the steering committee dates from the start.

A weak answer: "I start making a detailed plan in MS Project." A detailed plan of an unclear goal is detailed and wrong.

Follow-up: "The sponsor cannot say what success looks like." Offer two or three measures and ask them to choose, for example cost per case, go-live date, or user adoption.

How do you build a project schedule, and what is the critical path?

What they check: that you can turn work into a realistic plan and know where the real deadline risk sits.

Short answer: "I break the work into tasks, estimate them with the people who will do them, and link the tasks that depend on each other. The critical path is the longest chain of dependent tasks: any delay on it delays the whole project. I watch those tasks most closely and add buffer before key dates."

The full answer: A work breakdown structure splits the project into deliverables and then tasks small enough to estimate. Dependencies show which task needs another to finish first. Tasks off the critical path have float, meaning they can slip a little without moving the end date. For an office move, the fit-out of the new floor is often on the critical path, while ordering new chairs is not. Estimates are ranges; plan with the realistic one, not the hopeful one, and keep the buffer visible rather than hidden in every task.

A weak answer: "I take the deadline and divide the time between the tasks." Follow-up: "A task on the critical path slips by two weeks." Look for ways to run tasks in parallel, add people only where it really helps, or cut scope; tell the sponsor with the options.

How do you set and control a project budget?

What they check: that you can estimate costs, track them and act before the money runs out.

Short answer: "I build the budget from the plan: people, suppliers, licences, equipment and a contingency for risks. Each month I compare what we spent and what we have delivered against the plan, and forecast the cost at the end. If the forecast passes the budget, I tell the sponsor early with options."

The full answer: Contingency is money set aside for known risks; it is not a reserve for anything. Tracking only what was spent misleads: a project can be under budget because work is late. Earned value compares the value of the work done with what it cost and with the plan, and shows both delay and overspend early. Commit costs when contracts are signed, not when invoices arrive, so the forecast is honest.

A weak answer: "Finance tracks the budget." Follow-up: "Halfway through, you forecast a tenth over budget." Find the cause, look for savings or scope cuts, and bring the sponsor a recommendation, not just the problem.

Risks, changes and problems

How do you manage project risks?

What they check: that risk management is a habit, not a form filled in once.

Short answer: "I keep a risk log from the first week: what could happen, how likely, how bad, who owns it, and what we do about it. The team and I review it every week, and the top risks go into the status report. A risk that happens becomes an issue, and we act on it at once."

The full answer: For each risk choose a response: avoid it by changing the plan, reduce it, move it to someone better placed (a supplier, an insurer), or accept it with a plan B. Many projects keep a RAID log: risks, assumptions, issues and dependencies in one place. Ask the team "what keeps you awake?" each week; the best risks come from the people doing the work. And close risks that have passed, so the log stays useful.

A weak answer: "We wrote a risk register at the start." Follow-up: "Name a risk that happened on your project." Tell the story: when you saw it, what you did, and what it cost or saved.

The sponsor asks for a big new feature halfway through. What do you do?

What they check: that you handle scope change through a clear process, without saying a flat no.

Short answer: "I welcome the idea but assess it first: what it adds, and what it costs in time, money and risk. It goes through a change request, so the decision and its impact are written down. The sponsor or the steering committee decides, and I update the plan and tell everyone."

The full answer: Scope creep is the slow growth of a project through small additions nobody decided on properly. A change request is a short form: what changes, why, the effect on scope, schedule, budget and risk, and the options, such as adding it now, swapping it for something else, or doing it in a second phase. In an agile project the same idea works through the backlog: the new item is ranked against the rest, and something else moves out.

A weak answer: "I add it because the sponsor is the boss." Follow-up: "The sponsor wants it without changing the date or budget." Show what would have to come out, and the risk of trying to do everything.

Your project is six weeks late. How do you get it back on track?

What they check: a calm, ordered recovery, and honesty with the sponsor.

Short answer: "First I find out why, and whether the delay is still growing. Then I look at the options: cut or delay scope, run work in parallel, add the right people, or move the date. I take a realistic recovery plan to the sponsor quickly, with the options and my recommendation, and then report against it every week."

The full answer, in five steps:

1. Find the cause. Bad estimates, a supplier, people pulled away, unclear requirements? The fix depends on it.
2. Re-plan honestly. Rebuild the remaining plan with the team, with realistic estimates. A recovery plan built on hope fails twice.
3. List the options. Cut or delay scope, run tasks side by side, add experienced people to a few tasks, or move the date. Adding people late often slows a project further, because they must be trained.
4. Decide with the sponsor. Bring the options with their costs and risks, and your recommendation.
5. Track closely. Report weekly against the new plan, and fix the cause so it does not happen again.

A weak answer: "Everyone works weekends until we catch up." It works for a week and then people make mistakes or leave.

Follow-up: "The sponsor refuses to move the date." Then scope must move: agree which parts are needed on day one and which can follow.

Stakeholders, teams and suppliers

How do you manage stakeholders who disagree with each other?

What they check: that you keep people informed and settle conflicts at the right level.

Short answer: "I map who is affected and who decides, and talk to each important stakeholder regularly. When two disagree, I bring them together around the project's goal and the facts. If they still disagree, I take the decision to the sponsor or the steering committee with the options, rather than letting it drag on."

The full answer: A stakeholder map plots people by how much they are affected and how much influence they have; the powerful and affected ones need the most attention. Agree in the charter who decides what, so conflicts have a path. Share bad news early: a stakeholder surprised in a steering committee becomes an opponent. Write decisions down and send them the same day.

A weak answer: "I try to keep everyone happy." Follow-up: "A powerful stakeholder keeps blocking decisions." Meet them alone, find out what they fear losing, and see whether the plan can meet that need.

How do you lead a project team of people who do not report to you?

What they check: leadership through clarity and trust, not through authority.

Short answer: "I make sure everyone knows the goal, their part and the deadline, agree their time with their line managers, remove what blocks them, and give credit in public. When there is a problem with someone's work, I talk to them first, and to their manager only if that does not help."

The full answer: In most companies the project manager leads a team borrowed from departments. Agree how much of each person's time the project gets, in writing, with their manager. A short kick-off builds the team; a regular short meeting keeps it together. Conflicts in the team are normal; deal with them early and privately. Tell line managers what their people did well; it is the best way to get them again for the next project.

A weak answer: "I escalate to their manager when they do not deliver." Follow-up: "A key person is pulled back to their department." Show the sponsor what it costs the project, and agree a replacement or a change to the plan.

How do you manage an external supplier who is missing deadlines?

What they check: that you manage suppliers through the contract, facts and relationship.

Short answer: "I check the facts against the contract and the plan, then talk to the supplier's project manager about the cause and a recovery plan with dates. I track it weekly. If it does not improve, I escalate through the contract's process and involve purchasing."

The full answer: Prevention starts at the contract: clear deliverables, acceptance criteria, milestones linked to payment, and a way to escalate. Treat the supplier as part of the team: share the plan and the risks, and invite them to the regular meetings. When problems come, find out whether the cause sits with them or with us, such as late decisions or unclear requirements. NegotiationAsked in 4% of project manager ads (as of 5 Nov 2026).Agree scope, dates and money with sponsors, suppliers and teams without losing trust. is easier when both sides trust the facts.

A weak answer: "I threaten them with penalties." Follow-up: "The supplier says our changes caused the delay." Check the change log; if they are right, agree the impact and update the plan.

Methods, reporting and closing

When would you use waterfall, agile or a hybrid?

What they check: that you choose the method by the project, not by habit.

Short answer: "Waterfall, planning in stages from start to end, fits work where the result is clear and changes are costly, such as a construction or an office move. Agile, delivering in short cycles, fits work where needs will change and early feedback matters, such as new software. Many projects are hybrids: a fixed overall plan with agile teams inside."

The full answer: The question is how much is known at the start and how costly change is. A data centre move has fixed steps and a hard weekend; plan it in detail. A new customer app will change once users see it; deliver it in sprints and adjust. Methods such as PRINCE2Asked in 5% of project manager ads (as of 5 Nov 2026).A method and certificate for running projects in stages, common in the UK, Europe and the public sector. split a project into stages with a decision at each; Scrum runs work in sprints of two to four weeks. Large companies add a framework such as SAFeAsked in 1% of project manager ads (as of 5 Nov 2026).A framework for agile at large companies, with programme planning across many teams. to plan many agile teams together. Certificates such as the PMPAsked in 2% of project manager ads (as of 5 Nov 2026).The PMI's project management certificate; named in many ads in the US, India and at large companies. now cover both.

A weak answer: "Agile is always better." Or: "We always use waterfall." Follow-up: "The sponsor wants a fixed date and a fixed scope for an agile project." Fix the date and the budget, agree the must-have scope, and let the rest follow the priorities.

What goes into a good status report?

What they check: that you report honestly and briefly, so leaders can act.

Short answer: "One page: the overall status, what was done and what comes next, the schedule and budget against the plan, the top risks and issues, and the decisions I need, with a date. I use red, amber and green honestly, and I never let a report be the first place a sponsor hears bad news."

The full answer: A status report is for the reader, so it starts with what they need to know or decide. Red, amber, green (RAG) status works only if amber is used: a project that is green every week until it turns red has not been reporting. Use the same format every time, so changes stand out. For the steering committee, add a short view of the benefits and the change requests waiting for a decision.

A weak answer: "A long list of everything the team did." Follow-up: "Your sponsor never reads the report." Ask what they need, cut it to that, and talk through the top risk with them in person each week.

How do you close a project, and how do you run lessons learned?

What they check: that you hand over properly and help the organisation learn.

Short answer: "I check that everything in scope is delivered and accepted, hand over to the people who will run it, with documents and training, close contracts and the budget, and release the team. Then I run a lessons learned session and share what we would do again and what we would change."

The full answer: For IT projects, handover to operations includes support rules, often under ITILAsked in 1% of project manager ads (as of 5 Nov 2026).The common framework for IT services; useful for projects that hand a system over to operations., so the service desk can take calls from day one. A lessons learned session works best soon after go-live, with the whole team, and with a few concrete actions, not a long document nobody reads. Agree with the sponsor when the benefits will be measured, because that often happens months after the project ends.

A weak answer: "When it goes live, the project is finished." Follow-up: "Lessons learned always produce the same list." Pick one or two actions, give each an owner, and check them at the start of the next project.

Programmes, the PMO and the portfolio

These questions come up for senior project managers, programme managers, PMO leads and head of delivery roles.

What is the difference between managing a project and a programme?

What they check: that you think in benefits and dependencies across projects.

Short answer: "A project delivers an output, such as a new system. A programme is a group of related projects that together deliver a bigger benefit, such as a new way of serving customers. The programme manager manages the dependencies, the shared risks and the benefits, and leads the project managers."

The full answer: In a business change programme, one project may build the system, another change the processes, a third train the staff and a fourth move the offices. None of them alone delivers the benefit. The programme manager keeps a shared plan of the dependencies, a benefits map from each output to the business result, and a governance where the project managers bring issues they cannot solve alone. They also decide when to start, stop or merge projects.

A weak answer: "A programme is just a big project." Follow-up: "Two of your projects need the same expert at the same time." Decide by the programme's critical path and benefits, and move the other project's plan.

How would you set up or improve a PMO?

What they check: for PMO lead roles, that a PMO helps projects deliver rather than adding paperwork.

Short answer: "I start by asking leaders and project managers what they need: better reporting, standard methods, help for struggling projects, or portfolio decisions. Then I set up only that, with light standards, a common status view and support for project managers. I measure the PMO by whether projects deliver better."

The full answer: A PMO, a project management office, can be supportive (templates, training, coaching), controlling (standards and reviews) or directive (it runs the projects). Choose the kind the organisation needs. Keep templates few and short; a PMO known for forms loses the project managers. A portfolio view of all projects, with status, cost and benefits, helps leaders decide where to invest. Build a community of project managers that shares lessons and tools.

A weak answer: "I would make every project fill in the same twenty templates." Follow-up: "Project managers see the PMO as overhead." Ask what would help them most, deliver that first, and cut a report they find useless.

As head of delivery, how do you decide which projects the company should run?

What they check: portfolio thinking: value, capacity and strategy, not first come, first served.

Short answer: "I put all proposed and running projects in one portfolio, score them on value to the strategy, cost, risk and urgency, and compare that with the people and money we have. Leadership then chooses, and we stop or pause projects that no longer earn their place. We review the portfolio every quarter."

The full answer: Most organisations start too many projects at once and finish them late. Limiting the number running at the same time, and finishing before starting, often speeds delivery more than any method. A head of delivery also builds the project management career path, hires and coaches project and programme managers, sets the delivery standards, and reports to leadership on the portfolio's results, not only on its status.

A weak answer: "We do the projects the most senior people ask for." Follow-up: "A director's favourite project scores low." Show the scores and the trade-off openly, and let leadership decide with the facts.

Your CV for these questions

Every answer above is easier when your CV already says it, because the interviewer asks about what is on it. Put one line under each job for each of these, in the words the ads use:

Then score your CV against a real job: you will see which of these the job needs and which your CV does not prove yet.