What PM job postings at US tech employers ask for (November 2026)

Last updated:

About this sample. 329 US project, program and product manager job postings from 102 mostly tech employers, collected on November 7, 2026 from public job boards on Greenhouse, Lever and Ashby. This is not a sample of the whole job market: banks, government contractors, large retailers and traditional manufacturers are mostly missing.

The short version

  • In this sample, pay ranges are the norm: 84% of postings show one. The median posted range is $165K to $235K.
  • Years of experience are stated in most postings and rarely softened. 83% of postings state a minimum (median 5 years), and staff and principal titles usually ask for 8.
  • Certifications barely appear. PMP is mentioned in 6% of postings and required in 1 of 329. AI, by contrast, comes up three or more times in 58% of postings.
FindingShare of postingsPostings95% interval
Salary range posted84%276 of 329[80%-87%]
Minimum years stated83%273 of 329[79%-87%]
AI mentioned at least once82%269 of 329[77%-86%]
AI mentioned three or more times58%191 of 329[53%-63%]
Degree mentioned37%122 of 329[32%-42%]
Remote34%113 of 329[29%-40%]
Agile or Scrum named11%35 of 329[8%-14%]
Jira or Confluence named11%36 of 329[8%-15%]
PMP mentioned6%21 of 329[4%-10%]

1. Most postings show pay, and the range is wide

84% of postings (276 of 329) include a salary range [80%-87%]. Across those 276, the median low end is $165K, the median high end is $235K, and the median midpoint is $205K. The high end sits a median 38% above the low end.

Role familyPostings with a rangeMedian lowMedian highMedian midpoint
Product managern=131$185K$255K$220K
Technical program managern=56$180K$250K$215K
Program managern=56$140K$195K$170K
Project manager (small group)n=16$120K$180K$155K
Level in the titlePostings with a rangeMedian midpoint
No level statedn=116$180K
Seniorn=74$195K
Staffn=35$235K
Principaln=18$245K

To see the posted range for one role family at one level, with the groups too small to read marked as such, use the salary ranges by role and level tool.

Years, posted pay and the remote share for senior, staff and principal titles side by side, with the program and TPM cells: Senior vs staff vs principal: what PM postings ask

2. Years of experience are stated, and rarely softened

83% of postings (273 of 329) give a minimum number of years [79%-87%]. The median is 5 years, with the middle half between 4 and 8 (n=273). Only 7% of those (20 of 273) soften the number with "preferred" or "nice to have".

The title level moves the bar more than the role family does. Technical program manager postings run higher than the other families, at a median of 7 years (n=47).

Level in the titlePostings with a numberMedian minimum yearsAsk for 8 or more years
Seniorn=70521% (15 of 70)
Staffn=31865% (20 of 31)
Principaln=20870% (14 of 20)

The same figures by role family, with senior project and program titles side by side: How many years of experience PM jobs ask for.

What technical program manager postings ask for next to program manager postings, from pay and years to AI, degrees and clearance: TPM job requirements: what postings ask

3. PMP is rare in these postings, and almost never required

Any certification at all appears in 7% of postings (22 of 329) [4%-10%]. PMP is mentioned in 6% (21 of 329) [4%-10%] and marked as required in 1 of 329. Scrum credentials (CSM, PSM, CSPO, SAFe, PMI-ACP) together appear in 2% (5 of 329).

Role familyPMP mentioned95% interval
Project manager38% (9 of 24)[21%-57%]
Program, technical program and project combined13% (20 of 152)[9%-19%]
Product manager0% (0 of 158)[0%-2%]

The project manager group is small, so treat its figure as a direction, not a precise number.

What these figures mean if you are weighing a credential: Is PMP worth it? and Do PM jobs require an Agile certification like CSM?

4. AI is mentioned in most postings

82% of postings (269 of 329) mention AI, machine learning, LLMs or generative AI at least once [77%-86%]. That count includes company descriptions, so we also used a stricter cut: three or more mentions. 58% of postings (191 of 329) clear it [53%-63%].

Role familyThree or more AI mentions
Technical program manager64% (37 of 58)
Product manager61% (96 of 158)
Program manager50% (35 of 70)
Project manager46% (11 of 24)

Only 9% of job titles (29 of 329) name AI, ML or agents. In this sample, AI is context for most roles rather than a separate title.

AI mentions by role family and level, and what they ask you to show: Do PM jobs require AI skills?

5. Degrees are mentioned in about a third of postings

37% of postings (122 of 329) mention a degree [32%-42%]. When a level is named it is almost always a bachelor's (88 of the 96 mentions that name a level); the other 26 mentions say "degree" without a level. In 34% of degree mentions (41 of 122) the posting adds "preferred", "or equivalent" or similar wording.

