PM archetype
The Firefighter
Takes the project nobody wants and brings it back on track.
You do your best work when something is breaking. You find the one blocker that matters today, get the right people in the room and turn a red status green.
Top strengths
- Recovery under pressure
- Fast triage of what matters
- Getting owners to commit
Blind spot
Calm projects can feel slow to you, and prevention work gets less of your attention than rescue work.
How The Firefighter works in each role
Project manager.
On a single project, the Firefighter is the person you call when the date is already at risk. Triage is fast: one blocker, one owner, one day. The slip comes after the recovery. Once the status is green, the account of what failed often stays in someone's head, and the next project starts with the same gap. Strong Firefighters leave a short written note on what broke and what changed. On a resume, that note is the source for your before and after.
Program manager.
At program level, the Firefighter steps into the workstream that is red and leaves the rest of the structure alone. That is useful when one vendor is failing or one cutover is stuck. It becomes a pattern when the program keeps producing fires because nobody has time to look at the plan between rescues. The fix is a standing slot to ask why the same kind of problem keeps returning. A rescue record across several workstreams reads as program experience.
Product manager.
In product work, the Firefighter handles the launch that is slipping or the incident that follows a release. The strength here is calm in the middle of a launch. The risk is that urgent fixes crowd out discovery and roadmap decisions, so the team reacts more than it chooses. Good product Firefighters keep a short list of what they chose not to fix this week, and why. On a resume, name the release, the cause and what you changed afterward.
The typical resume mistake
Your resume lists fires, not outcomes: "Handled escalations", "Resolved critical issues".
Examples are illustrative, not from a real client.
Example 1
Before: Handled escalations for critical production issues.
Why Reed flags it: Rule family: handled or resolved with no before and after. The verb names the task, not the change of state. Reed would ask what was different when you left, and where that is written down.
After: Brought the [system name] incident queue from [your starting count] open critical issues to [your end count] over [period], from [your ticket export or incident log].
Example 2
Before: Resolved critical issues under tight deadlines.
Why Reed flags it: Rule family: pressure words with no before and after. "Critical" and "tight" describe the mood of the work, not the state of the project.
After: Took a late [type of project] from [red status and its cause] to [state at handover] by [the one decision you made]. Source: [status report or steering note].
How to fix it
Write the before and after: what state the project was in, what it was when you left, and where that number comes from.
Interview questions to prepare
Tell me about a project you took over in trouble. What did you do on day one, and what did you leave behind?
How to prepare: Pick one recovery from your own record and write three things: the state on the day you arrived, the state on the day you left, and the document that shows both.
How do you stop the same problem from coming back?
How to prepare: Find one fire where you also changed the process afterward and note the change and the date it was agreed; if you did not, say so and say what you would do now.
Common questions
Is a recovery story still a good resume story?
Yes. A recovery makes a good story when the before and after are clear. The trouble is the vague version. A line that names the state when you arrived, the state when you left and the source reads as a recovery. A line that says "handled escalations" may read as a job description.
What if I have no clean numbers from a rescue?
Then leave numbers out. A rescue can be described in states: red to green, release blocked to released, no owner to a named owner. Write what is true and say where it is recorded. Reed asks for the source and never suggests a figure.
For fun and self-reflection only. This quiz has not been scientifically validated. It is not a psychometric, personality or hiring assessment, and should not be used to evaluate anyone for a job.