Author: MTF Institute Research Team
Independent review: MTF Institute Research QA
Evidence date: 10 October 2026 · United States
Technical report: MTF-CF-RR-2026-10-10-NSABM
Executive summary
This study examines 111 distinct, employer-authored United States vacancies at 17 private-sector commercial-space and space-service employers, captured and coded on 10 October 2026. The positions span supply chains, program delivery, commercial growth, contracts and capture, mission operations, product work, customer delivery, and business operations. The sample was deliberately assembled to cover those kinds of work. It is a purposive, point-in-time sample, not a census or a representative measure of all U.S. space-sector hiring. Its value is a source-traceable map of what these particular employers described in their open roles.
Three findings shape the role picture. First, management work frequently crosses engineering and commercial boundaries: 107/111 postings explicitly describe cross-functional coordination, including 67/70 outside SpaceX and 76/79 after limiting each employer to ten postings. Second, risk, quality or change control appears in 72/111, 46/70 and 50/79 respectively, while program/project control appears in 47/111, 30/70 and 36/79. These are coded mentions in vacancy text, not sector-wide rates. Third, the job families differ substantially. A procurement manager, a launch-site operations manager, a government-contracts manager and a satellite product manager face different decision rights and specialist boundaries. An integrated description of “the space business manager” would conceal that variation.
The descriptions also understate some operational details. Only 54/111 name a tool or system, 58/111 state a work cadence, and 25/111 specify an escalation route. An omission means not stated, rather than “not required.” Commercial-space professionals should therefore ask about the actual decision authority, review rhythm, customer and supplier interfaces, and handoff to engineering, safety, regulatory, export-control or legal specialists when evaluating a role.
Research question and design
We asked: what work, outputs, methods, tools, behaviors, qualifications and decision boundaries are explicitly described in current U.S. management-oriented vacancies in private and commercial space? The geographic study population was declared as United States before coding. No vacancy from another country is included. A U.S.-located commercial employer serving a government customer remains in scope; that customer relationship does not make the job a government position.
The unit is one employer-authored requisition with a U.S. work location or U.S.-remote eligibility and substantive responsibility for managing or coordinating a space-related product, service, mission, program, customer, contract, operation or supply chain. A technical job enters only where its stated work includes material management or coordination. Purely technical individual contributors, generic non-space corporate work, internships without such duties, expired posts, anonymous aggregator copies and unverifiable descriptions were excluded. Requisition IDs, employer, title, location and substantive description were compared to avoid duplicate counts. Three Rocket Lab multi-city pairs were conservatively treated as one opportunity per pair; a location-conflicted ispace opening was held out. The Rocket Lab Senior Contracts Manager II posting illustrates why identical descriptions across cities must not automatically become separate seats.
Employer boards and linked application pages were checked for the title, U.S. location and an Apply control. Public captures preserve source URLs, retrieval evidence and minimal supporting excerpts privately. The 111-row coded matrix matches the 111-row study roster by URL, with no duplicate coded URL. An independent second-coder calibration and source adjudication covered 20 examples across employers and role families before the complete coding pass. Each positive code has a short source excerpt; absent detail is marked not stated. The counts describe the postings observed in the 10 October 2026 snapshot; openings may change after capture.
The sample includes 41 SpaceX postings, 11 CesiumAstro, seven each from Firefly Aerospace, Planet, Rocket Lab and E-Space, six Vast, five Impulse Space, four Astranis, three each from Viasat, Terran Orbital, Varda Space Industries and Spire, and one each from GITAI, Stoke Space, Epsilon3 and ispace U.S. SpaceX supplies 41/111 rows, making sensitivity analysis essential. We show: raw (all 111); non-SpaceX (70); and an employer cap of ten (79). The cap uses a reproducible family-stratified draw with seed newspace-us-2026-employer-cap-v1 and retained URLs recorded with the matrix summary. These are alternative descriptions of this sample, not probability-weighted estimates of U.S. hiring. A posting may contain several codes, so code rows do not add to the sample total.
Role families: related work, distinct jobs
| Primary stated work | Raw postings | Non-SpaceX | Employer cap | Illustrative employer source |
|---|---|---|---|---|
| Supply-chain planning | 25 | 10 | 10 | Astranis supply-chain manager |
| Program and production delivery | 23 | 19 | 20 | Viasat space program manager |
| Commercial growth | 19 | 10 | 12 | Planet account executive |
| Mission operations | 9 | 8 | 9 | Firefly mission manager |
| Contracts and capture | 9 | 9 | 9 | Astranis government contracts manager |
| Customer service delivery | 7 | 1 | 2 | Spire federal account manager |
| Business operations | 7 | 4 | 6 | Planet deal desk manager |
| Product management | 5 | 4 | 5 | Viasat device platform product manager |
| Other in-scope management | 7 | 5 | 6 | Firefly spacecraft quality manager |
These mutually exclusive primary families follow the dominant described responsibility; a posting can also have a carefully evidenced secondary workstream. Family counts show the composition of the chosen sample, not the national mix of opportunities. The raw sample overrepresents SpaceX supply-chain and customer-delivery postings: supply-chain planning drops from 25/111 to 10/70 without SpaceX, while contracts/capture remains 9 in both views. The capped view also retains 9 contracts/capture and 9 mission-operations records. The sample therefore supports a broad cross-functional study, but not a single generic occupational profile.
Several boundary cases matter. Stoke Space’s launch-vehicle role has substantial technical engineering content but was retained because its description includes team leadership and workstream ownership. It should not make technical design expertise a universal business-management prerequisite. GITAI’s mission program role is an example where program ownership can coexist with an explicit individual-contributor arrangement. A “manager” title alone does not prove direct reports.
Within the primary-family subsets, program and production delivery (23 postings) includes 22 with program/project control and 21 with quality/risk/change work; Viasat's program manager illustrates this combination. Supply-chain planning (25) includes 20 with materials/inventory/logistics work and 16 with supplier sourcing or management; Astranis's supply-chain manager is one example. Commercial growth (19) includes 17 with pipeline/sales and 14 with market development; Planet's account executive illustrates the customer-facing side. Mission operations (nine) contains nine mission/launch coordination descriptions and eight requirements/interface descriptions, as illustrated by Firefly's mission manager. These are within-sample descriptions, not comparisons of U.S. employer demand. Cells of nine, and especially the five product-management or seven customer-delivery roles, warrant caution.
Duties, methods and named work products
The coding distinguishes current duties from required or preferred candidate criteria. The table counts explicitly described current work. None of these duty totals relies solely on preferred experience.
| Coded current-duty theme | Raw sample | Non-SpaceX | Employer cap |
|---|---|---|---|
| Quality, risk and change control | 72/111 | 46/70 | 50/79 |
| Finance or operations analytics | 50/111 | 23/70 | 29/79 |
| Program or project control | 47/111 | 30/70 | 36/79 |
| People or team leadership | 39/111 | 23/70 | 27/79 |
| Contract and commercial management | 37/111 | 20/70 | 22/79 |
| Requirements and interfaces | 30/111 | 22/70 | 25/79 |
| Materials, inventory and logistics | 28/111 | 10/70 | 10/79 |
| Capture, bid and proposal | 24/111 | 23/70 | 24/79 |
The changing rank of analytics and materials work after removing SpaceX shows why a raw total alone can mislead. These are overlapping labels, not mutually exclusive occupations. Specific descriptions show the substance behind the labels: Viasat’s program role connects delivery, reporting and customer work; Rocket Lab’s proposal role centers on bid coordination; Astranis’s payload supply-chain role centers on supplier and material decisions; and Planet’s deal desk role connects commercial process with deal evaluation. These illustrations should be read as examples, not proof that every post in a family is identical.
All 111 descriptions support some coded duty and method. Process improvement appears in 55/111, 31/70 and 35/79; risk/issue/change management in 42/111, 34/70 and 34/79; data analysis/forecasting in 41/111, 17/70 and 23/79. These method codes identify stated work or criteria rather than audited competence. Exactly 95/111 postings name at least one identifiable output; 16 do not. Common named products are a program plan or schedule (27/111; 21/70; 23/79), proposal or bid (22/111; 20/70; 21/79), contract record (14/111; 6/70; 7/79), and quality/compliance record (13/111; 11/70; 13/79). A role may produce several. Output absence in a job advert is not evidence that the job has no deliverables.
Work combinations in the same postings
A single advertisement can describe more than one kind of work. Quality/risk/change control and a program/project-management method occur together in 24/111 postings, including 16/70 outside SpaceX. Contract/commercial management and a named proposal or bid output appear together in 9/111 and 7/70 respectively. Mission/launch coordination and requirements/interface work appear together in 11/111 and 9/70. The shared denominator is the full eligible sample for each view, and the numerator requires both codes in the same posting. Viasat's space program manager, Rocket Lab's Senior Contracts Manager II and Firefly's mission manager illustrate the three pairs respectively. Co-mentions do not show that one practice causes another or that these combinations occur at the same rate in the U.S. vacancy population.
Supplier sourcing and a named supplier-sourcing plan occur together in 11/111, but 0/70 outside SpaceX; a SpaceX supply-chain posting illustrates the paired coding. That contrast illustrates employer concentration in this selected sample; it is not evidence that other employers never use such plans.
Interfaces, authority and escalation
Cross-functional coordination is explicitly described in 107/111 postings (67/70 without SpaceX; 76/79 capped). The named interface most often coded is internal engineering, 84/111 (58/70; 61/79), followed by executive leadership, 48/111 (29/70; 34/79), finance/legal, 42/111 (22/70; 26/79), internal manufacturing, 36/111 (22/70; 21/79), and suppliers, 34/111 (20/70; 20/79). These codes are posting-level mentions; they do not imply that every worker personally makes engineering or legal decisions. For example, Viasat’s satellite device product role explicitly joins product priorities to RF, modem, antenna, software, test and supplier interfaces. Firefly’s mission-management posting illustrates mission-delivery coordination, a different work setting.
Authority was explicitly codable in 79/111; it was not stated in 32. The descriptions support owning a plan in 44/111 (24/70; 29/79), staff supervision in 27/111 (16/70; 18/79), negotiating terms in 19/111 (10/70; 11/79), and prioritizing work in 18/111 (13/70; 14/79). These are distinct acts. Negotiating is not automatically contract-signing authority, and owning an integrated plan does not give technical, flight or regulatory approval power. Of the 111 roles, 27 explicitly support a people-manager classification, four explicitly say no, and 80 do not state it. Responsibility-based seniority coding yielded 23 director/executive, 41 manager/lead, 35 senior, ten specialist/analyst and two entry/early roles. It reflects described scope, not the title alone.
Escalation language appears in only 25/111 descriptions and is not stated in 86; the corresponding stated counts are 10/70 without SpaceX and 13/79 under the cap. An explicit risk/issue escalation appears in 22/111 (9/70; 12/79), while specialist handoff is clearly coded in three. These small counts mostly measure how rarely adverts specify the route. They cannot establish that other employers lack escalation practices. Astranis’s government contracts posting and E-Space’s contract role show why coordination with legal or compliance colleagues must not be overstated as final legal authority.
Tools, cadence and candidate criteria
Only 54/111 adverts specify at least one concrete tool or system; 57 do not (35/70 and 41/79 do not in the sensitivity views). Spreadsheets are named in 23/111, data querying or programming in 21/111, ERP/MRP in 19/111, project scheduling tools in 13/111, business intelligence in 13/111 and CRM in 11/111. Tool codes may arise from duties, required skills or preferred experience. Under a stricter duty or required filter, spreadsheets and ERP/MRP each appear in 15/111, project scheduling in nine, and CRM in four. A preferred CRM criterion is not evidence of daily CRM use. Spire’s account role, Astranis’s production scheduler and Planet’s product role illustrate how system needs vary with the workstream.
Work cadence is stated in 58/111 and omitted in 53 (stated in 37/70 and 42/79). Daily appears in 19/111, weekly in 12/111, project lifecycle in 14/111, and mission lifecycle in 11/111. A role may have several rhythms. Terran Orbital’s production role is an example of explicit short-cycle shop priorities. Firefly’s mission manager shows a mission lifecycle rather than a generic office cadence. Neither pattern should be assigned to a vacancy that omits it.
Qualifications were coded separately from current job duties and from each other. A required years-of-experience criterion appears in 87/111, required degree in 64/111, required technical experience in 47/111, and required management experience in 33/111. The advertisements use different domains, thresholds and equivalent-experience alternatives; no common experience minimum or degree field is justified. Industry experience appears as required in 39/111 and preferred in 35/111, with overlap possible when different domains have different criteria. Certification is preferred in 18/111 and required in one. These are employer statements in this sample, not a common occupational requirement.
Work authorization and security conditions are job-specific. A required citizenship/work-authorization code appears in 62/111; 33/111 contain an either_or alternative that must be read exactly as written. Required clearance appears in 22/111 and preferred clearance in 13/111. Some conditions involve an eligible U.S.-person route or a government export authorization; they cannot be restated as universal U.S. citizenship requirements. On-site location and travel criteria likewise depend on the employer and role. Before acting on any eligibility condition, an applicant should consult the exact current posting and the employer’s recruiting team.
Practical interpretation and specialist boundaries
Taken together, the vacancies describe a role landscape in which a manager or coordinator often needs to turn incomplete technical, customer and supplier information into a bounded plan, decision brief, handoff or controlled execution record. A professional entering the field can use that insight to ask five concrete questions about a prospective role: Which product or mission outcome is owned? Which named artifacts must be kept current? Which teams and external parties are involved? What decisions may the role make independently? Which risks require specialist review or escalation? These questions are derived from the coded work and missingness above, rather than from a claim that every employer follows one operating model.
The high-risk workstreams need sharper boundaries. Launch and reentry licensing, spectrum and satellite communications, remote-sensing permissions, export classification, flight and human-safety decisions, and contract interpretation belong to their relevant specialists and public authorities. Vacancy language about “managing” a mission or contract does not transfer their legal or engineering authority to a generalist. The official U.S. source families are FAA Commercial Space, the FCC Space Bureau, NOAA’s commercial remote-sensing licensing office and BIS space export-control materials. Each addresses a different regulatory question. This report maps management interfaces; it makes no authorization, safety, legal or export classification determination.
Limitations and reproducibility
This is a purposive sample assembled from discoverable public employer postings on one date. It is not exhaustive; openings can be unindexed, private, duplicated across locations, revised or closed. SpaceX accounts for 41/111, and the family mix reflects deliberate sampling as well as employer availability. The non-SpaceX and employer-cap views test whether a descriptive result depends heavily on that composition; they do not correct it into a representative estimate. Small families, especially product management (five) and customer delivery without SpaceX (one), should not be compared as if their apparent differences are stable population patterns. Multi-label codes overlap, and a written advert may omit real work, authority or tools. The not stated category is unknown information, never zero prevalence.
The private reproducibility package binds each coded row to an employer URL, requisition identity, location, retrieval evidence, content hashes and short section-labelled excerpts. It records inclusion and exclusion decisions, conservative multi-location deduplication, a versioned codebook, independent-coder calibration and adjudication, and raw/non-SpaceX/capped count tables. The report paraphrases employer expression and links to the source posting rather than reproducing job descriptions. Readers should treat linked listings as volatile historical study sources after that date.
This vacancy corpus is distinct from the separately sourced analysis of recent sector changes. It makes no estimate of future hiring or the size of the NewSpace economy.
Appendix: source register for the 111-posting matrix
These employer pages are the posting-level sources behind the coded counts. Titles and pages may change after capture.