From Report to Pipeline

Why this document exists

SWIFT did not publish The Space Economy Jobs Report to publish a report. The stated purpose is a working talent pipeline for employers. This document takes the report as the first input to that pipeline and asks what has to happen next for it to produce one.

The operating model

Building a talent pipeline for employers requires five steps in order. Each step consumes the previous step's output.

The chain has one structural property worth stating plainly: it is subtraction. Step 3 subtracts step 2 from step 1. Subtraction requires both operands to be expressed in the same units. That single requirement is where the chain currently breaks.

Where the chain breaks

Break 1 — Step 1 is not complete

The report delivers occupations and credentials, not skills. "Welder," "technician," "AWS D17.1" are labels for bundles of skills, not skills themselves. A pipeline cannot be planned from a list of job titles, because a job title cannot be trained, measured, or subtracted.

This is not an oversight in the report. It is the state of the entire field — no one deconstructs postings into skills, because the tooling to do it at scale did not exist. It is the demand half of what PowerTechs does; the other half is in §6.

Break 2 — Steps 1 and 2 are denominated in different units

Demand, as the report captures it, is expressed in certifications and standards. Supply — the way any workforce agency, college, or employer describes a talent pool — is expressed in degrees, credentials, and years of experience.

This is why no one in the sector has a number for the gap, only a qualitative sense that one exists. Step 3 is currently unexecutable, which means steps 4 and 5 end up running on judgment.

Break 3 — Step 5 assumes every gap is trainable by the institutions on hand

SWIFT's inventory of pipeline instruments is community colleges, technical schools, and regional training centers. That inventory closes gaps that a curriculum can close. It does not close the others — and the report does not distinguish between the two.

This is the most expensive break, because it explains the report's own central paradox.

The welding paradox is a diagnosis, not an anomaly

The report establishes that the shortage is not of people who can weld, but of welders who meet exacting standards. Follow it to the end:

1. If the binding constraint were technical, certification would relieve it. Train more, certify more, fill the roles.
2. Texas colleges teach welding. Certified welders exist. The report confirms ample national supply.
3. The roles remain open.

This matters directly and immediately for SWIFT's mission: the strategy as written — align colleges to industry certifications — executed perfectly, produces more certified welders and the same open roles. On the report's own largest single gap (11.9% of postings), the strategy would miss the constraint — not through any error in it, but because the constraint sits in a layer nobody has been able to see.

We think we can show exactly where the constraint hides. Below is one real posting from a Texas employer.

Worked example: Firefly Aerospace, Flight TIG Welder II, Briggs TX

We deconstructed one real posted role from a company inside SWIFT's own network. Retrieved from Firefly's public listing; postings churn, and this requisition may since have closed.

The posting contains 31 discrete requirement lines: 12 responsibilities, 9 required qualifications, 10 desired qualifications.

The closest is a schedule-flexibility line — an availability condition, not a capability — listed last under Desired.

What the posting says the job is

The summary states that the welders work closely with Fluid Systems Engineers to ensure the build is executed to instruction. That is the job, in Firefly's own framing.

The screen does not screen for the thing the summary says the work is.

The second layer, hiding inside layer-1 language

Every line below is a real requirement from the posting. The left column is what Firefly wrote. The right column is what it actually demands of a person — inferred from the described work, not yet measured against it.

What this proves

Firefly describes the job accurately in prose, then screens on 31 technical items, none of which touch the layer that determines whether the hire holds up. This is not a Firefly failure — it is what every employer does, because no instrument exists for the other layer.

Why SWIFT should care more than Firefly does

A Texas community college building a welding curriculum from this posting will build to all 31 items. It will teach AWS D17.1, GTAW, borescope inspection, precision measurement, tube fabrication, cleaning to aerospace standards. Every one of them correctly.

This is Break 3, made concrete: one document, one Texas employer.

Hypothesis worth testing on the full dataset

We noticed something in a second Firefly posting we do not have enough data to claim. In the Welding Engineer III listing — a degreed role — the durable layer is described: self-direction, internalizing intent, filling gaps, driving improvement to completion without supervision, working with stakeholders. Written in prose, unnamed as skills, unscreenable — but present.

In the welder posting, that language is absent entirely.

If that pattern holds across the 5,000 postings, it means the non-degree track — half of the report's demand — receives the least articulation of the layer that determines its success. That would be a significant finding for SWIFT, and it is testable on data you already hold.

The routing rule

This is the practical output. Once a gap is deconstructed into layers, it routes:

