Project Manager Job Description
What a Strong PM Job Description Includes
The best PM job descriptions do three things clearly: they describe the actual scope of projects the PM will own (size, budget, cross-functional complexity), they articulate the reporting structure and stakeholder landscape, and they distinguish between required qualifications and preferred ones. A JD that says everything is required tends to reflect a hiring manager who has not thought carefully about the role.
For candidates, the most important things to evaluate in a PM JD are the project scope described (or not described), what success looks like in the first 90 days, and what methodology the team uses. A JD that says ‘must have Agile experience’ but the role involves waterfall-heavy compliance projects is a signal about either a mismatch or a company trying to sound more modern than it is.
Standard PM Responsibilities by Level
Entry-level PM job descriptions typically include: maintaining project schedules, facilitating status meetings, tracking action items, managing vendor communications, and producing project reports. Mid-level PMs are expected to own scope definition, stakeholder communication, risk management, and budget tracking. Senior PMs and program managers carry full accountability for delivery outcomes, team performance, and executive communication.
If a job description for a titled Project Manager includes predominantly coordinator-level responsibilities, that is either an entry-level role or an organizational misalignment worth surfacing in the interview.
Project Scope and Ownership
Describe the types and scale of projects this PM will own. Be specific about budget range, team size, timeline, and cross-functional complexity. Vague descriptions like 'manage various projects' make it impossible for candidates to self-qualify and lead to screening problems downstream.
Strong example: 'Manage 2 to 4 concurrent enterprise software implementations with budgets ranging from $500,000 to $3M, cross-functional teams of 8 to 20, and 12 to 18 month delivery timelines.'
Weak example: 'Responsible for managing projects across the organization.'
Core Responsibilities
List 6 to 10 core responsibilities. More than 10 usually signals a role that tries to do too much or has not been clearly scoped. Group responsibilities by function: planning and scheduling, stakeholder communication, risk management, team coordination, and reporting.
Write responsibilities as outcomes where possible, not tasks. 'Deliver projects on time and within budget with clear stakeholder communication at each milestone' is clearer than 'manage project timelines, communicate with stakeholders, track budget.'
Required Qualifications
Required qualifications should reflect the minimum for someone to be effective in this role on day one (or within a 90-day ramp). If you say PMP required, you will lose good candidates who have equivalent experience without the credential. If you say 5 years required for a role where 3 years would work, you will miss good mid-level candidates.
For a mid-level PM role, typical required qualifications include: 3 to 5 years of PM experience, demonstrated experience managing cross-functional projects, proficiency in a PM tool, and strong stakeholder communication skills.
Preferred Qualifications
Preferred qualifications signal what would make a candidate stand out but should not disqualify strong candidates who lack them. PMP certification, experience in a specific industry, proficiency in a specific tool, or Agile certification are commonly listed here.
A useful test: if the candidate does not have this qualification but checks all the required boxes, would you still interview them? If yes, it belongs in preferred. If no, it belongs in required.
Reporting Structure and Team Context
Describe who this PM reports to, what team they join, and how they interact with other PMs in the organization. This context helps candidates understand the support structure and growth path. PMs reporting directly to a VP have different accountabilities than PMs embedded in engineering teams.
If this is a new role, say so. Candidates appreciate transparency about whether they are joining an established team or building a function from scratch. Both have appeal to different types of PMs.
How Long Does This Take?
| Milestone | Timeframe |
|---|---|
| Define project scope and team structure | Weeks 1 to 2 |
| Align on delivery methodology with stakeholders | Week 2 |
| Build and baseline project schedule | Weeks 2 to 4 |
| Establish reporting cadence | Week 3 |
| First major milestone or sprint review | Week 6 to 8 |
| Mid-project status review with sponsor | Midpoint |
| Project delivery and retrospective | End date |