Program Manager Salary Guide 2026

Last updated: August 7, 2026

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

Program managers earn $118,000 to $155,000 base at mid-level in 2026 and $150,000 to $195,000 at senior, while technical program managers at scaled tech companies clear $240,000 in total compensation. Those bands come from reconciling eight public trackers against reqs our desks actually closed. Take the trackers at face value and the same two words return anywhere from $95,750 to $394,000.

The spread is not the interesting part. This is.

On August 1, 2026, Salary.com benchmarked a program manager with less than one year of experience at $139,315. Same page, same morning, a program manager with more than eight years came back at $143,965.

Eight years of work. $4,650.

That is not a career ladder. It is a rounding error wearing a job title, and it is the clearest evidence I have found that the label has stopped carrying information. Salary.com is not being careless. Their panel is real. The problem is that the panel contains a nonprofit coordinator in Dayton, a bank’s PMO governance lead in Charlotte, and a staff engineer’s counterpart at Meta, and every one of those people checked the same box on the survey.

Four careers, one average. The line had to go flat.

Where my money comes from, so you can weigh the rest accordingly. KORE1 places program and project talent for a fee, and a bigger band means a bigger invoice on our side. Two sections below argue for hiring cheaper than you planned. One argues against opening the req at all. I have been running this company since 2005 and I would rather lose the search than watch a client pay portfolio money for a single-project problem. Our IT staffing services practice covers this desk, and I will tell you plainly when it is not the desk you need.

What Program Managers Actually Earn in 2026

A program manager owns a set of related projects that share a goal, a budget, or a dependency chain, and gets measured on whether the whole set lands rather than on any single delivery date. Project managers own the pieces. The program manager owns whether the pieces add up to the thing the company actually wanted.

That distinction sounds academic until you price it, at which point it turns into roughly forty thousand dollars a year and a decision about whether the person you hire has any standing to tell two directors that their teams are about to collide in March. Companies blur it into a req by accident about once a week.

The bands below blend what the public trackers report against searches we have closed across the 30-plus U.S. metros we cover. Base salary in the third column. Total comp includes bonus and, where it exists, equity, which matters enormously in the technical program management track and almost not at all in the enterprise PMO track.

The row people misprice is the fourth one. A technical program manager is not a program manager who happens to sit near engineers. The job is holding a dependency graph in your head across teams that do not report to you, then telling a VP of Engineering that the date is wrong and surviving the conversation. Companies write that req and budget row two. Every quarter. Somebody does it every quarter.

Every Tracker Has a Different Job in Mind

Salary aggregators disagree about every role. Normal. Different panels, different self-selection, different definitions of base against total. On a job like backend engineer the spread lands inside thirty or forty thousand dollars and averaging gets you somewhere usable.

Program management is not that job.

First row against last row is $144,250. Add one adjective and the median more than doubles.

ZipRecruiter’s absolute floor for the title sits at $38,500. Levels.fyi puts the 90th percentile at $394,000. Ten times, one title, both figures published this year and both defensible inside their own samples.

The Bureau of Labor Statistics lands at $100,750 median for project management specialists as of May 2024, with 6 percent projected growth through 2034 and roughly 78,200 openings a year. That figure is honest and nearly useless for a tech req, because the occupational code it lives in was built for a labor market that includes construction schedulers and clinical trial coordinators.

Same bucket. Very different jobs.

We watched this cost a client eleven weeks last spring. A medical device manufacturer in Irvine approved $112,000 for a program manager to own their FDA submission program, anchored to a national average someone pulled in about ninety seconds. Every candidate who could actually run a regulated submission program was at $150,000 or better. They moved the band in week nine. The person they hired had been in their pipeline since week two, at $148,000.

Eleven weeks of delay to pay the number that was on the table in week two.

The Four Labor Markets Hiding Behind Two Words

Our desks fill four distinct versions of this role. Candidates move between them, but not casually and not in a two-week ramp. Write one req and expect the whole market to answer it and you will get four hundred applicants and no fit.

Technical program management

Engineering-facing. The TPM owns dependencies across services and teams, runs the launch, and translates between an architecture decision and a date the business can plan around. Jira, Linear, and a dependency map that lives in somebody’s head more often than anyone admits. This track pays the most and is the hardest to fill, because the honest job description is “part project manager, part systems thinker, part diplomat, and you will be told no by people who outrank you.”

