PMP Project Manager Job Description: Skills, Roles & Salary

I have written, reviewed, and rewritten more PMP project manager job descriptions than I can count, both as a hiring manager building out PMOs and as a consultant helping HR teams attract the right candidates. The truth is that most job descriptions for PMP project managers read like an unfocused wish list. They include every possible responsibility, every nice-to-have skill, and every loosely related certification, which means they actually attract no one specifically and lots of people generally.

PMP Project Manager Job Description: Skills, Roles & Salary

In this guide I will share the structure I now use when writing or evaluating PMP project manager job descriptions. I will cover the core responsibilities a credible role must include, the skills you should require versus prefer, the salary ranges I see in the market right now, and the screening questions I use to separate strong applicants from polished ones. I will also include a one-page sample job description that HR teams can reuse and adapt. By the end you should be able to write a posting that attracts the right candidates, not just the most candidates.

Why Good Job Descriptions Matter

I have noticed that the quality of a job description is the single strongest predictor of the quality of the candidate pool. A vague description gets vague candidates. A precise description filters effectively even before the screening call. The reason is simple: strong project managers self-select. They read a job description and ask, "Does this describe the work I want to do for the next three years?" If the answer is unclear, they move on.

A second reason matters too. Job descriptions are an artefact of organisational thinking. If you cannot describe the role precisely, you probably have not thought about it precisely. That muddiness shows up later as scope creep on the role itself, misaligned expectations during onboarding, and high turnover.

The job description is the first impression of your organisation that a candidate experiences. Treat it accordingly.

That mental model has shaped how I structure every job description I write. The rest of this article walks through that structure.

Anatomy of a PMP Project Manager Role

A good PMP project manager job description has six core sections:

1. Role summary. Two or three sentences describing the role's purpose and outcomes.
2. Key responsibilities. Six to ten bullets describing what the person will actually do.
3. Required qualifications. Education, certifications, experience, and non-negotiable skills.
4. Preferred qualifications. Nice-to-haves that distinguish strong candidates.
5. Compensation and benefits. Salary range, bonus structure, equity if applicable, benefits highlights.
6. About the team and culture. Three to five sentences about the team, leadership, and what makes the role distinctive.

Every section needs to be lean. Bloating any one of them dilutes the rest. A two-page job description is much stronger than a four-page one.

Core Responsibilities

The responsibilities section is where most job descriptions go wrong. They list activities ("manage stakeholders") without specifying scope, context, or outcome. Here are the responsibility categories I include for almost every PMP project manager role:

• Scope management. Define and maintain project scope. Manage scope changes through formal change control.
• Schedule management. Build, maintain, and communicate detailed project schedules. Identify and manage critical path.
• Cost management. Develop project budgets. Track actuals against plan using earned value management techniques.
• Quality management. Define and verify quality standards for deliverables. Manage cost of quality.
• Risk management. Maintain a risk register. Lead qualitative and quantitative risk analysis. Implement risk responses.
• Stakeholder management. Identify, analyse, and engage stakeholders across the project lifecycle. Maintain a stakeholder register.
• Communications. Establish reporting cadence, executive updates, team comms, and document repositories.
• Team leadership. Build, develop, and maintain a high-performing project team. Resolve conflicts and coach members.
• Vendor management. Manage third-party vendors, contracts, and statements of work where applicable.
• Project governance. Maintain documentation aligned to organisational PMO standards. Participate in portfolio reviews.

Each responsibility should specify the scope it applies to (a single project, a workstream, a programme) and the cadence (continuous, monthly, quarterly).

Required Technical Skills

The required technical skills section should be tight and honest. Include only what you actually require, not what would be nice. A useful filter: would you reject an otherwise excellent candidate who lacked this skill? If not, it belongs in preferred, not required.

For specialised industries you will add to this list. Construction projects require knowledge of trades and safety standards. IT projects require infrastructure or software delivery fluency. Financial services projects require regulatory awareness.

Required Power Skills

Power skills are what PMI used to call "soft skills". I prefer the new term because it acknowledges that these are not soft; they are often the hardest skills to develop and the most differentiating. For a PMP project manager I look for:

• Communication. Clear, concise, and contextually appropriate across executive, peer, and team audiences.
• Active listening. The ability to summarise back what someone said before responding.
• Negotiation. Comfort with respectful disagreement and finding common ground.
• Conflict resolution. Familiarity with collaborate, compromise, smooth, force, and withdraw modes.
• Critical thinking. The ability to evaluate trade-offs rather than seek immediate solutions.
• Emotional intelligence. Self-awareness, self-management, social awareness, and relationship management.
• Adaptability. Comfort changing approaches when context changes.
• Influence without authority. The single most important skill for project managers.
• Decision-making. Comfort making decisions under uncertainty with incomplete information.
• Servant leadership. Putting the team's success ahead of personal recognition.

The way to test these in interviews is through behavioural questions, not self-assessment. Anyone can claim emotional intelligence; few can tell a specific story that demonstrates it.

The PMI Talent Triangle Applied

