What does a project manager do?
A project manager plans a piece of work, runs it to a finish, and keeps everyone informed along the way. The Bureau of Labor Statistics says project management specialists "coordinate the budget, schedule, staffing, and other details of a project." The job mixes planning, tracking, problem solving and a lot of communication.
The BLS page on project management specialists lists duties such as developing project plans with "objectives, funding, schedules, and staff," monitoring costs to stay within budget, and proposing or approving changes to plans. It gives a median annual wage of $102,320 in May 2025 and projects employment to grow 7 percent from 2025 to 2035, "much faster than the average for all occupations."
O*NET OnLine's profile for Project Management Specialists (13-1082.00) starts its task list with "Communicate with key stakeholders to determine project requirements and objectives." Its top transferable skills are judgment and decision making, coordination, time management, complex problem solving and management of personnel resources.
In Canada, Job Bank lists IT project manager under NOC 21222, with a national median of $46.15 an hour, updated November 19, 2025. Project managers in construction or other fields fall under different codes, so check the one that matches your posting.
How were these project manager questions chosen?
They come from the duties listed by BLS and O*NET, matched to the question each duty tends to produce. They are drawn from the job's published duties, not from a survey of real interviews. Nothing here claims to be the most asked list or to show what any named employer asks.
| Duty (BLS and O*NET) | Question it tends to produce | What the interviewer is checking |
|---|---|---|
| Communicate with stakeholders to set requirements and objectives | "How do you start a new project?" | Whether you agree on scope and success before planning |
| Develop project plans with objectives, funding, schedules and staff | "Walk me through a plan you built" | A clear breakdown of work, owners and dates |
| Monitor project costs to stay within budget | "Tell me about a project that went over budget" | Early warning, options and an honest report |
| Monitor milestones and deliverables | "How do you know a project is slipping?" | Measures you track, and how often |
| Confer with project staff to identify and resolve problems | "Tell me about a conflict on your team" | Listening, fairness and a decision |
| Propose, review and approve changes to project plans | "A sponsor adds scope midway. What do you do?" | A change process with cost and time made visible |
Which behavioral questions should you expect?
Behavioral questions ask about real projects, told in STAR order: situation, task, action, result. Interviewers listen for the moment a plan went wrong, what you did in the first few days, and how you kept people informed. Use numbers you can stand behind, such as weeks late or budget used, and say plainly if a project failed.
The STAR method guide covers the structure. The page on missed a deadline handles one of the most common versions.
1. Tell me about a project that fell behind schedule.
What they listen for: when you noticed, what you told the sponsor, and what you changed. A good answer shows you raised it early.
Made-up example answer. Situation: we were moving a team of 40 people to a new ticketing system, and a vendor's data export was three weeks late. Task: as project manager I had to protect the go-live date or reset it openly. Action: I told the sponsor the same day, laid out two options with their costs, and got approval to move training earlier while we waited. Result: we went live two weeks late, smaller than the original slip, and I added a vendor checkpoint to our plan template for later projects.
2. Tell me about a conflict between two team members.
What they listen for: hearing both sides in private, focusing on the work, and making or getting a decision. The page on conflict with a coworker covers the structure.
3. Describe a time you managed a project with no authority over the team.
What they listen for: how you built agreement, used shared goals, and escalated only when you had to. The page on influence without authority fits here.
4. Tell me about a project you would run differently now.
What they listen for: a specific change you would make, and evidence you made it on a later project.
What role-specific project manager questions come up?
Role-specific questions test method: how you plan, track risk, handle change and report status. Interviewers check that you can explain your tools in plain terms and adjust them to the project. A rigid answer that fits only one method tends to score lower than one that explains when you would use each.
5. How do you build a project plan?
What they listen for: agreed goals and scope first, then a breakdown of the work, owners, dates, dependencies and a budget. Mention how you check the plan with the people doing the work.
6. How do you track and manage risk?
What they listen for: a written list of risks with an owner, a rough likelihood and impact for each, and a planned response. Say how often you review it.
Made-up example answer: "I keep a risk log from the first week, with each risk's owner, how likely it is, how bad it would be, and what we'll do about it. I review it with the team every week and with the sponsor at each status meeting. On a past rollout, the log flagged that one engineer held all the knowledge about a legacy system. We paired a second person with him early, which helped when he was out sick during testing."
7. When would you use an agile approach instead of a fixed plan?
What they listen for: a reason tied to how stable the requirements are. The Agile Manifesto values "responding to change over following a plan" while saying "there is value in the items on the right." The Scrum Guide describes Sprints as "fixed length events of one month or less to create consistency."
8. How do you report status to executives?
What they listen for: a short summary, clear colors or flags tied to real measures, decisions needed from them, and risks. Bad news goes near the top.
9. How do you handle a scope change request?
What they listen for: writing it down, estimating its effect on time and cost, and getting a decision from the right person. BLS lists proposing, reviewing and approving modifications to plans as part of the job.
Which situational questions test judgment?
Situational questions describe a problem and ask what you would do first. Interviewers look for an order: understand the facts, tell the people affected, lay out options, then decide or escalate. Asking who owns the decision is often the strongest first step, because it shows you know where your authority stops.
The guide to situational interview questions explains the format.
10. Your sponsor wants the launch date moved up by a month.
What they listen for: what would have to give, such as scope, staff or quality, and a clear set of options for the sponsor.
Made-up example answer: "I'd ask what's driving the new date, because that tells me what really has to be ready. Then I'd work with the team to see what we could deliver a month early. I'd go back with two or three options, each showing what's cut or added and the risk. The sponsor picks, and I'd write the decision down and update the plan the same day."
11. A key team member quits halfway through.
What they listen for: protecting the work they held, a handover plan, and an honest update to the schedule.
12. Two stakeholders want opposite things from the same project.
What they listen for: tying both requests back to the agreed goals and bringing the choice to whoever owns them.
What follow-up questions tend to come next?
Follow-ups test whether your story holds detail. Expect the interviewer to ask how you measured progress, what the sponsor said, or what you would do if your first option failed. Prepare by noting the actual dates, budget and team size in each story, and what you learned from each one.
- "How did you find out the project was slipping?"
- "What did you tell the sponsor, and when?"
- "What tool did you use to track it, and why that one?"
- "What would you do if the team pushed back on your plan?"
How should you prepare for a project manager interview?
Choose four or five projects of different sizes, including one that went badly, and write a STAR story for each. Learn the terms in the posting, such as risk log, scope change or Sprint, well enough to explain them simply. Practise a two-minute status update for one of your past projects as if speaking to an executive.
The free interview question generator lets you paste the job and pick the round, and it returns likely questions, why they come up, and what the interviewer listens for. Project managers often work with the people covered on the product manager, business analyst and software engineer pages, and their questions show what your partners care about.
Prept's Mock room lets you answer out loud on a clock, scores each answer out of 10 and checks it against your resume. It is included in the free plan.