How to Hire an IT Project Manager: 2026 Guide

Last updated: August 12, 2026

By Mike Carter, Director of Partnership Success, KORE1

Hiring an IT project manager in 2026 comes down to scoping which of three jobs you are actually filling, budgeting $99,000 to $130,000 in base pay, and running a short, focused loop that closes in four to six weeks. The scoping step decides the other two. Skip it and the comp debate never settles, the loop sprawls to five rounds, and the person you finally hire is excellent at a job you do not, in fact, have.

Pull up any job board and read ten IT project manager postings. Same bullets. PMP preferred, five years of experience, strong communication skills, familiar with agile. Ten postings, one template. Underneath that template sit three jobs so different that a great hire for one of them fails outright in another.

We run an IT staffing desk at KORE1, and PM reqs are where the quiet money gets lost. A bad developer hire announces itself within a sprint or two. A mis-scoped PM hire looks fine for a quarter. Status reports arrive. Meetings happen. Dashboards stay green. Then a cutover date slides in week eleven, and everybody in the steering meeting discovers, at the worst possible moment and in front of the wrong audience, which of the three jobs they actually needed.

One Title, Three Different Jobs

An IT project manager plans and runs technology projects for the company paying for them. They own the schedule, the budget, the risk register, and the vendor scope, and they carry the go or no-go call when a system change is about to touch production on a Friday night. The title stretches from server migrations to software rollouts, which is exactly the problem.

In practice, the reqs we see break into three shapes. If you are writing the posting right now, our IT project manager job description template has the copy-ready block and the pay bands by project type.

That third row is its own discipline. If your project is an ERP or platform implementation with an integrator attached, you are shopping in a different pool, and our ERP implementation project manager staffing team covers that variant separately.

Last fall, a healthcare software company in San Diego brought us a rescue. They had hired a genuinely skilled delivery PM. Eleven years, a wall of certifications, superb at running two agile release trains at once. They put him on a data center exit. Thirty-four applications, a Broadcom licensing bill that made staying in the colo expensive on purpose, and a hard stop at the end of June when the contract lapsed with no renewal option anybody wanted to price. Ninety days in, there was no cutover calendar, no dependency map showing which applications shared a database, and no rollback criteria for anything. There were velocity charts. Gorgeous ones.

He was not a bad PM. He was the wrong species of PM, and the req that hired him never said otherwise.

The Market You Are Shopping In

The headline numbers say deep pool, and they are technically right. The Bureau of Labor Statistics puts project management specialists at a $100,750 median as of May 2024, projects 6% growth from 2024 to 2034, and expects around 78,200 openings a year over the decade. PMI’s talent gap research goes further, estimating the world needs 25 million new project professionals by 2030. Openings everywhere. Candidates everywhere.

Specific experience is a different market. Project manager appears on a few hundred thousand resumes. People who have personally owned a Saturday night cutover with a regulator watching, or fought eleven change orders down to signature against a fixed-fee SOW, are a much smaller crowd, and they rarely sit on the market past week three.

Our own desk fills IT roles in 17 days on average. PM searches that start with a settled scope run close to that number. The unsettled ones do not, and the difference is never the candidates.

Money, and the Fights It Starts

Ask two salary sites, get two markets. Glassdoor has the average IT project manager around $129,000, with a typical spread from roughly $101,000 to $167,000. ZipRecruiter says closer to $113,700. Both are national, both are self-reported, and the gap between them is mostly a definition problem, because the same title covers a coordinator running intake tickets and a program lead holding a $30 million portfolio.

For budget planning, here is where our placements have landed.

The city-by-city detail lives in our IT project manager salary guide, and the salary benchmark assistant will hand you a band for your metro in about a minute. Then post the number. In this market, an unlisted salary reads as a warning label, and the candidates you most want are the least willing to guess.

Rent the Seat or Fill It

The question almost nobody asks before posting: does this job still exist in eighteen months?

A migration has an end date. A portfolio does not. If the work is a program, a defined thing with a finish line, a contract PM through project staffing is usually the better economics, because you pay for exactly the months you need and the rate can match the phase. If the work is a standing portfolio, PMO leadership, or anything that owns vendor relationships year over year, make it a direct hire and pay for continuity. Contract-to-hire covers the honestly uncertain middle.

We place all three shapes. The mistake we keep meeting is a company that direct-hired for an eight-month migration and spent month nine inventing work for a $130,000 salary.

The Search, Week by Week