PMI's Talent Triangle has three sides: Ways of Working, Power Skills, and Business Acumen. A strong PMP job description balances all three.

The most common failure I see is overweighting Ways of Working at the expense of Business Acumen. Project managers who cannot tie their work to business outcomes get passed over for promotion and limit their compensation. A senior PMP role description should be explicit about the business acumen expected: P&L exposure, vendor negotiation, regulatory awareness, strategic planning contribution.

A project manager who cannot tell you why their project matters to the business is delivering activity, not outcomes.

Educational and Certification Requirements

I keep educational requirements light unless there is a specific reason not to. Most PMP project manager roles can be filled by someone with a bachelor's degree in any discipline plus the PMP credential. Specialised industries (engineering construction, biotech, defence) may require domain-specific degrees.

For certifications, the hierarchy I use is:

• Required: PMP for senior roles; CAPM or PMP for mid-level
• Preferred: PMI-ACP, CSM, or equivalent agile credential
• Preferred for senior roles: PgMP for programme manager candidates
• Industry-specific: PMI-RMP for risk-heavy programmes; PMI-SP for schedule-heavy programmes

For mid-level roles where you want to attract candidates working towards PMP, the language to use is "PMP certification or PMP-eligible (working towards within 12 months of hire)".

Years of Experience by Level

Years of experience are a clumsy proxy for skill, but they remain a useful filter. Here are the bands I typically use:

These bands flex by industry. Construction project managers typically work on larger budgets earlier in their careers than IT project managers. Consulting project managers often span a wider range of scopes than internal project managers.

Salary Ranges in 2026

Compensation data for PMP project managers in 2026 reflects continued strong demand. Here are the medians I am seeing in the US market:

Total compensation typically includes base, bonus, and sometimes equity. Bonus targets range from 10 percent at junior levels to 30 percent at director level. Equity is common in tech but rare in financial services and construction.

Geographic and Industry Variations

Salary varies enormously by geography. As a rough rule:

• San Francisco, New York, Seattle: Add 25 to 40 percent to the medians above
• Boston, Washington DC, Los Angeles: Add 15 to 25 percent
• Chicago, Dallas, Atlanta: Roughly at the median
• Smaller cities: Subtract 10 to 20 percent
• Remote with national pay: Roughly at the median, sometimes higher

International data is messier. The UK runs 20 to 30 percent below the US median in pound terms; Australia is closer to the US median; India and South-East Asia are significantly below, though the gap is narrowing for senior remote roles.

Industry variations are also significant:

Sample One-Page Job Description

Here is a complete sample job description for a senior project manager role. HR teams can adapt this for their context.

Senior Project Manager, Digital Transformation

Reports to: Director of Programme Delivery

Location: Hybrid, three days in office (Chicago HQ)

Compensation: USD 145,000 to USD 175,000 base, 15 percent target bonus

Role Summary

We are looking for an experienced senior project manager to lead concurrent digital transformation initiatives across our retail and operations functions. You will work directly with executive sponsors to deliver multi-million dollar programmes with measurable business impact. This is a hybrid delivery role combining predictive infrastructure work with agile product development.

Key Responsibilities

• Lead end-to-end delivery of two to three concurrent transformation projects with combined budget of USD 8M to USD 15M
• Develop and maintain project plans, schedules, budgets, and risk registers
• Apply earned value management to forecast and report project performance to executive sponsors
• Manage cross-functional teams of 12 to 25 people including third-party vendors
• Conduct formal change control for scope, schedule, and budget changes
• Facilitate steering committees with C-suite stakeholders fortnightly
• Mentor and develop two to three junior project managers
• Contribute to PMO standards and methodology evolution

Required Qualifications

• PMP certification, currently active
• Bachelor's degree in any discipline
• 8 or more years of project management experience including at least 3 years on programmes over USD 5M
• Proven experience with hybrid delivery approaches
• Strong working knowledge of MS Project or Smartsheet
• Excellent written and verbal communication skills

Preferred Qualifications

• PMI-ACP, CSM, or equivalent agile certification
• Experience in retail or consumer goods
• Familiarity with Power BI or Tableau for executive reporting
• Prior PMO contribution experience

About the Team

The Digital Transformation team is part of our enterprise PMO and reports to the Chief Operating Officer. We are a 14-person team running approximately USD 80M in concurrent project investment. We work in a hybrid model with strong support for flexible hours and continuous learning.

This is a deliberately tight description. It tells the candidate everything they need to know in under one page.

Screening Interview Questions

Once you have applications, the screening interview separates strong candidates from polished ones. Here are the screening questions I use:

1. Walk me through the largest project you have personally led. Look for scope, budget, team size, and a clear personal contribution.
2. How do you build a schedule from scratch? Look for WBS, dependencies, critical path, and resource levelling.
3. Tell me about a project that did not go to plan. Look for ownership, learning, and reasonable composure.
4. What is your approach to risk management? Look for a repeatable process: identification, analysis, response, monitoring.
5. How do you handle a stakeholder who keeps changing their mind? Look for facilitation skills and decision discipline.
6. What does servant leadership mean to you? Look for specifics rather than platitudes.
7. Why are you looking to leave your current role? Look for forward-looking motivation rather than complaints.
8. What is your salary expectation? Look for researched ranges and reasonable flexibility.

