Project Manager Job Description Template 2026
Last updated: April 28, 2026
A project manager plans, executes, and closes projects by coordinating scope, budget, schedule, and stakeholders, with U.S. base salaries running $75,000 to $105,000 for mid-level and $110,000 to $150,000 for senior technical PMs in 2026, and PMP-certified professionals earning roughly 33% more than their non-certified counterparts according to the Project Management Institute. Below is a ready-to-adapt job description, a salary table from four independent sources, and the JD mistakes that quietly add six weeks to the search.
Devin Hornick. I’m a partner at KORE1, and project management is one of the roles we place regularly across our IT, engineering, and operations practices. Not glamorous. Just consistent. We fill PM openings in software development teams, data engineering groups, infrastructure environments, and construction companies, and the calibration failures are remarkably similar across all of them. The JD starts with a good instinct and ends with fifteen bullet points that describe three different jobs. The template below is the version that actually closes.
Full disclosure. KORE1 earns a fee when a search runs through our project staffing practice. The framework works either way.
What a Project Manager Actually Does
A project manager delivers a defined outcome within agreed scope, budget, and timeline by coordinating decisions across people who don’t share a reporting line and have competing priorities.
That last clause is the whole job. The Gantt chart is a tool. The status update is a byproduct. The actual work is making sure a DevOps engineer in one time zone, a business analyst in another, and an external vendor who responds to email twice a week all understand what they owe each other and when. Without someone making that connection, the project stalls. Usually quietly.
The tools shift by industry. Software development PMs typically run in Jira or Linear with Agile ceremony. Infrastructure PMs work in Smartsheet or Microsoft Project. Construction PMs live in Procore. Healthcare IT implementations usually run in ServiceNow. The software is not the job. The job is scope, schedule, budget, risk, and stakeholder communication, which is why JDs that lead with “must have 5 years in Asana” consistently miss the candidates who actually deliver.
One clarification on titles. A scrum master owns sprint ceremony and removes impediments for one team. A PM owns an initiative that spans multiple teams and delivery cycles. A program manager coordinates a portfolio of related projects against a strategic objective. When a posting says “PM or program manager,” the hiring committee hasn’t decided which role it’s filling, and the candidates who can tell the difference will notice before submitting.
Before You Write the JD: Three Decisions That Change Everything
Most PM searches run into trouble because these three questions weren’t resolved before the posting went live.
How technical does this person need to be? A PM managing a core banking migration at a regional bank needs to read a data flow diagram and ask useful questions about integration architecture. A PM coordinating a marketing campaign rollout does not. The experience bar, the salary band, and the interview structure look different depending on the answer. A JD that doesn’t commit ends up screening on the wrong criteria.
Methodology fit is the second one. An Agile-native PM who has spent six years in two-week sprints will find a six-month waterfall infrastructure project disorienting. Not impossible. Disorienting. The inverse is equally true. If the team is mid-transformation between methodologies, say so in the posting. The PM who thrives in a hybrid environment is a specific profile, not the default, and the pool for it is smaller than it looks.
What authority does this person actually have? Does the PM own the go/no-go on scope changes, or facilitate the decision for someone else? Do they control the project budget or track it for a program director? Candidates who have run high-accountability PM roles and candidates who have been project coordinators with the PM title do not have the same salary expectation. Sorting that out in round two wastes everyone’s time.
Project Manager Job Description Template
This template is written for a mid to senior technical PM at a software or IT organization. For non-technical environments, remove the tool specifics and adjust the experience floor. The italic notes are intake guidance, not part of the posting.
Job Title: Project Manager
Location: [City, State / Remote / Hybrid]
Employment Type: [Full-time / Contract / Contract-to-Hire]
Department: Technology / Engineering / IT / PMO
Reports To: Director of Engineering / VP of Product / PMO Director
About the Role
We’re looking for a project manager to own end-to-end delivery of [specific initiative type, e.g., software releases, infrastructure migrations, ERP implementations]. You will drive requirements gathering, schedule and resource planning, risk identification, and stakeholder communication from kickoff through go-live. This role owns the outcome. Not just the calendar.
What You’ll Do
- Define project scope, objectives, and success criteria in collaboration with stakeholders and the technical team
- Build and maintain project schedules in [Jira / Smartsheet / Microsoft Project] with clearly owned milestones and dependency tracking
- Facilitate sprint planning, backlog grooming, and retrospectives in Agile environments; own waterfall planning documentation in phase-gated projects
- Identify, log, and actively manage project risks and issues, escalating when resolution requires authority above the project team
- Provide regular status reporting to stakeholders and leadership, including executive summaries and steering committee presentations
- Manage vendor relationships where third parties contribute to the project timeline or deliverables
- Conduct post-project retrospectives and deliver documentation capturing lessons for future initiatives
What We’re Looking For
- 3 or more years of project management experience delivering technology or IT projects end-to-end
- Demonstrated ability to manage scope, budget, and schedule simultaneously across teams without a shared reporting line
- Working fluency in at least one PM tool in a production context: Jira, Smartsheet, Microsoft Project, Asana, or equivalent
- Strong written and verbal communication with both technical teams and non-technical stakeholders
- Experience with Agile, Scrum, or hybrid delivery methodologies in a real project environment, not only in certification coursework
Preferred
- PMP certification from the Project Management Institute, or equivalent credential (CAPM, PMI-ACP, CSM)
- Domain experience in [cloud migration, ERP implementation, cybersecurity programs, product development, or similar]
- Familiarity with RAID logs, change control processes, and formal project governance in enterprise environments
Compensation
$85,000 to $130,000 base depending on level, domain specialization, and location. See the salary table below for level-by-level context.
Project Manager Salary Benchmarks: 2026
The Bureau of Labor Statistics classifies this role as Project Management Specialists (SOC 13-1082), reporting a median annual wage of $98,580 in its most recent occupational survey. That figure is a population median across every industry and understates tech, which trends 15 to 25% above the all-industry median. BLS projects 7% job growth for the occupation through 2033, faster than average across the economy.
The certification premium is real and consistent. PMI’s Earning Power survey found PMP-certified professionals in the United States earn approximately 33% more than non-certified counterparts in comparable roles. That spread has held steady for several survey cycles.
| Level | Base Salary (U.S., 2026) | With PMP | Notes |
|---|---|---|---|
| Entry-level / Coordinator | $60,000 to $78,000 | $72,000 to $90,000 | PMP eligibility requires 36 months of experience |
| Mid-level PM | $75,000 to $105,000 | $95,000 to $125,000 | Most common hiring level |
| Senior PM | $110,000 to $145,000 | $130,000 to $165,000 | Tech vertical adds 15 to 20% in most markets |
| Principal / Program Manager | $145,000 to $185,000 | $165,000 to $200,000+ | Enterprise PMO and strategic program ownership |
Sources: BLS May 2023 OEWS, PMI 2023 Earning Power Survey, Glassdoor 2026 salary data, ZipRecruiter 2026 compensation data. Tech markets like Seattle, New York, San Francisco, and Austin add 15 to 25% to every band. Use our salary benchmark tool to build a location-adjusted range before posting.
Four JD Mistakes That Extend the Search
These patterns come up constantly in the PM searches that stall.
Listing every methodology without committing to one. A JD that says “PMP required, Agile certified preferred, waterfall experience needed” is describing someone who can do three things competently at once. They exist. They’re expensive. They also read that combination of bullet points and see a committee-approval process from a hundred yards, which tells them something about what onboarding will look like. Pick a methodology. Say what your environment actually runs.
Scope creep in the requirements section is the second one, and the most common. Every PM posting I see lists stakeholder communication, cross-functional coordination, risk management, status reporting, executive presentations, vendor management, budget ownership, and resource planning as required skills. That’s describing a program manager. Sometimes a VP of Engineering. A JD written to include everything is written to attract nobody in particular, because candidates who can do all of it at a competitive level are reading your JD to decide whether the team has any idea what it actually needs.
PMP as the first screening filter. PMP is a useful credential. It is not a proxy for delivery track record. Three of our last six PM placements in the mid-market tech space came from candidates without active PMP certification who had shipped complex projects in production environments on schedule. Move PMP to preferred unless the role sits inside a formal PMO with certification requirements, or you will cut a large portion of the available pool before the first resume screen.
Finally, compensation ranges that haven’t been updated since 2022. Posting $70K to $90K for a senior technical PM with Agile experience in a tech market will attract coordinators and recent grads. The PM who ran your last infrastructure migration is not in that range.
What Hiring Managers Ask Before Writing the Post
Does this role really need a PMP?
Inside a formal PMO or in a regulated environment with audit requirements, yes, it usually does. Everywhere else, PMP is a positive signal, not a gating requirement. Making it required eliminates a significant share of qualified candidates who spent their early career shipping projects rather than sitting for an exam. We recommend moving it to preferred unless the posting has a specific governance or compliance dimension that demands the credential.
How quickly can KORE1 fill a project manager role?
KORE1’s average time-to-first-submittal for IT project manager roles is under 17 days. The variable is compensation clarity. A defined comp band at market rate with a committed hiring manager typically closes in three to four weeks from kickoff. Open-band postings and multi-round consensus hiring processes add four to six weeks to that. We serve 30-plus U.S. metros and can run the search locally or across markets depending on what the role requires.
Contract or direct hire, which works better for PM?
A discrete initiative with a clear end date fits contract or contract-to-hire well. A PM who needs to own the organizational relationship with a product team through multiple cycles is a direct hire. We’ve filled PM roles both ways. The hybrid model works better for PM than for most roles because the scope is usually defined enough to evaluate on contract before converting to permanent.
PM vs. program manager: does the gap actually matter?
For sourcing, yes. A program manager coordinates a portfolio of related projects against a strategic objective and typically commands a higher salary band. A PM delivers one project. The titles get used interchangeably in postings, which is mostly harmless early in the search and becomes a problem around offer stage when the candidate expected one level of responsibility and the budget was set for another.
Should we post a salary range?
Post it. Salary range disclosure is now required in California, New York, Washington, Colorado, and several other states. Beyond compliance, postings with a visible range attract better-calibrated applicant pools. The fear that a posted range anchors every candidate to the top is overstated. PMs in this market already have a number in mind before they apply. A range at market filters in motivated candidates and filters out the applicants who will walk at offer anyway.
Starting a PM search? Our team has filled project manager roles across technology, engineering, and engineering staffing engagements in 30-plus U.S. metros. Reach out to our team to talk through the scope.