SpaceX Plans 10,000 Starships a Year. The Factory Is Half-Built and the Town Doesn't Have Enough Houses.
The Gigabay Signal: From Rocket Factory to Starship Fulfillment Center
SpaceX's Starbase site — a sprawling launch complex at the southern tip of Texas, on the Gulf Coast near Brownsville — is undergoing a buildout unusual for any aerospace manufacturer. The centerpiece is a permitted 700,000-square-foot facility purpose-built for Starship production, designed to enable the production of 1,000 Starships each year. The company has described it as a high-rate assembly environment, a term that signals intent more than it describes current output. The facility sits inside the broader Starbase campus, where the company already stages launch operations and prototype construction.
The Gigabay's footprint matters less for its square footage than for what it implies about throughput. Traditional aerospace manufacturing (think satellite buses or military aircraft) operates on low-rate production lines measured in dozens of units per year. A facility designed for Starship assembly at scale points to a different calculus: building the same vehicle not a handful of times, but repeatedly, on a cadence closer to automotive production than to legacy launch-vehicle manufacturing. The building's design accommodates that shift, with the internal volume and logistics flow needed to move large structures through sequential assembly stages rather than building one vehicle at a time in a fixed position.
Permitting and early construction at Starbase have proceeded in phases, with the Gigabay representing a later-stage commitment to sustained production rather than prototyping. SpaceX's job postings for the site — including a Construction Project Engineer (Starship) role listed at the Starbase address — suggest the company is still in the active buildout phase, hiring to manage the physical expansion rather than only to staff finished production lines. That distinction matters: the roles being posted now shape who gets in the door when the facility ramps.
10,000 Starships a Year: The Production-Rate Assumption Behind the Workforce Math
Elon Musk has said publicly that SpaceX's long-term plan calls for producing roughly 10,000 Starships per year — a target that demands a manufacturing capability roughly 20 times that of the world's highest-volume commercial jetliner production lines. That number doesn't come from a production schedule or a filed capacity plan — it's a stated ambition, repeated across interviews and presentations, that functions as the load-bearing assumption behind every hiring projection and facility decision at Starbase. Treat it as a design target, not a forecast, and the workforce math starts to come into focus.
A single Starship stack (booster plus upper stage) contains on the order of hundreds of thousands of parts: stainless-steel rings, Raptor engines, avionics bays, thermal-protection tiles, actuators, wiring harnesses, and the tooling to join them. No one outside SpaceX knows the exact part count, and the figure shifts as the design iterates. But the scale is enough to make the comparison instructive. A commercial aircraft like the Boeing 737 has roughly 300,000 to 500,000 parts and is produced at a rate of a few dozen per month in a supply chain that took decades to build. SpaceX is talking about producing a comparably complex vehicle (one that has to survive reentry and orbital flight) at a rate of roughly 800 per month, with a supply chain that is, in many cases, still being invented.
That throughput implies a headcount density per vehicle that looks nothing like legacy aerospace. A traditional launch-vehicle program might employ a few thousand people across the full production lifecycle to build a handful of units per year. Scaling to thousands of units per year doesn't just multiply the headcount linearly — it changes the ratio of production workers to design engineers, of technicians to program managers, of quality inspectors to welders. The Gigabay's 700,000 square feet only makes sense if the plan is to run multiple parallel assembly lines with a workforce measured in the thousands, not the hundreds.
The job postings SpaceX is currently listing for Starbase reinforce that reading. Roles like Construction Project Engineer (Starship) and Sr. Application Software Engineer point to a facility still being built out and a production system still being automated — the phase where you need people who can stand up lines, not just run them. The 98 SpaceX roles added in the past week span Starbase, Hawthorne, and Redmond, which tells you the production buildout is pulling talent from across the company's sites, not just hiring locally.
The honest caveat: no one knows if 10,000 Starships a year is achievable on any realistic timeline. The number is a north star, not a commitment. But it's the number SpaceX is designing its facilities and workforce around, and that's what makes it the right lens for reading the hiring signals coming out of Boca Chica.
Who Gets Hired First: Reading the Enterprise Zone Filing for Role Signals
The Gigabay permit tells you how big the building is. The Enterprise Zone filing tells you who walks into it. SpaceX's application through the Texas Enterprise Zone program, tied to a request for $7.5 million in incentives for its Starbase expansion, is the closest thing to a hiring roadmap the company has made public for the Boca Chica site, and it rewards careful reading.
Enterprise Zone designations in Texas require a company to commit to creating a specific number of jobs in a specific place, typically in exchange for tax incentives tied to capital investment. The filings don't usually name individual job titles. But the structure of the application forces a company to describe the kind of facility it's building and the economic activity it expects to generate. When the description points to high-rate vehicle assembly rather than, say, a mission control center or a launch-only pad, the workforce implications narrow fast.
So what does a Starbase hiring plan look like when you map it against the Gigabay's function? Start with the production floor. A single Starship vehicle (Super Heavy booster plus Starship upper stage) involves stainless-steel ring forming, orbital-welded tank sections, tile installation for the thermal protection system, and engine-cluster integration. Each of those process steps demands technicians who can work to aerospace tolerances on a cadence that doesn't exist anywhere in the U.S. right now. The bulk of the jobs are almost certainly production technicians and manufacturing engineers, not design engineers.
This tracks with what's already visible on Zero G Talent's job board. SpaceX's open roles skew toward production-adjacent engineering at Starbase and its Hawthorne headquarters. Construction Project Engineer (Starship) at the Starbase address (1 Rocket Road, Starbase, TX 78520) is the kind of role that only exists when a company is still building the factory while simultaneously preparing to run it. That's a signal: SpaceX is hiring people who can manage facility buildout and production standup at the same time.
The Enterprise Zone filing's scale also tells you something about the support layer. A major facility in rural Cameron County, Texas, means SpaceX isn't just hiring welders and avionics techs. It's building an entire site infrastructure — facilities engineers, safety personnel, quality assurance inspectors, supply chain coordinators, and the logistics staff needed to move stainless-steel coils and Raptor engine components through a facility designed for throughput that no orbital rocket production line has attempted. A traditional aerospace factory producing a handful of vehicles a year doesn't need that density of support roles. A factory targeting double-digit monthly output does.
There's a geographic signal embedded in the filing too. Cameron County sits at the southern tip of Texas, roughly 20 miles from Brownsville, with a workforce that skews toward logistics, light manufacturing, and agriculture — not orbital mechanics. SpaceX's willingness to commit jobs there, rather than clustering new roles near Houston's Johnson Space Center or a major university town, suggests the company has calculated that the skills it needs can be trained locally. That's a manufacturing-hiring assumption, not a research-hiring assumption. You don't put jobs in a border county because you need PhDs in propulsion. You put them there because you need hands on vehicles, repeatedly, at speed.
The one tension the filing doesn't resolve is the split between permanent Starbase roles and roles that will migrate to Boca Chica temporarily as the Gigabay comes online. Factory commissioning, process qualification, and initial production runs tend to pull experienced manufacturing engineers from a company's existing facilities. SpaceX's Hawthorne campus (where Starship prototyping already happens) will almost certainly loan senior production staff to Starbase for months at a time. The Enterprise Zone jobs count as new positions, but some of them may be filled internally before a single external posting goes live.
What's clear is the order of operations. The first wave at Starbase will look less like NASA's civil-service aerospace and more like Toyota's supplier network: process engineers, quality technicians, and manufacturing leads who can build the line before the line builds the rocket. The Gigabay gives them the building. The Enterprise Zone filing gives them the headcount. And the 10,000-Starship target from section two gives them the reason to move fast.
How Starbase Differs From Traditional Aerospace Hiring
Legacy aerospace production lines — Boeing's 737 plant in Renton, Lockheed Martin's F-35 assembly in Fort Worth, Blue Origin's orbital launch vehicle work in Florida — were built around low annual unit counts and long program timelines. A facility producing 30 to 50 flight vehicles per year organizes its workforce accordingly: deep specialization, rigid job descriptions, and long certification cycles for each role. SpaceX's Starbase operation is assembling something different, and the open roles on Zero G Talent's board show where the divergence starts.
SpaceX added 98 roles in the past week alone. Several of them sit at Starbase — titles like Construction Project Engineer (Starship) and Sr. Application Software Engineer, posted to the 1 Rocket Road, Starbase, TX 78520 address. That combination — facilities construction and application software on the same campus, hiring simultaneously — is the signal. Legacy aerospace sites tend to separate capital-project staffing from production staffing from software staffing into different buildings, different reporting chains, different phases. Starbase is collapsing those categories. A rocket factory that is also a test site and also a software integration hub demands people who move across those boundaries without friction.
Traditional aerospace manufacturing hubs stratify the workforce by phase. Design engineers sit in one city. Manufacturing engineers sit in another. Test engineers occupy a third facility, often a dedicated range or launch site. Technicians report to a separate chain entirely. The job titles reflect the silo: "structures designer," "tooling engineer," "quality assurance inspector." Each role has a narrow band of responsibility, and career progression means moving up within that band. The system works when the production rate is measured in dozens per year and the design is stable for a decade.
SpaceX's Starbase hiring pattern (visible across several hundred open roles) suggests a different model. When a single facility is expected to integrate hardware production, software development, launch operations, and continuous design iteration on the same site, the workforce profile shifts. The company needs people who can read a drawing in the morning and debug a telemetry pipeline in the afternoon. It needs technicians comfortable with software-defined workflows and engineers who understand weld sequences. The traditional aerospace career ladder, which separates these tracks at the first rung, doesn't map onto what Starbase is actually building.
This isn't a theoretical distinction. Legacy programs like the F-35 and 737 operate under supply-chain architectures where major subcontractors handle design and integration at their own facilities, feeding final assembly plants that focus on integration and checkout. The workforce at those plants is structured around receiving, inspecting, and assembling components designed elsewhere. Starbase, by contrast, is where the components are designed, where they are manufactured, where they are tested, and where they are launched — often in the same week. That vertical integration flattens the traditional role boundaries. A structures engineer at Starbase is more likely to be on the factory floor interacting with manufacturing than sitting at a desk running analysis in isolation.
The salary bands visible on Zero G Talent's board reinforce this.
| Role / Metric | Source | Location | Range (USD) |
|---|---|---|---|
| Sr. Application Software Engineer | Zero G Talent | Starbase | $165,000 – $230,000 |
| Manufacturing roles (early-career) | Blue Origin | Colorado | $67,005 – $93,806 |
| Manufacturing roles (early-career) | Blue Origin | Washington | $73,095 – $102,333 |
| Starship production target | Elon Musk (public statements) | — | 10,000 units/year |
| Gigabay production capacity | Permitted facility | Starbase | 1,000 units/year |
| Gigabay footprint | Permitted facility | Starbase | 700,000 sq ft |
The practical implication for anyone considering a move to Starbase is straightforward: the job description may look familiar, but the daily work will not. The facility is still under construction. The processes are still being written. The people who thrive there are the ones who tolerate ambiguity and cross functional lines without waiting for a formal handoff. That's a different hiring profile than the one Boeing or Lockheed or Blue Origin optimized for, and it's what makes the Starbase workforce genuinely new — not bigger, not louder, but structurally different from anything the legacy aerospace labor market has produced.
Who Else Is Hiring in the Gulf Coast Space Corridor
Blue Origin is the most direct competitor for the same manufacturing engineer pipeline SpaceX needs at Starbase. The company lists early-career manufacturing roles across five locations, including Van Horn, Texas (roughly 300 miles from Starbase) and Merritt Island, Florida, on the Space Coast. Blue Origin's new graduate rotation program cycles engineers through New Glenn, Blue Engines, and Lunar Permanence over three four-month stints, and the job posting explicitly says "experience in aerospace is not a requirement." That's a signal Blue Origin is willing to pull from automotive, oil and gas, and nuclear backgrounds to staff its production lines, the same non-traditional labor pool SpaceX has been recruiting for years.
The compensation range Blue Origin posts for its Colorado and Washington applicants sets a wage floor that Starbase recruiters have to match or beat for the same mechanical and manufacturing engineering graduates. SpaceX's own Starbase listings on the Zero G Talent board include a Construction Project Engineer role at 1 Rocket Road, Starbase, and a Sr. Application Software Engineer at the same address, which suggests the company is hiring for the Gigabay buildout and the production lines it will feed simultaneously.
The broader labor market is tight. Cameron County officials project SpaceX's presence will generate more than $13 billion in gross economic output and support around 24,000 local jobs through 2026. That figure includes direct SpaceX hiring plus the supplier and service ecosystem clustering around Starbase. When a single employer's expansion promises that many jobs in a county with fewer than 300 current Starbase residents, the competition isn't just Blue Origin versus SpaceX for engineers — it's every role at Starbase competing against every other employer in the Rio Grande Valley for the same finite pool of skilled tradespeople, technicians, and engineers willing to relocate to the southernmost tip of Texas.
What the Gigabay Means for the Broader Space-Economy Talent Map
The Gigabay isn't just a bigger factory. It's a workforce experiment running at a scale the U.S. aerospace sector hasn't tried before, and the early numbers suggest it's already pulling the center of gravity for space-industrial talent toward a stretch of South Texas that most engineers couldn't have pointed to five years ago.
Cameron County's 2026 economic impact report, prepared with SpaceX and shared by County Judge Eddie Treviño Jr., projects the company's operations will generate more than $13 billion in gross economic output and support roughly 24,000 local jobs through 2026. More than 350 local suppliers are now in SpaceX's vendor network. The company has already moved its corporate headquarters from Hawthorne, California, to Starbase, and the site employs over 4,000 workers with plans to nearly double that to around 8,000 in 2026, per ProTexas Industry.
That growth is reshaping who gets hired and where. Roughly 70% of SpaceX's Starbase workforce comes from the Rio Grande Valley — Brownsville, Harlingen, San Benito, Los Fresnos, Port Isabel. The company has told county officials it wants to grow the community itself, stating in incorporation documents that "to continue growing the workforce necessary to rapidly develop and manufacture Starship, we need the ability to grow Starbase as a community." The May 2025 vote to incorporate Starbase as a Type-C municipality passed 212 to 6, with nearly all voters being SpaceX employees or their relatives.
But the local labor pool has limits, and the Gigabay's production timeline will test them. SpaceX's Hawthorne facility remains the primary production site for Falcon 9 and Falcon Heavy, and the company still draws on Silicon Valley for AI and engineering talent. The Starship program, though, is now anchored in Texas. Engineers relocating to Starbase face a 40-minute commute from Brownsville, limited on-site housing (tiny homes, Airstream trailers, modular units) and a K-12 school still under construction. The Texas Tribune reported that, according to one SpaceX engineer, "SpaceX's ability to offer adequate housing to its employees onsite is critical to the development of the space launch complex, and there are currently hundreds of employees on the waitlist to move to the campus."
The knock-on effects are already visible across the Gulf Coast corridor. Cameron County officials say the company's expansion has boosted area schools, workforce training programs, and high-wage manufacturing jobs tied to rocket production. The county is one of only two in Texas with all six major transportation modes (seaport, airport, highway, rail, pipeline, and space) and it's positioning itself as a logistics and research hub for aerospace and related industries.
The tension is that Starbase's success creates both a template and a warning for the rest of the sector. Blue Origin's operations in Florida and Texas, NASA's Marshall Space Flight Center in Alabama, and the growing cluster of space companies along the Gulf Coast all now compete for some of the same welders, propulsion technicians, and manufacturing engineers that SpaceX is pulling into Cameron County at volume. When one employer plans to double its local headcount in a single year, the labor market feels it fast.
The signal for anyone tracking where the space workforce is heading is concrete: SpaceX's board currently lists 98 roles added in the past week, with positions spanning Starbase, Hawthorne, and Redmond. The Gigabay's production target doesn't just change what gets built. It changes who builds it, where they live, and what every other aerospace employer in the region has to offer to keep them.
Working in space? Zero G Talent tracks the openings: browse space jobs, openings at SpaceX, and the people building the field.