GAP IDENTIFIED
    │
    ├── LAYER 1 — technical / procedural
    │      Closed by: curriculum + practice + certification
    │      Instrument: community colleges, technical schools, apprenticeships
    │      SWIFT has this. It works.
    │
    └── LAYER 2 — durable
           Closed by: repeated exposure under realistic conditions, with feedback
           Instrument: simulation, or years on the floor, or prior formation
           SWIFT has none. Neither does anyone else.

Durable skills are trainable. This is the correction we would offer to the common framing. They are not innate, and they are not soft. The military trains them continuously and deliberately. They are simply not trainable by the instruments currently in SWIFT's inventory, because they do not transfer through a course. They accumulate through repetition under pressure with correction.

Without this rule, a pipeline plan routes durable gaps into colleges, where they will not close, and the resulting time-to-close estimate is wrong by an order of magnitude — in the optimistic direction. That kind of error is hard to catch, because nothing about the plan looks wrong from the outside.

Step 4: time-to-close, and where it compresses

Time-to-close is the step nobody can currently answer, and it is the step that determines whether a pipeline plan is a schedule or a wish.

Our estimates come from practitioner expertise, not from published data — no validated dataset on durable-skill time-to-close exists in this sector, ours included. We offer the framework as the contribution and treat the numbers as what measurement calibrates. We would rather say that plainly than present estimates as measurements.

What we can state structurally:

This is the other half of what PowerTechs does, and the two are one system in that order: the deconstruction in §2 names the layer in the work, and the simulation scores that same layer in a person. Nothing can measure a technician's composure under pressure until something has established that Firefly is paying for it. It is also why the timeline compresses. Absent an instrument, layer 2 accumulates at the speed of the job — years on the floor, if the employer is patient enough to carry someone that long, which the report shows they are not. A simulation delivers the same mechanism at a controlled rate, and produces a measurement as a byproduct.

Step 2: the talent pool not counted

The report inventories Texas's educational institutions. It does not mention veterans, the military, or transitioning service members — which follows naturally, since the military is not an educational institution and does not appear in any workforce inventory we know of.

We would submit that Texas's largest source of layer-1-and-layer-2-complete technical talent is not in the inventory. The correspondence below is structural — mapping occupational specialties to the report's role taxonomy is a workstream, not yet a claim. Look again at the Firefly posting through this lens:

This is the point we would most want SWIFT to take. The military is not a source of raw candidates needing durable-skills training. It is the one institution in the country that trains durable skills deliberately, at scale, and by design. A transitioning aircraft structural maintainer has spent years doing precisely what the Firefly posting's unnamed layer requires.

The certificate is the easy half — months, not years, and SWIFT's colleges are already excellent at it. But nobody routes a Sheppard technician toward one, because nothing on Firefly's screen tells them apart from any other applicant without a cert. They land in the quadrant the screen cannot see: layer 2 complete, layer 1 uncredentialed. The 31 lines read them as unqualified, while the layer that makes them worth the months is invisible.

This is a rare shape for a workforce problem, and it divides the labor cleanly. The expensive half is already built, at federal expense, arriving continuously. The cheap half is precisely what SWIFT's colleges do. The only missing piece is the instrument that tells you which of the two you are looking at — the one §5 says nobody has.

And the placement mechanism already exists and costs the employer nothing. Under DoD SkillBridge, a service member in their final 180 days trains full-time with a civilian employer while the Department continues paying salary, allowances, and benefits; industry partners are prohibited from paying wages. PowerTechs is an approved SkillBridge provider.

What the instrument produces at scale

The Firefly deconstruction in §4 took an afternoon. The instrument exists; what follows is not a proposal to build something, but a description of what it returns when pointed at a role family instead of a single posting.

Everything above was built from the published report and public postings — not from SWIFT's underlying 5,000 records or its taxonomy. That is the only reason this section describes a role family rather than showing one.

Scope: welder / precision technician postings across SWIFT's 27 surveyed employers — roughly 200–500 records.

Input: the posting subset and the taxonomy structure. Turnaround is days. If the subset is not readily extractable, we can start from public postings and lose very little.

Output — a Skill Demand Profile, one page:

The "Implied — never stated" column is the whole message. Employers require these skills in fact, do not name them in the posting, therefore they do not reach the curriculum, and therefore the pipeline does not produce them.

At that point step 1 is finished: demand for the role family, denominated in skills rather than job titles, and therefore subtractable. That is the input steps 3, 4 and 5 have never had.

The open question, and the one worth answering next: whether the durable-layer score predicts x-ray reject rate and standards-qualification pass rate better than certification status does. That needs one employer and one criterion — nothing more. It is the measurement that would settle the argument in this document, and we would rather run it than win on reasoning.