Research question

How often did 100 current management vacancies from large US employers explicitly signal project or programme work, which delivery capabilities appeared, and what evidence should candidates build?

This MTF Research Report is a dated labour-market snapshot. It does not estimate all US management employment, compare employer quality or rank project-management credentials.

Executive finding

In a frozen sample of 100 distinct US management vacancies from eight 2026 Fortune 100 employers, 25 postings were coded positive for project or programme work. Among the full sample, 24 signalled ownership or delivery activity, 24 cross-functional delivery, 21 scope or planning, 20 risk/governance/quality, 19 formal project/programme-management evidence, 15 resource/budget/commercial work and 12 schedules, milestones or dependencies.

These categories overlap: one vacancy can contain several capability signals. The practical conclusion is not that every manager needs the title “Project Manager.” It is that candidates can strengthen their evidence by showing how they converted an outcome into a controlled cross-functional delivery system.

Scope and sampling frame

The analysis reuses the frozen 100-vacancy corpus captured on 10 August 2026 for the MTF management-skills research series. It contains public vacancy pages from Amazon, Apple, Alphabet (Google), UnitedHealth Group, McKesson, Microsoft, JPMorgan Chase and CVS Health. The employers were selected from the 2026 Fortune 100 and supplied accessible current US management vacancy pages across multiple functions.

Every observation is one distinct vacancy page. The design is purposive and employer-uneven; it maximizes functional variety inside the accessible frame but is not a probability sample of all Fortune 100 vacancies.

Inclusion and coding method

The primary inclusion code was the manually reviewed program_project_management field in the frozen 100-row dataset. A posting was positive when its title, responsibilities or qualifications assigned or required identifiable project, programme, portfolio, implementation, roadmap or structured delivery work.

Benefits wording, search-page navigation and unrelated uses of “programme” were not treated as evidence. For positive observations, the full captured page was coded into seven non-exclusive capability classes:

Code Operational definition Positive postings
Ownership and delivery Lead, own, manage, drive, oversee or deliver a project, programme, portfolio, roadmap or implementation 24
Cross-functional delivery Coordinate stakeholders, partners or multidisciplinary teams to deliver 24
Scope and planning Scope, requirements, charter, roadmap or implementation-plan work 21
Risk, governance and quality Risk, controls, governance, assurance, compliance, quality or change-control activity 20
Formal PM evidence Explicit project/programme/portfolio management, Agile delivery, Scrum, PMP or related experience 19
Resources, budget and commercial Budget, cost, capacity, procurement, vendor, commercial or contract responsibility 15
Schedule, milestones and dependencies Timeline, milestone, schedule, deadline, dependency or release/launch-plan work 12
Any project/programme work At least one context-confirmed inclusion signal 25

Counts are document frequencies, not estimates of time spent or capability importance.

Results by employer

Employer Positive postings
Microsoft 11
Apple 7
Amazon 2
JPMorgan Chase 2
Alphabet (Google) 1
McKesson 1
UnitedHealth Group 1
CVS Health 0

These counts must not be read as employer rankings. The number and functional mix of sampled vacancies differ by employer; Microsoft and Apple supplied many programme, product, engineering and construction roles.

Results across work contexts

The 25 positive postings were distributed across five practical contexts:

Context Positive postings
Technology, data and product 10
Construction, facilities and infrastructure 4
Corporate, transaction and governance 4
Retail, marketing and customer 4
Healthcare and laboratory operations 3

The context classification uses title and employer information to avoid treating every mention of digital tools as a technology role. It is descriptive and single-label; a job may operate across more than one domain.

What the capability pattern means

Ownership and cross-functional delivery each appeared in 24 of the 25 positive postings. This pairing matters. Employers were rarely signalling isolated schedule administration. They were assigning managers to move work across organizational boundaries while remaining accountable for an outcome.

Planning appeared in 21 positives and risk/governance/quality in 20. Together, these signals describe controlled delivery: define the work, coordinate it, test the forecast, govern exceptions and preserve acceptance evidence.

Schedule and dependency language appeared in 12 positives—less often than general ownership or stakeholder work. This does not make scheduling unimportant. It shows that vacancy language often describes the broader mandate while leaving the detailed control system implicit.

A practical candidate framework: PROJECT-5

Candidates can translate the findings into five privacy-safe portfolio records:

PROJECT-5 record What to show Evidence question
1. Outcome and boundary brief Intended value, scope, exclusions, acceptance and authority What was the project meant to change, and what was outside scope?
2. Integrated delivery map Milestones, dependencies, owners, resources and decision points Which handoffs controlled the forecast?
3. Stakeholder and decision system Stakeholder evidence, communication cadence and decision rights Who needed to act, advise, approve or be informed?
4. Risk/change decision record Trigger, evidence, options, trade-off, authority and revised forecast How did new evidence change the plan?
5. Outcome and learning review Delivered result, benefit measure, exceptions and lessons What was achieved, what remained uncertain and what changed next?

Remove employer-confidential information. Use synthetic values where necessary, but preserve the logic and clearly label simulation.

Worked PROJECT-5 example

Suppose a manager led an onboarding redesign. A weak résumé bullet says: “Managed a cross-functional project.”

A stronger evidence chain states that the manager defined a 30% cycle-time objective, documented exclusions, coordinated product, operations, risk and vendor owners, tracked three critical dependencies, escalated a privacy-acceptance delay, proposed a phased release and measured the first 30 days against the baseline.

The portfolio does not need to reveal customer data or internal financials. It should show the outcome, the control logic, the evidence that changed a decision and the result.

How students can apply the result

  1. Select one completed or simulated project.
  2. Build the five PROJECT-5 records in a consistent case.
  3. Add baseline, forecast and actual values where authorized.
  4. Label assumptions, evidence gaps and decision authority.
  5. Ask a peer or manager to challenge one trade-off.
  6. Convert the evidence into two résumé bullets and one interview story.

The research suggests prioritizing cross-functional ownership and controlled delivery before collecting more tool names. Candidates should still match each target vacancy: a construction role may require cost, safety and contractor evidence, while a technical programme role may emphasize dependencies, platform risk and release governance.

Limitations

  • The sample is purposive, not random, and includes only eight Fortune 100 employers.
  • Employer representation is uneven and the vacancies were captured on one date.
  • Public vacancy pages can change or disappear after capture.
  • The study measures explicit text, not actual time allocation or unadvertised expectations.
  • The primary project/programme code was inherited from the frozen management-skills dataset; the seven secondary codes use transparent keyword rules on captured full text.
  • Category counts overlap and should not be summed.
  • The research identifies hiring signals, not causal effects on recruitment outcomes or job performance.

Reproducibility and integrity

The accompanying workbook contains all 100 sample IDs, employers, titles, source URLs, capture dates, inclusion codes, secondary capability codes, context labels and evidence excerpts for positive observations. The archived PDF and supporting data preserve the dated result. No personal applicant data was collected.

Learning next step

MTF Institute's Professional Certificate in Project Management provides a published 20-day applied curriculum across initiation, scope, schedule, budget, stakeholders, Agile delivery, risk, quality, change, procurement, metrics and portfolio work. Students can use the programme exercises to build a PROJECT-5 evidence portfolio while preserving human accountability and confidential-data boundaries.

DOI and archival materials

Sources

Author and review

Author: MTF Institute Editorial Team
Verified reviewer: Igor Dmitriev
Publication date: 4 September 2026
Report number: MTF-RR-2026-09-04-01