IT Project Manager Job Description Template 2026

Last updated: August 12, 2026

By Robert Ardell, Co-Founder and Strategic Advisor, KORE1

An IT project manager job description has to name the systems being changed, who owns cutover and rollback, how change control runs, and a pay band near the 2026 market of $99,000 to $130,000. A generic project manager posting states none of that. The copy-ready template is about halfway down this page, and everything above it exists to keep you from pasting the wrong things into it.

There is a quick test for an IT project manager job description. Swap “IT” for “marketing” and reread the posting. If nothing else needs to change, the posting describes a coordinator with a technical-sounding title, and coordinators are exactly who will apply. Cross-functional teams. Stakeholder alignment. A methodology acronym or two. Nothing about the systems, the change windows, or the night the migration actually ships.

An IT project manager delivers change into systems that people are using while the change happens. Payroll runs on the thing being migrated. The warehouse scans against it. Nobody pauses payday. McKinsey and the University of Oxford studied more than 5,400 IT projects and found the large ones run 45% over budget on average and deliver 56% less value than promised. The person you are writing this posting for is the person hired to keep your project out of that data set. The posting should say so.

One honest note first. I co-founded KORE1 in 2005, our project manager staffing desk sits inside the IT staffing services practice, and we bill a fee when a search closes. You can use everything on this page without ever calling us. Most readers will. That is fine. Also, if the seat you are filling never touches production systems, stop here and use our project manager job description template instead. It is built for exactly that role, and this one is not.

Start With the Project, Not the Person

The project type decides what the posting must say and what the seat costs. An infrastructure refresh, a cloud migration, and an ERP go-live are three different hires wearing the same title.

Write the posting for the project you funded. Not for a platonic project manager who can run anything, because that person reads your fifteen identical bullets and applies somewhere that named the actual work.

Those bands line up with the level-by-level detail in our IT project manager salary guide, which breaks the same numbers out by experience and city. The short version is that the project type moves the band more than the years of experience do, and postings priced off a generic PM survey run $10,000 to $25,000 light for migration and ERP work.

The Four Lines Nobody Puts in Writing

Every stalled IT PM search we inherit is missing at least one of these. Usually three.

The change windows. If cutovers run Friday night into Saturday, the posting says so. A medical device client of ours in Carlsbad learned this at the offer stage, when their finalist asked about the go-live calendar, heard “quarter-end weekends, all of them,” and withdrew two days later. Nobody blamed the candidate. The search restarted from zero and the second-choice candidate had already taken a counteroffer. Six weeks, gone, over one sentence the posting could have contained.

Rollback authority. Somebody decides at 2 a.m. whether the migration proceeds or reverses. Say whether that is this role, and if it is, you are hiring for judgment under pressure and the posting should ask for evidence of it. Our IT project manager interview questions guide covers how to test for this once resumes arrive. The posting’s job is to attract people who have actually held that pager. Most have not.

How change control works in your shop. A PM who has only shipped in a move-fast product culture will suffer inside a CAB-gated environment with ITIL change classes and a frozen December calendar, and the frustration shows up by week three as tickets stall behind approvals the posting never mentioned. It cuts both ways. One line fixes it. “Changes go through a weekly CAB and a formal change calendar” tells the right candidate they are home and the wrong one to keep scrolling.

The vendor half. Most IT projects over $500K have an integrator or managed services vendor attached, and managing their PM against a signed statement of work is half the actual job, some weeks the whole job. If your PM will spend Tuesdays pushing back on change orders, the posting should say “vendor management” like it means it, not bury it as bullet eleven.

IT Project Manager Job Description Template

Copy the block, replace every bracket with something true, and delete the italic notes before posting. It is written for a mid-to-senior seat running infrastructure or enterprise application work. Trim the change-control language if your environment genuinely does not have any. Be honest with yourself first.

What the Seat Pays in 2026

IT project managers in the United States earn between $99,000 and $130,000 base in 2026 depending on the source, with Glassdoor reporting a median total pay of $130,000 and ZipRecruiter averaging $113,676.

