Use this as a neutral starting point for a project manager job description — adapt every line to your own company, team and market. For the writing principles, see how to write job descriptions; for the underlying structure, the job description template.
Role overview
Project management looks different across industries and methods (predictive, agile, hybrid). Stating the domain, the typical project size and the way of working helps the right candidates recognise the role.
What a project manager typically does
The job is mostly coordination and communication. A project manager keeps a clear picture of what needs to happen, removes blockers, manages risks before they become problems, and keeps stakeholders informed with an honest status — not just good news. They rarely do the technical work themselves; their craft is making delivery predictable.
Key responsibilities
- Define scope, deliverables and a realistic plan with the team
- Coordinate people and tasks across the life of the project
- Track progress against time, budget and quality, and surface issues early
- Identify, communicate and manage risks and dependencies
- Keep stakeholders informed with clear, honest status updates
- Facilitate the team’s way of working (e.g. stand-ups, planning, reviews)
- Capture lessons learned and improve how the next project runs
Day-to-day activities
- Running stand-ups or check-ins and following up on actions
- Updating the plan, board or schedule as work progresses
- Unblocking the team and chasing dependencies
- Talking to stakeholders and managing expectations
- Reviewing risks and adjusting the plan
- Preparing concise status reports
Required and preferred skills
Required skills
- Organisation and the ability to hold many moving parts at once
- Clear communication with both technical and non-technical people
- Risk awareness — seeing problems before they land
- Facilitation and gentle accountability without authority
- Comfort with project or work-tracking tools
Preferred skills
- Experience in your domain (e.g. software, construction, marketing, events)
- Familiarity with your method (agile, predictive or hybrid)
- A recognised certification, where genuinely relevant
- Experience managing budgets or external vendors
Education and experience considerations
Project managers come from many backgrounds. Some hold project-management certifications; many move into the role from a domain they know well. Evidence of delivering real projects usually matters more than any single credential.
Set the experience bar to the project complexity. Coordinating a small internal project is very different from running a large, multi-team programme — be honest about which one this is, and treat certifications as preferred unless your context truly requires them.
Example job description template
A generic, editable structure — not tied to any company. Replace every bracketed placeholder.
Hiring a project manager?
Plan the role before you post it. Start from a neutral structure and a free, printable recruitment planning checklist — no signup, no gating.
Common hiring mistakes
- Describing a coordinator role but demanding a senior programme manager (or the reverse)
- Listing a certification as mandatory when experience would serve better
- Ignoring the method — agile and predictive roles attract different people
- Confusing project management with doing the technical work itself
- Leaving out stakeholder and decision-making context, the heart of the job
Interview considerations
- Ask the candidate to describe a project that went wrong and how they handled it — recovery says more than a smooth story.
- Explore how they manage a slipping deadline and an unhappy stakeholder at the same time.
- Check how they handle accountability without direct authority over the team.
- Rate every candidate on the same competencies with a shared scorecard.
For ready-made questions and a way to compare candidates fairly, use the interview question bank and the hiring scorecard guide.