Project manager job description
Project manager is among the least standardised titles you will ever open. In one company it means the person who keeps a plan current. In another it means the person who decides what ships and when. If the description does not say which, you will interview both populations, and the mismatch stays invisible until the first date slips. Below is a description that commits to a version of the job, and the screening judgement underneath it.
The job description
We are looking for a project manager who changes the status rather than reporting it. You will own delivery on work that crosses teams, and you will be the person who says early and clearly when a commitment is at risk.
What you will own
- Plan, sequence and drive projects that span more than one team
- Hold the scope line, and renegotiate it explicitly when it genuinely has to move
- Track the dependencies outside your control and escalate them before they become the explanation
- Run the meetings the work needs and cancel the ones it does not
- Close projects properly, including a written account of what did not get done
What the job needs
- Experience running delivery where the people doing the work did not report to you
- Comfort with a plan that carries real uncertainty rather than hidden padding
- The ability to write a status update a busy executive can act on in one read
Signals we weight heavily
- You have moved a date and told people early
- You have declined a scope change and kept the relationship
- You can name a meeting you killed
What a project manager is actually accountable for
Coordination is visible and status reporting is easy to grade, which is why both get mistaken for the job. What you are paying for is a shorter gap between the moment a project is in trouble and the moment somebody who can act on it finds out.
- A date the business can put in front of a customer without hedging
- Raising a slip while there is still room to do something about it
- Cutting scope on purpose, with the person who owns the outcome in the room
- Chasing a dependency inside a team that does not report to them, repeatedly, without becoming easy to ignore
- Leaving a plan behind that somebody else could pick up mid-flight
Four ways a project manager hire looks right and is not
Every one of these passes a resume screen. Ladders eye-tracking study timed the average initial scan at just 7.4 seconds, which is long enough to check the four signals below and not long enough to check anything that would contradict them.
Looks right
PMP or Prince2 certification
The certification proves familiarity with a methodology vocabulary and the discipline to sit an exam. Neither predicts the behaviour the seat lives on, which is volunteering bad news in week two rather than week six. Require it only if a client contract does.
Looks right
Ran a programme worth a large budget with dozens of people on it
Inside a big programme management office, the project manager is often the person maintaining the plan while a delivery lead makes the calls. Programme size tells you the scale of the room they sat in, not the scope of what they decided. Ask what they chose, not what they coordinated.
Looks right
Immaculate status packs, clean dashboards, a well-kept plan
Artefact fluency is the most portable and least diagnostic skill in delivery. A project that stays green until the week it goes red is a reporting failure, not bad luck. The signal you want is a project that went amber early and came back, which almost nobody puts in a portfolio.
Looks right
Delivered every project on time
One of three things is true: the estimates carried padding, the scope was quietly trimmed without anybody agreeing to it, or the work was never genuinely uncertain. All three are worth knowing. Ask which projects shipped smaller than planned and who signed off on the reduction.
What to ask for evidence of instead
Four questions, and what the answer actually tells you. Take these into your own process whether or not you ever talk to us.
- Tell me about a date you moved. When did you know, when did you say it, and who did you tell first?
- What it tells you: The gap between knowing and saying is the entire role. Candidates who tell the sponsor first, before the number is certain, are describing the behaviour you are hiring. Candidates who waited for the next steering meeting are describing the reason projects surprise people.
- Tell me about the last time you told a stakeholder no on a scope change.
- What it tells you: Whether they carry any weight at all in a structure where nobody reports to them. Listen for what they offered instead. Project managers who only ever say yes are administrators with a calendar.
- Which dependency outside your team broke a plan, and what did you do differently the second time?
- What it tells you: Chasing other teams without authority is most of the job. The second half of the question is the important one, because everybody has been let down once and only some people changed how they work afterwards.
- What did you stop tracking?
- What it tells you: A plan that tracks everything gets read by nobody. This question finds the people who understand that reporting has a cost, and it is very hard to answer from theory.
How Continuity1 runs this funnel
The screening above is the job. These are the numbers it produces when a function owns it end to end, set against the published benchmarks for the same market.
- 1 in 3
- Shortlisted candidates you meet who become the hire
- Aligned engagements run nearer 1 in 2, distant ones nearer 1 in 10. The market takes about 180 applicants to make one hire, and that sifting lands on your team rather than ours.
- Continuity1 tracked engagements
- ~3
- Interviews your team sits in, per hire
- Ashby puts technical roles at 17.6 interviews per hire across the whole process, up 52% since 2021. The rest of that load sits with the function, not with you.
- Ashby talent-trends report
- 1 in 9
- Accepted offers that ghost before joining
- Indian employers report nearly 4 in 10 offers dropped. We lose 1 in 9.
- nasscom community
- 95%
- Offers that close inside your stated band
- 20 of the last 21. A flat fee earns nothing from an inflated offer; a percentage of CTC earns more.
- Continuity1 tracked engagements
Every brief becomes a success profile before sourcing starts, calibrated with the people who will manage the role. That calibration is the step most hiring skips, and it is why a shortlist either matches the job or matches the job advert.
You review a scored shortlist and make the calls. The filtering never lands on your calendar.
Questions teams ask
Project manager, delivery manager or scrum master, which are we actually hiring?
Decide by who owns the date. A scrum master owns a team process and usually owns no commitment to the business. A delivery manager owns a stream of work end to end. If you need somebody accountable for a date across several teams, write that into the description, because all three populations will apply and they barely overlap.
Should our project manager be technical?
They need enough to be lied to unsuccessfully. That is a much lower bar than doing the work and a much higher one than reciting the vocabulary. Ask them to explain the main technical risk on their last project and see whether the answer has any load in it.
How many projects can one project manager carry?
Fewer than the org chart suggests once the work is genuinely cross functional. The constraint is not meeting load, it is the number of relationships they have to keep warm in teams they do not manage. A project manager who starts missing dependencies is usually carrying too many rooms rather than too many tasks.
How do we test for this in an interview?
Describe a project going quietly wrong and ask what they would do in the first week. Strong candidates ask who the sponsor is and what has already been promised externally before they propose anything. Weak candidates start reorganising the plan.
Related