The spread across aggregators is itself useful information. ZipRecruiter puts the national average at $113,676 as of mid-2026. PayScale reports $99,295 for the same title, and Salary.com shows a level-one IT PM at $82,763, which mostly tells you Salary.com is measuring the junior end. The Bureau of Labor Statistics counts the whole occupation, every industry, and puts the median for project management specialists at $100,750 with 6% growth projected through 2034 and about 78,200 openings a year. Tech runs above that median. Coastal tech runs higher still.

Do not price the req off any single one of these numbers. Price it off the project type table above, sanity-check against our salary guide, and run the specific title and city through the salary benchmark assistant before the band goes to finance. Ten minutes of benchmarking beats a reposted req every time.

Where IT Project Manager Postings Go Wrong

Three failure patterns account for most of the reqs that sit open past week six.

The first one is the reason this page exists. The posting is a generic PM posting, so generic PMs apply, and the hiring manager rejects every one of them for missing something the posting never asked for. The feedback loop runs “no infrastructure background, no cutover experience, no vendor scars” while the req itself still says “manage cross-functional stakeholders,” and nobody connects the rejection reasons back to the paragraph that produced them. Recruiters call this a calibration gap. It is a writing problem. The fix takes an afternoon.

Second, the certification stack. CAPM, PMP, PMI-ACP, CSM, SAFe, ITIL, all listed as required, for a seat where the actual bar is one production cutover and a renegotiated statement of work. Every credential in the required section cuts your pool, and PMP alone removes a lot of people who have shipped more than some certificate holders. Put certifications in preferred and let the delivery record carry the screen.

The third is writing a technical program manager posting at an IT project manager price. If the role coordinates outcomes across four teams with no single budget and no single scope document, that is a different seat and it pays differently. Our interview questions guide has a full breakdown of the adjacent titles, because the sorting matters more before the posting goes live than after.

The Intake-Call Questions

The same handful of questions comes up when clients scope one of these reqs with us. Answers here. Skip the call.

Does the posting need a whole methodology paragraph?

One sentence naming what your environment actually runs beats a paragraph of Agile vocabulary. Candidates can smell committee writing.

Say “two-week sprints in Jira with quarterly release trains” or “phase-gated waterfall with a weekly CAB” and move on. The candidates who fit will recognize their own environment. The ones who do not will filter themselves out, which is the posting doing its job.

Our PM will manage vendors and never build anything. How technical does the posting need to sound?

Technical enough to read an architecture diagram, challenge an estimate, and catch a padded change order. That is a real bar. The posting should state it plainly.

You are not hiring an engineer. You are hiring the person who keeps engineers and vendors honest, and that takes fluency rather than depth. We wrote that line into the template above because clients kept asking for it in intake and then forgetting to put it in the req.

Contract, contract-to-hire, or direct hire for this seat?

Contract wins when the project has a defined end, which most IT projects do. Direct hire wins when this person will run a portfolio after go-live.

An 18-month ERP implementation does not require a permanent headcount. It requires eighteen months of a very specific skill set, and our project staffing practice exists for exactly that shape of need. Month nineteen decides it. If the honest answer is another project, hire direct and say so in the posting, because that changes who applies.

How much more does the IT qualifier cost us?

$10,000 to $25,000 a year over a generalist PM at mid level, and more for ERP and cloud migration work.

The premium is real. You are paying for the cutover scar tissue. It is cheaper than the alternative, which is a generalist learning rollback planning for the first time on your payroll, during your go-live weekend.

How long should this search actually take?

Our average time-to-hire across IT roles is 17 days, and a well-scoped IT PM req usually sees first submittals inside a week.

The catch is the phrase well-scoped. A posting that names the project, the windows, and the band moves at that speed. A posting that says “manage cross-functional stakeholders” moves at whatever speed your applicant pool feels like. If the req has already sat open six weeks, the fix is almost never a bigger job board budget, because budget buys more of the same applicants the posting already attracts. Talk to our team and bring the posting, because the rewrite is usually the whole conversation.

We have filled these seats since 2005, from Irvine to Phoenix to Charlotte, and 92% of the people we place are still in the seat a year later, a number we watch closely because filling the same seat twice helps nobody. The template above is the same one our recruiters use on intake. Steal it.