A TPM who cannot read a design doc is not a TPM. That is the screen. It eliminates more candidates than anything else we test for, and it is the one clients most often ask us to relax.

We do not relax it.

Business and operations program management

Cross-functional work that is not gated on engineering. A customer onboarding program, a compliance rollout, a go-to-market launch spanning marketing, sales enablement, and support. These roles are genuinely hard. They pay ten to twenty percent below the technical track for reasons that have more to do with which budget line they sit in than with difficulty.

That is not fair. It is just true.

PMO and portfolio program management

Governance, stage gates, portfolio reporting, and the quarterly conversation where somebody has to tell the executive team which four of eleven initiatives are actually funded. Heavy in banking, insurance, healthcare systems, and defense. This is where the PMP means the most and where a candidate without one gets filtered out of enterprise pipelines before a human reads the résumé. If you are standing one up rather than hiring into one, our guide to building a project management office covers the sequencing.

Delivery and client program management

Systems integrators, consultancies, and managed services firms. The program manager owns the client relationship, the statement of work, and the margin, which makes it a quasi-commercial role wearing a delivery title. No tracker captures the utilization bonus or the margin kicker, so a candidate walking out of a systems integrator and into your company will quote you base salary, forget the variable piece entirely, and undersell themselves by twenty thousand dollars before you have said a word.

Ask them. They will tell you.

One warning about that table. A résumé claiming all four is almost always a consulting background, which buys you breadth and costs you depth. Sometimes breadth is exactly right. It is usually wrong when the program you are hiring for has already failed once, because a restart needs somebody who will still be there in month fourteen when the same argument comes back around.

They usually will not be.

The Experience Curve That Flatlines, and What It Is Actually Telling You

Back to the $4,650.

Salary.com’s experience tiers for program manager run $139,315 at entry, $139,873 at one to two years, $140,803 at two to four, $142,105 at five to eight, and $143,965 past eight. Plot those and you get something close to a horizontal line. No other role we benchmark behaves this way. Backend engineers roughly double between year one and year eight. Data architects climb nearly as steeply.

This one moves just over three percent.

Two forces are doing this to the curve, and because they pull against each other in ways that vary by employer, the flatness you see on the page is a genuine artifact rather than a claim that experience has no value in this discipline.

The first is title contamination, which I already covered. The second is subtler and it changes how you should read your own internal bands. Program management is one of the few disciplines where seniority gets negotiated at the point of hire rather than earned inside a ladder. Most companies do not have a program manager career track. They have one program manager, or three, reporting to different VPs with different levels attached, and the person’s compensation was set by whatever they were making at the last company plus fifteen percent.

No ladder. No bands. Just history.

So the market rate for a program manager with eight years is not really a market rate. It is a distribution of individual negotiations, and the trackers are averaging those.

The practical version is uncomfortable but useful. Your leverage on this hire is higher than on an engineering hire, because the candidate has less benchmark data they trust. Their leverage is also higher, for exactly the same reason. Whoever walks in with defensible numbers wins the conversation.

It is usually not the employer.

The PMP Premium Is Real. It May Not Be Real for You.

The Project Management Institute’s Earning Power survey, 14th edition, published November 2025 from 14,628 respondents across 21 countries, found U.S. PMP holders reporting a median salary of $135,000 against $109,157 for non-certified peers. Call it 24 percent. Respondents certified more than ten years reported $173,000, against $123,000 for those certified under five. Pharmaceuticals and aerospace topped the U.S. industry list at $150,000.

Those numbers are solid, the sample is large enough to trust, and if you are staffing a portfolio inside a bank or a pharmaceutical company they describe your candidate pool with reasonable accuracy.

Here is the part that matters for a tech req. PMI surveys project professionals, a population weighted heavily toward the PMO and delivery tracks. Among the technical program managers we place, the PMP shows up on maybe one résumé in six, and it has never once been the reason an offer went up. Different population. Different credential economy.

Screen accordingly. Hiring for a regulated portfolio in a bank or a defense integrator, the PMP is close to a hard gate and you should pay for it. Hiring a TPM to untangle a services migration, asking for it narrows your pool over a credential that predicts almost nothing about the work in front of them.