1. Write the scope memo first. One page. Which of the three jobs this is, what program it lands on in month one, who it reports to, and what this person can decide without convening a committee. If you cannot fill in the decision-rights line, stop. That argument is cheaper on paper than it is mid-search.
2. Set the band and the model together. Base plus bonus for a standing seat, an hourly range for program work. Check the number against two sources, not one.
3. Source where the type lives. Infrastructure PMs surface through ops communities and referrals from network and platform leads. Delivery PMs come out of product orgs. Program PMs are almost always a referral from somebody who sat across a negotiating table from them. Keyword-matching a job board treats all three as one species, surfaces whoever refreshed a profile most recently, and is more or less exactly how the San Diego hire happened in the first place.
4. Ask for an artifact, not a story. A redacted cutover runbook. A status pack. A marked-up statement of work. Good candidates have these and will share them sanitized. Candidates who cannot produce any artifact at all have usually been near projects rather than on top of them.
5. Run three rounds, no more. Screen, a hard technical round with the delivery team, a final with the sponsor. The full question set is already written. Our IT project manager interview questions guide covers cutover judgment, change control, and vendor scope, round by round, with scoring. Reuse it.
6. Offer inside 48 hours, then land them on something real. Senior PM candidates in this market are holding two or three processes at once, and at anything close to equal money the offer that moves inside two days tends to beat the one still collecting signatures a week later. First week on the job: system access sorted, a stakeholder map, and one deliverable with a date on it. PMs onboard by doing.

The Interview, in One Paragraph

Interview for judgment under constraint, not vocabulary. Anybody can define critical path. The candidates worth hiring can tell you which line in their last statement of work cost them the most, who was allowed to call a rollback at 2 a.m., and what they did when an executive shortened a timeline the engineering lead had already called tight. The loop and the scoring live in the interview guide linked above, and this post will not repeat them. One thing bears restating. The round almost every company skips is cutover and rollback, and it is the round that would have caught our velocity-chart friend inside forty minutes.

Three Searches We Talked Clients Out Of

We charge fees when you hire. Talking you out of a req costs us money, and it is still the right answer about a third of the time.

A Phoenix logistics company wanted a $125,000 direct hire to shepherd a single vendor-run WMS upgrade. Nine months of real work, maybe. They brought on a contract PM at 30 hours a week instead and saved roughly $60,000 against the loaded cost of the permanent seat.

A medical practice group asked for an IT PM and then described, on the intake call, a backlog of ServiceNow tickets and an intake process nobody owned. Not a project. An operations gap. They needed a business analyst and a part-time systems admin, and a PM in that seat would have either quit from boredom or built an empire in self-defense.

And a manufacturer came to us after burning through three PMs in two years, convinced the talent pool was the problem. It was not. Every decision above $10,000 routed through a monthly steering committee that tabled half its agenda, so nothing a PM did could land. The fix was a decision-rights memo their CFO signed in an afternoon. The fourth PM is still there.

Asked on Almost Every Intake Call

Realistically, how fast can this seat get filled?

Seventeen days is our average fill across IT roles, and contract PM seats often beat it. Direct-hire PM searches run four to six weeks when the scope memo exists. When it does not, add three, because your earliest and often best candidates get burned calibrating the req.

Do they need experience in our exact stack?

Mostly no, and stack-matching shrinks the pool for the wrong reason. A PM who has run an Azure migration will manage an AWS one, because the job is dependencies, vendors, and windows rather than console clicks. The exceptions are regulated or genuinely odd environments, Epic in a hospital system, validated manufacturing, anything mainframe-adjacent, where the failure modes are domain-specific enough that an outsider spends a first quarter learning what not to touch. Match the constraint, not the logo.

Should this person report to the CIO or to the business sponsor?

Short answer: to whoever owns the budget the project spends. A PM who reports into IT while the business holds the money escalates into a dead end, and we have watched that movie more than once. If the reporting line and the money genuinely cannot be aligned, which happens in matrixed companies more often than anybody admits, write the escalation path down and get it signed before day one. Otherwise the first real conflict draws the org chart for you.

Is contract-to-hire an honest option here, or a dodge?

Honest, with one condition. C2H works when the uncertainty is real, a new PMO, an unproven program, a culture the PM might not fit. It curdles when it is quietly a six-month audition for a seat you already know is permanent, run at a contract rate, with conversion terms left vague on purpose. Senior candidates can smell the difference, and the strongest ones decline the audition version. Decide which one you are running before you post it.

What should we ask for instead of references?

An artifact. References mostly confirm a candidate is likable, which the interview already told you. A redacted status pack or cutover runbook shows you how they think when nobody is performing. Ask what they would need in week one, too. Strong PMs answer with a list so specific it sounds rehearsed. It is not rehearsed. It is scar tissue.

Ninety Percent of This Happens Before the First Interview

Scope the job. Name the type. Put a number on it, post the number, and ask for artifacts instead of adjectives. Then go shopping. The loop is the easy part once the req tells the truth.

KORE1 has been placing IT talent since 2005 across 30-plus U.S. metros, 92% of the people we place are still in the seat a year later, and in PM hiring specifically that retention number is mostly scope discipline wearing a trench coat. If you want a second opinion on a req before it goes live, or a shortlist against one that is already settled, start the conversation with a recruiter and bring the scope memo. Ten minutes with it beats six weeks without it.