Project Manager Interview Presentation: A Worked Example, Slide by Slide

The presentation round is the one candidates prepare hardest and lose most often, and almost always for the same reason: they build a slide deck about a project instead of a case for their own judgement.

The panel already assumes the project happened. What they can't tell from your CV is what you decided, what it cost, and whether you'd be honest about the parts that went badly. Everything below is built around making those three things unmissable.

The two briefs, and which one you got

Almost every project management presentation task is one of two things, and they need different decks.

If the brief is ambiguous, ask. A one-line email to the recruiter — "should this be a project I've run, or a plan for the scenario?" — is a free win and reads as competence, not confusion.

The worked example below is the retrospective version, because it's the more common of the two and the harder to do well. The prospective structure is at the end.

The eight-slide structure

Two minutes of buffer, deliberately. Panels interrupt, and a deck timed to the second falls apart on the first question.

The worked example

The project below is a system migration, because it's the most transferable shape. Swap the domain; the structure holds.

Slide 1 — The one-liner

"We moved 40,000 customers off a billing system that was going end-of-life in nine months, without a billing outage. I ran it. The interesting part isn't the migration — it's that we cut a third of the scope six weeks in, and that's what made the date."

That last sentence is doing the work. It tells the panel what the presentation is about and gives them a reason to keep listening. Most candidates open with an agenda slide instead, which spends thirty seconds telling people they'll hear things later.

Slide 2 — The situation

• Vendor contract ended in nine months. Hard date, no extension available.
• 40,000 active customers, 11 pricing plans, four of them legacy and undocumented.
• Team of six engineers, shared with a second project that had its own deadline.
• Failure mode: a customer billed twice, or not at all. Both are regulatory problems, not just bugs.

Numbers and a named failure mode. "It was a complex project with tight deadlines" says nothing; the four lines above let the panel picture the constraint themselves.

Slide 3 — My role

"I owned the plan, the sequencing and the stakeholder side. I did not own the technical design — our staff engineer did — and I didn't own the pricing decisions, which sat with finance. What I did own was the decision about what we'd migrate and in what order, which turned out to be the thing that mattered."

Naming what you did not own is what makes the rest believable. Candidates who imply they owned everything get tested on the parts they clearly didn't, and the panel stops trusting the whole account.

Slide 4 — The decision

Six weeks in, we were tracking about three weeks behind.

Three options:

1. Add people. Rejected — onboarding cost would land inside the window we were trying to save.
2. Extend the date. Not available; the contract was the constraint.
3. Cut scope. The four legacy plans, about 1,200 customers, were taking a disproportionate share of engineering time because nothing about them was documented.

"I proposed moving those 1,200 customers onto a current plan manually, before the migration, rather than migrating four plan types nobody understood. It meant a commercial conversation with finance and about three weeks of someone's time doing it by hand."

Three options, one chosen, reasons for the rejections. This is the slide the whole deck exists for, and it should be the one you can talk about for ten minutes if asked.

Slide 5 — What it cost

• Finance had to approve moving customers onto plans that were, for about a third of them, slightly more expensive. We absorbed the difference for twelve months.
• Roughly $40,000 of absorbed cost, and a week of my time getting that agreed.
• Two customers escalated. Both stayed.
• The manual work was tedious and it landed on one person. In hindsight I should have split it.

Slide 6 — How it went

• Migrated on time, three weeks before the contract ended.
• Zero billing incidents in the first cycle. Two in the second, both from the same legacy edge case, both fixed within a day.
• The 1,200 manually-moved customers had a worse experience than the rest, and we knew that going in.

Include the two incidents. A perfect outcome invites the panel to go looking for what you left out; naming the imperfection yourself removes that entire line of questioning and costs you nothing.

Slide 7 — What I'd change

"I'd have gone looking for the undocumented plans in week one instead of week six. I built the plan from the system diagram, which showed eleven plans as eleven equivalent things. Two hours with someone from support would have told me four of them were special. The delay wasn't caused by the legacy plans — it was caused by me finding out about them late."

This is the strongest slide in the deck if it's genuine. The requirement is that the thing you'd change has to be yours and it has to be specific. "I'd communicate more" is what candidates say when they haven't thought about it.

Slide 8 — What I took from it

"I now start every plan by asking which parts of the system nobody wants to talk about. It's a five-minute question and it's found something every time since."

One habit, stated concretely enough that it's clearly real. Not "I learned the importance of communication."

What the panel is doing while you talk

They are not evaluating your slides. They're doing three things:

Looking for the decision. If they get to minute eight without hearing a hard call you made, they'll ask for one — and having it arrive as an answer rather than as your deck is much weaker.

Testing whether the story holds. Expect an interruption on slide 4 or 5. That's a good sign; it means the decision landed and they want the detail. The failure mode is a candidate who can't leave the deck to answer, then returns to the wrong slide.

Watching what you do with a challenge. Someone will disagree with the decision. They may not even think you were wrong — they want to see whether you defend reflexively or engage. The strongest response concedes the part that's fair before defending the part that isn't.

If you got the prospective brief instead

Same spine, different content. Eight slides, roughly:

1. What I understand the goal to be — restated in your words, not theirs
2. What I'd need to know before committing to anything (three to five questions)
3. My assumptions, listed, so they can be corrected
4. The plan, in phases, with the first phase detailed and the rest sketched
5. The risks, ranked, with the top one having an actual mitigation
6. What I'd measure to know it's on track — before the dates slip
7. Who I'd need, and what I'd need from the panel's own organisation
8. What would make me come back and change this plan

Slide 2 is the one that wins this version. A candidate who presents a confident plan for a scenario they were given four paragraphs about has demonstrated that they don't ask questions before planning — which is the exact failure the brief is designed to catch.

Before you present

Rehearse it out loud, timed, at least twice. Not in your head — the deck always runs long when spoken, and the slide that runs long is usually slide 2, which is the least important one.

The questions the panel asks after the presentation are the standard interview set, and they're worth preparing separately: Project Manager Interview Questions. The interruption on slide 4 is really the conflict question in disguise, and there's a guide for holding that steady: the team culture interview.