What moves an offer on the technical track is a specific, verifiable program the person owned from kickoff to close. Ask what shipped. Then ask what slipped and why. The second answer tells you more.

Geography, and Why It Matters Less Than It Used To

Program management stayed remote at a higher rate than most technology functions, because the job is coordination and the coordination was already happening over video before 2020. The location premium is real. It is also narrower than it is for engineering, and it has been compressing for three years.

Do not read that table as a ranking. The columns are measuring different things. Levels.fyi reports total compensation from offer letters at companies that grant equity, Glassdoor reports self-submitted averages across a far wider employer set, and stacking them tells you the shape of the market rather than the order of it. Price against the specific employers you are losing candidates to.

Orange County is a useful case because we work it weekly. Irvine, Costa Mesa, and Newport Beach run roughly eight to fourteen percent under the Glassdoor California average for equivalent technical program work. The gap closes fast when the employer is a medical device or aerospace company with a regulated program. Those companies compete against San Diego and against remote Bay Area offers, and they know it.

Remote changes the arithmetic more here than in most disciplines. A senior program manager in Boise working for a Seattle software company is priced against Seattle. Not Boise. If you are a mid-market employer in a secondary metro, that offer is your competition, and the local average is a comfortable fiction.

What Interim and Contract Program Managers Cost

Programs arrive in waves. An ERP implementation, a post-merger integration, a data center migration, or a remediation program somebody committed to in an audit response. Those are nine-to-twenty-month problems that do not justify permanent headcount, which is why our contract staffing volume on this desk runs well above what we see on engineering desks.

One operational note that has cost more engagements than any rate disagreement. Put the interim program manager in the room where decisions actually get made, or do not hire one at all. We watched a $140-an-hour integration lead spend five weeks assembling a status deck because nobody would give them a seat at the steering committee they had been hired to run. They left. The program slipped two quarters.

The steering committee still meets.

Where I Talk You Out of the Req

A meaningful share of the companies reading this do not have a program. They have one large project and a communication problem.

If your dependency map fits on one page and every team involved reports into the same VP, you want a strong senior project manager for forty thousand dollars less. The program manager premium buys somebody who can hold competing priorities across organizational boundaries and force a decision without any authority to do so. Remove the boundaries and you are paying for a skill your org chart will not let them use. Bored in two quarters. Gone in three. Our project manager staffing agency desk fills that version, and it is a smaller fee for us.

The second one I give away constantly. Look at whoever is already running your largest workstream. In roughly a third of the searches that arrive as external program manager reqs, the client has someone internal who is one mentor and one title change away from doing the job, and the only reason they have not been promoted is that nobody wants to backfill the project manager seat.

That is a scheduling problem being solved with a search. Backfilling a project manager is faster and cheaper, and the person who already knows your systems will outperform an external hire through the first nine months regardless of pedigree. We lose both fees when a client takes that advice. I keep giving it because the alternative lands back on our desk eighteen months later with a worse story attached.

Same req. Lower morale. Higher band.

What These Searches Look Like on Our Desk Right Now

KORE1 has been placing technology talent since 2005, across eight verticals and 30-plus U.S. metros, with recruiters averaging 15-plus years in their specialties. Our 12-month retention rate on placements sits at 92 percent. Program management runs slightly below that number, and I think the reason is instructive. These roles fail on scope clarity more than on skill, and scope clarity is something we can probe for but not fix.

Concretely, here is the current shape of it.

Technical program manager searches run six to nine weeks and the bottleneck is almost never sourcing. It is the interview loop. A good TPM is talking to three companies, and whichever one reaches an offer first usually wins regardless of who had the better role. PMO and portfolio roles fill fastest, generally inside four weeks, and the pool there is genuinely deep. Regulated program work in medical device, pharma, and aerospace is the slowest and the most band-sensitive, because the candidate set is small and every one of them knows precisely what a submission program is worth. Across our IT desks generally we average 17 days to placement. Program management pulls that average up.

Reqs that stall almost never stall on supply. They stall on a band pulled from a national average, or on a job description that asks for a technical program manager and then describes a project coordinator.

Read yours again. Out loud, ideally.

Questions We Get on Every Program Manager Req

What number should actually go in the budget line?

Budget $118,000 to $155,000 base for a mid-level program manager and $150,000 to $195,000 for senior, then add 20 to 30 percent for benefits and payroll burden. Technical program management runs $30,000 to $50,000 above those bands.