The education line by role family and level, and what to do without a degree: Do project managers need a degree?

6. Methodologies and tools are seldom named

Agile or Scrum appears in 11% of postings (35 of 329) [8%-14%]. Jira or Confluence appears in 11% (36 of 329) [8%-15%], rising to 19% (29 of 152) in program, technical program and project postings, and to 33% for Jira in project manager postings (8 of 24). SQL appears in 10% overall (34 of 329) and 13% of product postings (20 of 158). Only 31% of postings (103 of 329) name any of the 15 tools we tracked. Postings rarely name tools or certifications.

Every tool we counted, by role family, with the caveats of each name: Tools in PM job postings: Jira, Confluence, SQL and more

7. About a third of roles are remote, more at senior levels

34% of postings (113 of 329) are marked remote [29%-40%].

Level in the titleRemote
No level stated28% (40 of 144)
Senior41% (34 of 83)
Staff47% (17 of 36)
Principal52% (13 of 25)

The intervals overlap, so read this as a pattern worth watching rather than a settled result.

How the remote flag was set, the shares by role family, and travel and clearance lines: Are project manager jobs remote?

How to use this for your resume

  1. Make your years easy to count. Most postings state a minimum, and few mark it as preferred. Show dates and scope for each role so a recruiter can add up the relevant years in seconds.
  2. Match the level, not only the title. Staff and principal postings mostly ask for 8 or more years. If you are applying a level up, your resume has to show the scope that level implies: budget, team size, number of teams, executive audience.
  3. Show AI work as results. If you have used AI tools or shipped AI features, write what you did, at what scale and what changed. Keywords alone do not.
  4. List certifications, do not lean on them. Keep PMP if you hold it; it shows up more often for project manager roles. In this sample it is rarely named in product and technical program postings.
  5. Mirror tools only when the posting names them. Most postings do not. When one does, use the same words in your skills and in a bullet that shows the tool in use.
  6. Read the pay range against the level. Ranges are wide. Use the level in the title and the years asked to judge where you are likely to land within it.

Method

  • Sources. Public job boards that employers publish on Greenhouse, Lever and Ashby, read through their public job feeds. Greenhouse 215 postings, Ashby 79, Lever 35. LinkedIn, Indeed and Glassdoor were not used.
  • Date. Collected November 7, 2026. Postings change weekly; 67% of the postings in the sample (219 of 329) had been updated in the 30 days before collection.
  • Scope. 329 US postings from 102 companies, at most 4 per company, with project, program, technical program, product, delivery or implementation manager, product owner, PMO or business analyst in the title. Industries: software and AI, fintech and insurance, health and biotech, logistics, transportation and hardware, consumer companies.
  • Families and levels come from the job title.
  • Extraction. Features (years, salary, certifications, degree, methods, tools, AI mentions, remote) were extracted by fixed text rules. Full posting text was not stored. We checked 14 records by hand against the original posting text. That check was done before we added a fallback pattern for years of experience, and it was not repeated after the change.
  • Statistics. Shares use all postings in a group as the denominator. Brackets show 95% Wilson confidence intervals. Salaries are medians of posted annual ranges, rounded to the nearest $5K. Groups with fewer than 10 postings are not used for conclusions.

Limitations

  • Tech-heavy sample. Employers that publish open feeds on these three platforms are mostly technology companies. Banks, government contractors, large retailers and traditional manufacturers mostly use other hiring systems and are not in the sample. Read the results as "US tech employers", not "the whole market".
  • Role mix. Product roles are 48% of the sample (158 of 329); project manager postings are only 24. No scrum master or IT manager postings were found.
  • Rule-based extraction. Text rules miss some phrasing. Our estimate of the error rate for minimum years is about 10-15%, from the 14-record manual check (2 errors), which was not repeated after the years rule was changed. Salary and certification errors were lower in that check, but the sample is small and few of those records named a certification. "Required" often means "not marked preferred".
  • Salaries. Ranges are what employers publish under pay transparency laws. They are not offers and exclude equity and bonus.

Check your resume against a posting

Want to see how your resume reads against a specific posting? The free match points out gaps between the two. It cannot promise interviews or offers.

Download the aggregate tables

Each file is one table of shares, medians and counts, in the form share (k/n) [95% interval]. In the years tables "required" means "not marked preferred". LOW_N marks groups of fewer than 10 postings. The files hold no posting text, no job titles and no employer names.

Source: PM Career Desk analysis of 329 public job postings, November 2026.