Project manager interview questions — and the CV claims behind them
The delivery, stakeholder and recovery questions project managers actually get, what each is really probing, and which line on your CV an interviewer will press hardest.
What this interview is actually testing
Whether you can run a project that is going wrong — and whether the budgets and team sizes on your CV are ones you controlled or ones you were adjacent to.
The questions, and what each one is really asking
1.Tell me about a project that went off track.
What it probes: The central question of the role. Everyone has one; the signal is in when you noticed, what you told whom, and how early the bad news travelled upward.
2.How do you handle a stakeholder who keeps changing scope?
What it probes: Whether you have a change process or a personality-based approach. Interviewers listen for whether you made the cost of the change visible rather than absorbing it.
3.What did you do when you knew the deadline would slip?
What it probes: Timing and courage. The difference between a PM who escalates in week three and one who escalates in week nine is the whole job.
4.Walk me through how you ran status reporting.
What it probes: Whether reporting was a ritual or a control. A report nobody acts on is an expensive habit.
5.How did you manage a team you had no authority over?
What it probes: Influence without line management, which is most project management. Weak answers describe escalation; strong ones describe having made someone's life easier first.
6.Tell me about a risk you flagged that came true.
What it probes: Whether you keep a real risk register or a compliance artefact. Anyone can list risks; the signal is having flagged the one that mattered.
7.What would you change about how that project was set up?
What it probes: Whether you think about governance and structure or only about execution inside constraints someone else chose.
The CV claim they'll press hardest
A budget or team-size figure — "managed a £4M programme", "led a team of 30".
These are the two most inflated numbers on project management CVs, and interviewers have seen enough to probe them as a matter of routine. "Managed" a budget can mean you owned it, tracked it, or reported on it, and those are three different jobs. "Led a team of 30" often means coordinating across teams totalling thirty people, none of whom reported to you. Both softer versions are respectable and common. What damages you is the follow-up — "who signed off spend?", "how many were direct reports?" — landing on a number you cannot break down, because the recovery from that is visibly awkward and the interviewer will remember it.
Project management interviews are unusually predictable, which cuts both ways. You can prepare thoroughly. So can everyone else, which means the differentiation happens somewhere narrower than most candidates expect.
It happens on timing.
When did you say something?
Almost every question in this interview is a disguised version of one question: how early does bad news travel through you?
“Tell me about a project that went off track” is not looking for a project that recovered. Recovery is nice; it is also frequently luck, or someone else’s heroics, or a scope cut that a sponsor was going to make anyway. What the interviewer is listening for is the date you knew and the date you told someone, and the gap between them.
A PM who escalated in week three of a twelve-week project, was overruled, and documented it, is describing exactly the behaviour that makes a programme survivable. A PM who escalated in week nine, when the slip was undeniable and nobody had any options left, is describing the failure mode that makes senior stakeholders stop trusting delivery functions.
Prepare that timeline explicitly. Most candidates narrate the recovery and skip the part the interviewer actually wanted.
The two numbers that get probed
Budget and headcount are the most inflated figures on project management CVs, and they get probed as routine rather than suspicion.
“Managed a £4M programme” — the follow-up is who signed off spend. Owning a budget, tracking a budget and reporting on a budget are three jobs. All three are legitimate; only one is “managed” in the sense a finance-literate interviewer hears it.
“Led a team of 30” — the follow-up is how many were direct reports. Very often the honest answer is none, and the thirty were spread across four functions who had their own line managers and their own priorities. That is harder work than managing thirty reports, and describing it accurately makes the point better than the inflated version does: “no direct authority over any of them, which is why I spent the first month making the two team leads’ reporting easier so they would tell me things early.”
The reason this matters more than usual for PMs is that the softer version is genuinely more impressive to anyone who has done the job. The inflation buys you nothing and costs you the follow-up.
Influence without authority
The question about managing people who do not report to you is where senior candidates separate themselves, and the weak pattern is consistent: escalation as a first tool.
Strong answers almost always contain an act of unsolicited usefulness that preceded the ask — taking a reporting burden off someone, fixing a dependency before it was raised, absorbing a meeting. Influence is banked before it is spent, and interviewers who have run projects recognise the shape immediately.
Preparing
Write down, for each project on your CV: the budget and what your authority over it actually was, the team size and how many reported to you, the date you first knew it was at risk, and the date you escalated.
Where the CV and that document disagree, change the CV. Our free claim checker flags lines that invite a follow-up, and the STAR guide covers the answer structure — with the note that for this role, the “when” matters as much as the “what”.
Questions about the interview itself
- What questions are asked in a project manager interview?
- Expect a heavy behavioural emphasis: a project that went wrong, a difficult stakeholder, a missed deadline, a risk that materialised, and how you influence people who do not report to you. Methodology questions (Agile, waterfall, hybrid) appear but are rarely decisive — teams care more about whether you escalate early than which framework you name.
- How should I answer 'tell me about a failed project'?
- Choose one where you saw it coming and said so. The interviewer is not testing whether your projects always succeed; they are testing when bad news reaches you. Be specific about the date you knew, who you told, and what changed as a result. A project that failed after a documented early escalation reflects far better than one that succeeded on heroics.
- Do I need PMP or PRINCE2 to get a project manager job?
- It depends heavily on sector — regulated industries and large enterprises often filter on it, while product and tech companies frequently do not. Read the posting: if a certification is listed as required, its absence is a screening problem rather than an interview problem, and no amount of interview preparation fixes it.