Pick the track before you pick the level. A PMO governance req and a platform TPM req at nominally identical seniority sit $50,000 apart. Splitting the difference loses both searches.

Program manager or project manager, which req should I actually be writing?

Count your interdependent projects. Three or more, with different owners and a shared outcome, is a program. One project with phases is a project, and a senior project manager will run it better for less money.

The tell is whether anybody currently holds authority to reprioritize across those projects. A VP doing it in a monthly meeting means you have a program and no manager for it. Projects that never compete for anything are just projects. We wrote a longer breakdown on the product manager and project manager distinction, which trips up as many reqs as this one does. The closer call for most hiring teams is product manager vs program manager, where the titles sit $39,294 apart.

Why does Indeed say $95,750 and Levels.fyi say $240,000?

Because they are describing different labor markets that share a job title. Indeed averages across nonprofit, healthcare, and government program roles. Levels.fyi reports offer letters from large technology companies where equity is most of the package.

Neither is wrong inside its own sample. Both are useless alone. Take three sources that match your track, drop the outliers, then sanity-check the middle against what candidates in your market have recently declined, because a declined offer is the only number in this entire exercise that reflects today’s clearing price rather than last year’s.

Is the PMP worth paying a premium for?

In PMO, regulated, and government-adjacent work, yes, and PMI’s 2025 survey puts the U.S. gap at $135,000 against $109,157. On a technical program management req in a software company, it predicts very little and screening for it costs you candidates.

I would rather see one program somebody owned from kickoff through post-mortem than four certifications. The credential proves they studied a framework. Fine. It does not prove they have told a senior engineer that their estimate was fiction and then kept the working relationship intact afterward, which is the actual job on most days.

How fast can we realistically fill one of these?

Four weeks for PMO and portfolio roles, six to nine weeks for technical program management, and longer for regulated program work in medical device or aerospace. The variable is almost always interview loop speed rather than sourcing.

Past nine weeks, read the job description before you blame the market. Ask somebody who fills these weekly which single requirement is eliminating the most people. There is nearly always one line doing most of the damage. Usually a years-of-experience number attached to a tool that has only existed for three.

Can I promote a senior project manager into the role instead?

Often, and it is usually the better trade. Project managers who already influence across teams without authority convert well, because the hard part of program management is political rather than technical.

Budget six to nine months of rough ramp. Give them explicit air cover from an executive, in writing, in front of the other teams. The conversion fails when the promotion gets announced and nothing else changes, at which point the person holds a new title and precisely the authority they had before.

Which is none.

Do I need a technical program manager or will a regular one do?

A TPM earns the premium when the dependencies are technical and the tradeoffs require reading design documents. If the program coordinates people and calendars around engineering work rather than inside it, a strong program manager does the job for $40,000 less.

Test it with one question. Will this person have to independently judge whether an engineering team’s proposed approach creates a dependency for another team? Yes means TPM. No means somebody sold you a title. Our technical program manager interview questions go deeper on separating the two inside a loop.

What should we expect to pay for an interim program manager?

$65 to $95 an hour W-2 for business and operations programs, $85 to $135 for technical program management, and $110 to $175 for ERP or post-merger integration work. Interim PMO leadership runs $125 to $200.

Contract rates on integration and ERP work moved up through the first half of 2026 and have not come back down. Anybody quoting you 2024 rates for a post-merger program is either out of date or about to send you somebody who has never run one.

Usually the second.

Pricing the Req Without Guessing

Pick the track first. Technical, business operations, PMO, or client delivery, because those are four separate markets and every table above only means something once you have chosen one of them. Level second. Metro and remote posture third, and they matter less than your instincts suggest.

Then quit averaging tracker pages. That one habit is worth more than everything else here combined.

Two resources worth ten minutes when you get to the number. Our salary benchmark assistant returns a live band for a specific level and market, and the methodology we use to benchmark tech leadership roles explains how we weight conflicting sources, which on this title is a daily exercise. If you are already past budgeting and into the search, our project and program management staffing desk covers all four tracks.

Or bring us the req and let us tell you what is wrong with it. Reach out to our team and you will know inside one conversation whether your band clears the market. Some of those calls end with us saying the hire you described is not the hire you need. We make them anyway.