In this article
The role and the basics
What does a project manager do?
A project manager plans a project, coordinates the people doing it and keeps scope, schedule and budget in balance until the goal is delivered. The U.S. Bureau of Labor Statistics describes project management specialists as people who "coordinate the budget, schedule, staffing, and other details of a project" (Bureau of Labor Statistics, last modified August 2026). Add one project you ran and its size.
Why it is asked: it checks that your idea of the job matches theirs.
What is the difference between a project and a program?
A project is a temporary effort with one goal, a schedule and a budget; a program is a group of related projects managed together for a combined result. Definitions vary between employers, so say which level you have worked at. The wider role split is set out in the program manager interview guide.
Why it is asked: it shows whether you understand where your role ends. Read the full explanation: how project and program managers differ.
How do scope, schedule and budget trade off?
Changing one of the three usually pressures the others. Adding scope normally costs time or money, a shorter schedule normally costs money or scope, and a tighter budget normally cuts scope or stretches the date. Give an example: when a stakeholder asked for a new feature mid-project, you showed the cost in days and let them choose what to drop.
Why it is asked: it tests whether you manage constraints or only track them.
How do you define success for a project?
Agree measurable success criteria with the sponsor before work starts: the outcome, the date, the cost limit and what "done" means in checkable terms. Then report against those criteria, not against activity. A project that ships on time but misses the outcome the sponsor wanted is not a success.
Why it is asked: vague goals are a common reason projects drift.
Planning and estimating
How do you build a project plan?
Start from the goal, break the work into tasks small enough to estimate, order them by dependency, assign owners, add the estimates and then add time for risks and reviews. Check the plan with the people doing the work, because they find missing tasks. Keep it visible and update it weekly.
Why it is asked: it shows whether you plan from the work or from a template.
How do you estimate when you are unsure?
Ask the people who will do the work, give a range and not a single number, and state your assumptions. Compare with similar past work if you have it. Re-estimate when a major unknown is resolved, and tell stakeholders the estimate is a range that narrows as you learn more.
Why it is asked: estimates are always uncertain, and interviewers want honest handling of that.
What is the critical path?
The critical path is the longest chain of dependent tasks, which sets the shortest possible project duration. A delay to any task on it delays the whole project, while tasks off it have slack. Say how you use it: watch those tasks first, and look for ways to shorten or overlap them.
Why it is asked: it tests whether you know where schedule risk lives.
How do you handle scope creep?
Scope creep is the growth of a project's scope after it was agreed, without a matching change to time, cost or resources. Handle it with a simple change process: write the request, estimate its effect, and let the sponsor approve, defer or swap it. Do not say no by reflex; show the trade-off instead.
Why it is asked: it tests firmness together with flexibility.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →Risk and problems
How do you identify and manage risks?
A risk register is a list of what could go wrong, with an owner, a likelihood, an impact and a planned response for each item. Keep one and review it at every status meeting. Respond by avoiding, reducing, transferring or accepting each risk, and escalate any that need a decision above your level.
Why it is asked: good managers plan for problems before they happen.
Text description of the diagram
- A risk register lists each risk with an owner, a likelihood, an impact and a planned response.
- Each risk is answered by avoiding, reducing, transferring or accepting it.
A key deadline is going to be missed. What do you do?
Confirm the facts, find the cause and the options, and tell the sponsor early with a recommendation. Options are usually to cut scope, add resources, move the date or accept a risk. Say you would bring the options and your choice, not only the problem, and follow up in writing.
Why it is asked: how you handle bad news matters more than a perfect record. Read the full explanation: worked deadline scenarios.
Tell me about a project that went badly.
Use the situation, task, action, result structure from how to answer interview questions: what went wrong, what you owned, what you did and what you changed. Choose a real example with a real lesson, and end on the process change you made, not on blame.
Why it is asked: it reveals self-awareness and learning. Read the full explanation: answering failure questions with a story.
How do you track progress and report status?
Track against the plan using a few clear measures, such as tasks done versus planned, risks open and the forecast end date. For example, if 15 of 20 planned tasks are finished, you are three quarters of the way against plan and should say so. Report the same measures at the same rhythm, with bad news first.
Why it is asked: it shows whether your reporting can be trusted.
People and stakeholders
How do you handle a conflict between two team members?
Talk to each separately to hear both views, then bring them together around the facts and the shared goal, and agree a next step. Escalate only if it affects delivery and does not resolve. Avoid taking sides in public. Describe a real case and what changed afterwards.
Why it is asked: project managers mostly lead by influence, not authority. Read the full explanation: conflict stories for behavioral rounds.
How do you deal with a difficult stakeholder?
Find out what they need, which is often a fear about risk, cost or being surprised. Meet them regularly, show progress with evidence, agree how decisions are made and put changes in writing. Staying calm and specific works better than escalating. Name one stakeholder you won over and how.
Why it is asked: stakeholders are part of the work, and some are hard to satisfy. Read the full explanation: handling stakeholders in depth.
How do you lead a team you do not manage directly?
Be clear about the goal and each person's part, make the work visible, recognise contributions and remove blockers fast. Because you cannot rely on position, you rely on trust and clarity. Agree with line managers what time each person can give, and raise conflicts early.
Why it is asked: most project teams are borrowed from other managers.
How do you communicate with senior stakeholders?
Lead with the conclusion and the decision you need, then give the few facts that support it. Use the same format each time, put risks and trade-offs in plain terms and keep detail available but out of the way. Stakeholder communication is a theme of its own in the program manager guide.
Why it is asked: senior people give you very little time. Read the full explanation: talking to senior stakeholders.
Agile and Scrum
What is the difference between waterfall and agile?
Waterfall plans and delivers in sequence, with each phase finishing before the next starts, while agile delivers working output in short cycles and adapts to feedback. The agile principles ask for delivery "from a couple of weeks to a couple of months, with a preference to the shorter timescale" (Agile Manifesto principles). Many teams mix the two.
Why it is asked: it tests whether you can choose a method for the work. Read the full explanation: what the agile principles say.
What is a Sprint, and what events does Scrum have?
A Sprint is a fixed-length event of one month or less in which a Scrum team builds a usable increment. Scrum's events are the Sprint itself, Sprint Planning, the Daily Scrum of 15 minutes, the Sprint Review and the Sprint Retrospective (2020 Scrum Guide). Name what each is for.
Why it is asked: it checks that you know the framework you claim. Read the full explanation: Sprints and Scrum events in depth.
How is a Scrum Master different from a project manager?
The Scrum Guide says a Scrum Master is "accountable for establishing Scrum" and serves the team and organisation (2020 Scrum Guide). A Scrum Master coaches the team on the framework; a project manager is accountable for the delivery of a project's scope, schedule and budget. Some employers combine the two roles.
Why it is asked: titles overlap, and interviewers want to see you understand the difference. Read the full explanation: the Scrum Master role compared.
Tools, fit and your questions
Which tools do you use to plan and track work?
Name the tools you have actually used, such as a ticket tracker, a spreadsheet, a planning board or a scheduling tool, and what you used each for. Say how you chose the tool for the team's size and habits, and that you would learn theirs.
Why it is asked: it tells them how quickly you will be productive.
How do you plan around a hard external deadline?
Work backwards from the fixed date: list what must be done, estimate each part, find the critical path and agree early what can be cut if the date cannot move. Add a buffer for risks, keep stakeholders updated and test the riskiest parts first.
Why it is asked: many launches and handovers have dates that cannot move. Read the full explanation: planning against a fixed date.
Why do you want to be a project manager?
Give a true reason that matches the work: you like organising people around a goal, you enjoy removing blockers, or you want to see work through to delivery. Add one example of where you did this. Avoid answers that stress status and meetings.
Why it is asked: it checks motivation for the job, not just a job.
What questions should you ask the interviewer?
Ask how success is measured for the role, what the current project portfolio looks like, how decisions and changes are approved and how the team gives feedback. See questions to ask the interviewer, and read how a round is organised in interview loops.
Why it is asked: your questions show what you care about. Read the full explanation: good questions to ask the interviewer.
How these interviews are run
Many employers use a structured interview, in which every candidate is asked the same questions in the same order and every answer is scored on the same scale. The U.S. Office of Personnel Management describes the format as designed to measure job-related competencies, asking about past behavior, hypothetical situations or both (Office of Personnel Management). Prepare one real example per theme above, and use the behavioral interview guide for the structure and tell me about yourself for your opening.
- Show how you balance scope, schedule and budget with an example.
- Keep a risk register and bring options, not only problems, to the sponsor.
- Use a change process for scope creep and show the trade-off.
- Know the Scrum events and the limits of each.
- Prepare one real example per theme and say what changed afterwards.
Sources
- Project Management Specialists, Occupational Outlook Handbook — U.S. Bureau of Labor Statistics, 27 Aug 2026
- The 2020 Scrum Guide — Ken Schwaber and Jeff Sutherland (ScrumGuides.org), 1 Nov 2020
- Principles behind the Agile Manifesto (undated page, read 2026-10-24) — agilemanifesto.org, 24 Oct 2026
- Structured Interviews (undated page, read 2026-10-24) — U.S. Office of Personnel Management, 24 Oct 2026
