Questions to Ask in a Project Manager Interview
For project manager candidates at the point in the interview where you are asked whether you have any questions. The 52 questions follow the order that conversation tends to take: the projects you would run and the state they are in, methods and tools, how scope, budget and deadlines get decided, your authority over a team that reports elsewhere and the sponsors behind the work, how success is judged and where the job leads, and the ones to end on. The note under each says what a good or a worrying answer sounds like, or what to do with it.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The projects
What projects would I be running in my first six months, and what state is each one in?
Why ask it
Ask for names, sizes and stages, not a description of the portfolio. A good answer sounds like 'two in delivery and one waiting for approval', with a word on how each is going. If nobody can say what you would run, the work may be handed out after you arrive, and you would be accepting a job without knowing what it is.
Is this a new position, or would I be replacing a project manager who left?
Why ask it
A predecessor who was promoted or moved to a bigger project is a good sign for the seat. If they left the company, ask how long they stayed and what they found hardest, and listen for whether the answer is about the person or the job. With a new position, someone has been running these projects on the side until now, and it matters whether they are glad to hand them over.
How many projects does a project manager here usually carry at once?
Why ask it
The number means little without the sizes, so ask for the largest and the smallest on one current PM's plate. One large project is a job of depth, and six small ones is a job of switching between them all day. 'As many as it takes' is the answer to worry about.
How big is a typical project here in budget, team size and length?
Why ask it
Set the answer beside the largest thing you have run. If it is a step up, say so and say what you would need, which goes down better than being found out later. Length matters as well: on projects that run for years you may not see one finish for a long time.
What is the hardest thing about the project I would pick up first?
Why ask it
The difficulty can sit in the technical work, in a date nobody believes, or in a relationship that has gone sour, and each makes for a different first month. An interviewer who names it without hedging is likely to be straight with you later. If everything is said to be going well, ask what made filling this role a priority.
Is any of the work I would inherit behind schedule or over budget right now?
Why ask it
A late project somewhere on the list is ordinary and no cause for alarm by itself. What matters is whether the people above already know. If the status still reads green and you would be the one to change it, that conversation is your first month.
If I took over a project already under way, who would hand it over, and how long would we overlap?
Why ask it
Taking over mid-flight means living with a plan, a budget and promises you did not make, and the person who made them is the only full record of why. A stretch of working side by side is a real handover. A folder of documents from someone who has already gone means your first month is spent finding out what was agreed out loud.
Are the projects for internal teams, for paying clients, or both?
Why ask it
Client work brings a contract, billable hours and someone outside the building who can refuse to sign off. Internal work has no contract, which makes it easier for priorities to shift under you. In both cases you will want a named person who speaks for the customer from week to week.
Where do projects come from, and who decides which ones go ahead?
Why ask it
Some places have an intake step with a business case and a ranking. In others a project starts because a senior person asked for it. Ask what was last turned down: an organization that never says no to a project is usually running more than it can staff.
What kind of project tends to go wrong here, and why?
Why ask it
A thoughtful interviewer can name the pattern: dates promised by sales, a supplier who runs late, specialists shared across too many teams. Whatever cause they give will be waiting on your projects too, so the useful part is what has already been tried against it. A flat 'none' suggests the reviews after a project are not very frank.
Method and tools
Which project management methodology do you use: Agile, waterfall or a mix?
Why ask it
The name of the method matters less than who chose it and how strictly it is followed. 'A mix' deserves a second question, since it can mean fixed dates with sprints in between and a project manager reconciling the two. If your training is in one approach, find out how much of it you would get to practice.
What software do you plan and track projects in, and could a project manager change it?
Why ask it
The names tell you how much there is to learn, and the second half whether you would run your own setup or keep up someone else's. The detail that costs time is who enters progress. A project manager who types in everyone's updates by hand loses hours to it every week.
Is there a PMO, and what does it require from each project?
Why ask it
A project office can be a help, with templates and someone to ask, or mainly an inspector. Find out which documents are mandatory and who reads them once they are filed. Where there is no PMO you would set your own standards, with nobody to back you when a stakeholder objects to them.
What does a project manager's week look like here, meeting by meeting?
Why ask it
Have them count the standing meetings: stand-ups, steering groups, status calls, one-on-ones. Whatever is left is the time for planning, chasing and thinking. If nothing is left, ask when the plan gets updated, because the honest answer may be evenings.
What does a status report look like here, and what happens when a project goes red?
Why ask it
Red, amber and green are common labels, and what follows a red differs a great deal between employers. Where it brings help, people report honestly. Where it brings a grilling, projects stay green until the week they fail, so the story to get is the last project that went red and what became of its project manager.
How are projects estimated, and who does the estimating?
Why ask it
Estimates from the people who will do the work tend to hold up better than figures committed on their behalf. If the date arrives first and the estimate is made to fit it, you have learned how planning works there. A good follow-up is whether anyone compares estimates with what the work really took.
How are risks tracked once a project is under way?
Why ask it
A risk register proves little by existing, because plenty are filled in at kickoff and never opened again. The test is whether an entry on it has changed a decision lately: money set aside, a date moved, a backup supplier lined up. If nobody can recall one, managing risk would be something you build yourself.
When a project finishes, is there a review, and what changed after the last one?
Why ask it
Lessons-learned files that nobody reads are ordinary. One specific change, such as a new sign-off step or a supplier dropped, shows that the organization learns from its projects. Notice whether the review they describe was about what happened or about who was at fault.
How much hands-on work does the project manager do besides managing the project?
Why ask it
On smaller teams the project manager may also write requirements, run testing or handle the supplier account. That can suit you or swamp you, depending on the number of projects. It usually turns on whether a business analyst or a coordinator works alongside, or whether those tasks are simply yours.
Scope and budget
Who sets the deadline on a project, and is the project manager asked before it is promised?
Why ask it
This is the question that shows whether the PM plans the work or is handed a plan. Being consulted, even when overruled, means your estimate is on the record. If dates come from sales or from the top and arrive as facts, expect to spend the job explaining why they are slipping.
When a stakeholder asks for something new partway through, how does that get decided?
Why ask it
A working change process has a person who can say 'yes, and it adds two weeks'. Without one, extras are absorbed quietly until the date breaks. Ask how the last sizable change was handled and whether the deadline moved with it.
Does the project manager own the budget, or report on a budget someone else controls?
Why ask it
Owning it means approving spend and answering for the variance. Reporting on it means explaining numbers you could not influence. Spending limits are set by each employer, so ask what you could approve on your own signature there.
Think of the last project that got squeezed. Did you cut scope, move the date, or add money?
Why ask it
Most organizations lean on one of the three, and it is not always the one in the handbook. If the real answer is a fourth, that the team worked nights and weekends, you have learned what a tight plan costs there. Who made the call matters as much as what it was.
How much contingency goes into plans and budgets, and who can release it?
Why ask it
A plan with no slack has nowhere to put the first surprise. Listen for whether buffer is allowed openly or has to be hidden inside task estimates, which tells you how much candor the planning can bear. If a sponsor holds the reserve, ask how a PM goes about requesting it.
Are the dates on the current projects tied to something outside, such as a contract or a launch, or were they chosen in planning?
Why ask it
A date with a contract or an event behind it is unlikely to move, so scope or money has to. A date picked in a planning meeting can often be renegotiated with evidence. Knowing which kind you hold tells you what to argue about when the plan gets tight.
If a plan I inherit turns out not to be achievable, what would you want me to do?
Why ask it
The answer you are hoping for is 'tell us early, show the evidence and bring a new date'. 'We need you to make it work' suggests replanning is off the table and the blame has been assigned in advance. Either way you know how your first hard conversation would go.
Has a project here ever been stopped before it finished, and who made that call?
Why ask it
Being able to cancel a project is a sign that someone is really governing the portfolio. Where nothing is ever stopped, failing projects run on, and a project manager can be tied to one for a long time. What became of the team afterward tells you the rest: if they moved on to good work, people will feel safe raising doubts about the next one.
How much of the delivery depends on outside vendors, and who manages those contracts?
Why ask it
If procurement or a legal team holds the contract, the PM can end up chasing a supplier with no leverage over them. Ask whether the PM is in the room when the supplier's dates and terms are agreed. A signed contract with dates you never saw is an easy way to inherit a slip.
When someone on the team misses a commitment, what can the project manager do about it?
Why ask it
Ask for the steps in order: a direct word, a talk with their manager, the sponsor. A good answer includes a recent case where it worked. If the only tool is persuasion and the line managers side with their own people, the plan's dates are requests.
Are team members dedicated to one project, or split across several?
Why ask it
Rough percentages are enough. Someone spread across five projects is rarely free on the day yours needs them, and the plan has to allow for that. The other half of the answer is who decides when two projects want the same specialist.
Where are the people on these projects based, and do any of them work for a contractor or an offshore team?
Why ask it
Distance changes the mechanics of the job: when a stand-up can happen, how long a question waits for an answer, who misses the decisions made in the corridor. People employed by a contractor add a second chain of command on top of that. Handoffs between an outside team and the in-house one are a common place for a plan to lose days, so it helps to hear how they are run today.
Does every project have a named sponsor, and how much time does that person give it?
Why ask it
The sponsor is the one who removes obstacles a PM cannot. A name and a regular meeting is the good answer. A sponsor described as 'very senior and very busy' often means decisions wait for weeks, so ask how the last urgent one was reached.
When a project manager escalates a problem here, what usually happens next?
Why ask it
Where escalating is treated as part of the job, it brings a decision within days. Where it is read as failing to cope, project managers learn to sit on problems. A recent example, including how the person who raised it was treated afterward, will show which of the two this is.
Which stakeholders would I deal with most, and which is the hardest to keep satisfied?
Why ask it
A frank interviewer names a person or a department and says what they want. Ask what the previous PM did that worked with them. If everyone is described as supportive, try asking who sends the most change requests.
How much would I deal directly with senior leadership or the client?
Why ask it
Some PMs present to the steering group themselves, and others pass everything through a director or an account manager. Direct contact brings visibility and exposure in equal parts. If someone stands in between, ask how you would learn what they had promised on your behalf.
When two stakeholders want opposite things from the same project, who settles it?
Why ask it
A sponsor or a steering group is the sound answer. If it is the project manager, ask with what authority, because refereeing between two directors without any is a quick way to make enemies of both.
How do project managers and technical leads divide the work between them?
Why ask it
A common split is that the project manager owns the plan and the lead owns how the work is done, with friction over who talks to stakeholders. Where it has rubbed lately is the part worth hearing. It is also a quiet way to learn whether the leads see a project manager as help or as paperwork.
Does the project manager have a say in who joins the project team?
Why ask it
Being able to ask for a particular person, or to turn one down, is real influence over the outcome. If teams are assigned by whoever happens to be free, ask what a PM can do when the skills do not match the work.
Success and growth
How is a project manager's performance measured here?
Why ask it
On time and on budget are the usual measures, so push one step further: what happens to a project manager who ran a project well when it was underfunded from the start? Stakeholder feedback may count too, and how it is collected changes what it is worth. Review systems vary by employer, so get the specifics for this team.
What would you want me to have finished by the end of my first 90 days?
Why ask it
Strong answers are concrete: a troubled project replanned, the steering meeting taken over, a baseline everyone believes. If the answer is learning the business, ask which project you would own outright by then. Write it down, because it is likely to be the yardstick for your first review.
Who would I report to, and have they run projects themselves?
Why ask it
A manager who has carried a late project understands a slipped date differently from one who came up through sales or operations. Neither is disqualifying, but with the second you would spend more time explaining what the job involves. How often you would meet, and whether they look at plans or only at results, tells you how your work would be judged.
What separates the project managers who do well here from the ones who struggle?
Why ask it
You will mostly hear habits: bad news delivered early, good relations with department heads, a grip on detail. That is the local definition of good, and worth comparing with how you work. If the praise is all for firefighting and long hours, the place may run on rescues more than plans.
Is a project judged on delivering to plan, or on whether it produced the benefit it was approved for?
Why ask it
Delivering to plan is within a PM's reach. Benefits usually land months later and depend on people the PM never managed. If you would be held to the second, ask who tracks it after the project closes and whether you would still be involved.
Does the company pay for certifications such as the PMP, or for Agile training?
Why ask it
Policies differ, so ask what applies there: exam fees, study time, renewals. Beyond the money, the answer shows whether project management is treated as a profession in that company or as a task added to someone's job.
Where do project managers go from here: larger projects, program management, or something else?
Why ask it
Bigger projects and a move into program or portfolio work are the usual routes, and they only count if someone has taken them. Where the last two people with this title are now is the evidence. If every former project manager had to leave the company to advance, that is your answer.
How many project managers are there, and do they review each other's plans?
Why ask it
A group of PMs who compare notes is a place to learn and a source of cover when you are away. As the only one, you would be the whole discipline, with nobody to check your thinking. That can be a fine job for an experienced PM and a lonely one for a first.
Closing
Is there anything in my project experience that makes you doubt I could run the work here?
Why ask it
The doubt is usually about scale, industry or method. Answer it once with the single project of yours that comes closest, and keep it short. A reservation you hear in the room can be answered, and one you never hear cannot.
What should I know about these projects that is not in the job description?
Why ask it
It gives the interviewer an opening for the thing they were unsure how to raise: a reorganization, a restless client, a system due to be replaced. Stay quiet after asking. People often fill the pause with the most useful sentence of the interview.
Which project here are you proudest of, and what made it go well?
Why ask it
People describe what they value when they describe a win: a hard date met, a client kept, a team that stayed together through it. Compare that with how you like to run things. It also lets the interviewer talk about something they enjoyed, which does no harm after a run of questions about slipped dates.
Could I talk to someone on a team I would be leading?
Why ask it
Team members will tell you what a project manager is for in that company, which the job description cannot. Ask them what the last PM did that helped and what got in their way. If the request is declined at this stage, raise it again when an offer is made.
What happens after this interview, and is there a project date that sets when you need someone in place?
Why ask it
A kickoff or a departing PM's last day often drives the timetable, and knowing it tells you how fast they will move and how much room there is on a start date. Ask whether a case exercise or a presentation is still to come, so you can prepare for it.
How to use your questions in a project manager interview
Practical guidance for the conversation itself
Before the interview
Work out which kind of project manager they mean
The title covers construction sites, software teams, marketing campaigns and client accounts at an agency. Read the posting for the verbs. 'Coordinate' and 'support' describe a different job from 'accountable for delivery' and 'manage the budget'. The second kind makes the questions under Scope and budget and Authority the ones to bring. For the first, start with The projects and Method and tools.
Find out who you are meeting
A head of the PMO or a delivery director knows how projects are approved, who sponsors them and how budgets are held. A project manager on the panel knows the tools, the meeting load and what a red status really brings. A recruiter knows the timetable and the pay band, and usually little about how the projects run. Sort your questions by who can answer them, and leave training budgets and certification fees for the recruiter if there is one.
Have your own numbers ready
Before you ask how big their projects are, know your own figures: the largest budget you have held, the most people on one team, the longest schedule, the most projects at once. Their answer only means something next to yours. Where theirs is bigger, you can say plainly what the step up would be and what you would need for it.
Lead with the one that could change your mind
The questions usually come at the end, with room for three to five. Open with the one whose answer would decide whether you want the job, which for many candidates is the state of the projects they would inherit or who sets the dates. It helps to write down beforehand which combinations you would not accept, such as a late project with no sponsor and no freedom to replan. Leading people who report elsewhere is ordinary in this job, and so is inheriting a slipped schedule, so the line to draw is around the combination and not any single answer.
In the room
Ask about one real project
'What is your change process?' gets the version from the handbook. 'Tell me about the last project that finished: how was the date set, what changed along the way, and who decided?' gets methodology, scope, sponsor and status reporting in a single story. If time is short, that one request can stand in for half the list. When the story sounds tidier than projects usually are, one 'and how did that go?' is enough. Then move on: an interview is not an audit.
Tie a question to something you have run
A question with your own experience in it does two jobs. 'On my last project the date was promised before the estimate was done, and we spent three months catching up. How does that order work here?' asks what you need to know and shows you have managed the problem. Keep the setup to one sentence.
Frame the awkward ones as planning
Asking what is behind schedule or why the last project manager left can sound like suspicion. Put it the way you would at the start of an assignment: 'So I can think about where I would begin, is any of this work in trouble at the moment?' Interviewers tend to answer a planning question more openly than a challenge.
Borrow their vocabulary
One company's sponsor is another's project owner or executive lead, and a steering group may be called a board or a committee. Once you have heard the interviewer's word, use it. Swapping in the textbook term gains nothing, and when a term is new to you, asking what it covers there is a fair question in its own right.
Reading the answers
Check that authority matches accountability
Put the answers side by side afterward. Being answerable for the date and the budget is normal. Being answerable for both with no say in the estimate, the team or the changes is a job where you carry the blame for other people's decisions. One mismatch is common and workable. Several together are the thing to weigh before you say yes.
Write the first month from what you heard
After the interview, sketch your first four weeks as you would plan them: who you would meet, which plan you would check first, which status you might have to change. Answers with names, dates and budgets in them make that easy. If you cannot write it, the gaps are your questions for the next round, and 'we are agile' or 'leadership is very supportive' will turn out to have told you little.
Trouble that is admitted is not a reason to walk away
Taking over a struggling project can be a good way in, provided the people above know it is struggling and would let you replan it. The warning sign is the opposite case: a project everyone calls fine that somehow needs a new project manager at short notice.
Ask two people the same question
If you meet more than one interviewer, put the question about what gives when a project is squeezed to each of them. Matching answers mean the practice is settled. A director who says scope and a project manager who says weekends have told you something neither would say alone.
Mistakes to avoid
Grading their methodology
Asking whether they 'really' do Scrum, or pointing out that their process is not by the book, makes you sound like someone who will arrive and lecture. Ask how it works and why they chose it. You can form your opinion on the way home.
Asking only about process
Tools and methods are the comfortable subjects, and they rarely decide whether the job is a good one. The answers that do are about people: who sponsors the work, who can overrule you and what you can do when a team member's manager says no. Spend at least half your questions there.
Offering the cure before you have seen the patient
When an interviewer describes a project in difficulty, it is tempting to say how you would fix it. You have heard two minutes of a long story, and a confident fix can sound careless. Ask one more question about it and say what you would want to find out first.
Interviewing for the projects and forgetting the job
The projects on the table will end, some of them within the year. Who you report to, how a project manager is reviewed and where the role leads will still be there afterward. Keep one question from Success and growth for every interview, however interesting the delivery questions are, and one from Closing, so that any doubt about you is said while you can still answer it.