A 30-minute screen with these eight questions will typically distinguish the top quartile of applicants.

Common Job Description Mistakes

• Endless requirements. Twenty bullet points of "required" skills, half of which are clearly preferred.
• Buzzword salad. "Synergistic", "dynamic", "fast-paced" tell the candidate nothing.
• Vague scope. "Manage projects" without specifying size, complexity, or domain.
• No salary range. Many jurisdictions now require it, and candidates expect it regardless.
• Endless culture fluff. Two paragraphs of generic culture language without anything specific.
• Inflated titles. Calling a role "Senior Project Manager" when the responsibilities and budget map to Project Manager.
• Missing reporting line. Candidates want to know who they report to and how the team is structured.
• Outdated methodology references. Mentioning waterfall as if it is the default in 2026.

Tailoring for Different Industries

The same job description structure works across industries, but the specifics need to change. Here is what shifts:

IT and software:

• Emphasise agile and hybrid delivery
• Reference DevOps, cloud, and digital transformation
• Smaller budgets, faster cadence, more frequent releases
• Stronger emphasis on product orientation

Construction:

• Larger budgets, longer durations
• Emphasis on safety, subcontractor management, regulatory compliance
• Stronger emphasis on physical site presence
• Critical path management on a much larger scale

Consulting:

• Concurrent client engagements
• Strong emphasis on client communication
• Business development contribution expected at senior levels
• Travel requirements explicit

Healthcare and pharma:

• Strong regulatory awareness (FDA, HIPAA)
• Long project durations
• Validation and qualification expertise often required
• Patient safety as a paramount consideration

Financial services:

• Regulatory awareness (SOX, Dodd-Frank, MiFID)
• Heavy stakeholder management complexity
• Strong audit trail and documentation expectations
• Vendor risk management capability

Author

Shashank Shastri

Coach & Mentor/317 articles

Shashank Shastri is a PMP trainer with over 14 years of experience and co-founder of Oven Story. He is an inspiring product leader who is a master in product strategies and digital innovation. Shashank has guided many aspirants preparing for the PMP examination thereby assisting them to achieve their PMP certification. For leisure, he writes short stories and is currently working on a feature-film script, Migraine.

Questions people ask

01

How long should a project manager job description be?

One to two pages. Longer than two pages and candidates skim. Shorter than one page and you have probably underspecified.

02

Should PMP be required or preferred?

For senior roles, require it. For mid-level roles, prefer it but consider strong CAPM holders. For junior roles, neither is required.

03

How do I attract candidates without inflating titles?

Be honest about scope and pay competitively. Title inflation creates resentment when candidates discover the misalignment.

04

Should I include the salary range?

Yes. Many jurisdictions require it, and candidates expect it regardless. Posting without a range filters out top candidates more than weak ones.

05

How do I handle remote versus on-site requirements?

Be explicit. "Hybrid, three days in office" is much more useful than "flexible work arrangements".

06

How do I write a job description for a programme manager versus a project manager?

Programme managers oversee multiple related projects with shared outcomes. Project managers oversee a single project. The difference shows up in scale, team structure, and strategic alignment expectations.

07

Should I list every benefit?

No. Highlight three to five distinctive ones. Generic benefits (healthcare, 401k) can be mentioned summarily.

08

How do I attract candidates from outside my industry?

Make the transferable skills explicit. Many strong project managers can work across industries with short ramp time.

09

What is the ideal interview process length?

Three to five rounds for senior PM roles. Six or more is excessive and loses candidates.

10

How do I assess cultural fit without bias?

Use structured behavioural questions consistently across candidates. Avoid casual conversation as a proxy for fit.

11

How do I handle candidates who do not yet have PMP?

For mid-level roles, consider "PMP eligible, with certification within 12 months of hire" as an alternative.

12

How do I differentiate a job at a smaller company from one at a larger company?

Highlight scope and autonomy at smaller companies; scale and resources at larger ones.

13

How quickly should I respond to applications?

Within five business days for an initial screen decision. Slower processes lose top candidates to faster competitors.

14

Should I require a cover letter?

Optional but useful for senior roles. Make it clear it is optional to avoid filtering out strong candidates who do not write them.

15

How do I structure a panel interview?

Two to four panellists, each focused on a distinct lens (delivery, stakeholder management, leadership, technical). Sixty minutes total.

16

How do I assess agile fluency?

Ask about a specific hybrid project they have led, what worked, and what did not. Generic agile questions get generic answers.

17

What is the biggest red flag in a candidate?

Inability to take ownership of a failure. If every problem was someone else's fault, they will be hard to manage.

18

How do I write a description that attracts diverse candidates?

Avoid gendered language, list only truly required qualifications, and emphasise growth opportunities. Tools exist to flag biased language in drafts.

Published 13 Jul 2026