Raptor 3’s 280 Tonnes Sit on One Desk—But a 'Monastery' Stalls Hire
Raptor Role Postings Define the 3rd-Gen Engine Scope
SpaceX is hiring propulsion engineers at Starbase to develop and own the third-generation Raptor engine as Starship manufacturing scales.
The openings are not vague calls for rocket scientists. They are precise job descriptions that map the boundaries of the 3rd-gen program. The company is working on the latest Raptor variant and expanding Starship manufacturing at the Starbase, Texas site. Per nextbigfuture.com, Raptor 3 fired first in August 2024 and reached scaled production by early 2025.
On June 4, 2026, a Propulsion Engineer role on the Raptor Development Operations team went live on Built In. SpaceX pulled the post the same day at 10:29 UTC, but the text still lays out a clear charter. The listing says the engineer will own development, production, and operation of the engine ignition system, transient sequences, and associated combustion devices and hardware that start and shut down the engine in all flight phases. That scope reaches from drawing board to pad.
"As a Propulsion Engineer on the Raptor Development Operations team, you will be responsible for guiding development of future versions of Raptor as well as end-to-end ownership of one or more systems on the engine." — SimplyHired listing
The same description directs the hire to drive all necessary work to develop, operate, and fly (and re-fly) hardware on the most advanced full-flow staged combustion engine that boosts the largest launch vehicle ever built. SpaceX developed Raptor as a methalox engine family, and it became the first full-flow staged combustion engine to power a vehicle in flight. The listed duties include owning design, analysis, development, sequencing, and flight operations for Raptor ignition and transients. The engineer also owns hardware design and requirements, hits production throughput targets, and keeps the engine reliable from startup to mainstage to shutdown.
Those duties explain the coding skills the post requires. The hire must automate analysis of test and flight data to enable high launch cadence. The role also demands that the engineer flag, organize, and drive hardware and sequence changes to simplify parts, boost reliability, raise performance, and make the whole vehicle stack succeed. That ties one engineer’s desk to the entire Starship.
SpaceX [https://www.spacex.com/] is also recruiting Raptor Integration Engineers for Starbase, TX and McGregor, TX, per a LinkedIn post. A Greenhouse posting for the Raptor Fleet Operations team says that group manages the engine fleet from the moment units leave the Hawthorne factory until they fly.
| Role level | Annual salary band (USD) |
|---|---|
| Propulsion Engineer Level I | $100,000 – $115,000 |
| Propulsion Engineer Level II | $110,000 – $135,000 |
Those bands come from the June 4 Built In listing. SpaceX added 159 roles in the past 7 days, with a median salary of $145,000 across 1,061 open roles (SpaceX). The propulsion pay sits below the silicon and AI positions topping the recent add list, but it reflects the specialized, system-owning nature of the work.
The postings show that the new engine program is not about bolting parts. An engineer owns a system from concept to flight and back. That definition sets the hiring bar at Starbase.
Raptor 3 makes about 280 tonnes of sea-level thrust. At McGregor, SpaceX fired Raptor engines 24 times in a recent week, roughly three test burns a day. The engine family’s scale matches the all-in ownership the postings demand.
End-to-End Ownership Replaces Prototype Handoffs
SpaceX’s August 2025 posting for the Raptor Integration propulsion engineer role draws a hard line between prototype-era handoffs and the current fleet model. At the Texas site, this consolidation pairs with the manufacturing expansion already underway.
Single-Desk Accountability
The new Raptor propulsion postings demand one person own whole systems. A SimplyHired copy of the development operations role states the engineer “is accountable for defining requirements, developing operations, verifying capability, and ensuring compatibility with the vehicle for the system(s) you own.” That removes the buffer of sequential sign-offs. The job expects the hire to make calls alone on vague specs with minimal oversight.
The fleet operations model breaks the chain of discrete prototype handoffs. The propulsion engineer links hardware and reliability engineering teams and builds maintenance processes for the engine fleet. The posting explicitly requires the hire to feed the production line and design engineering to cut cost per ton to orbit. That loop turns line workers into system owners rather than part swappers.
Flight Data Closes the Loop
Today, the team is focused on enabling rapid design iteration by taking lessons from flight and engine testing and applying those lessons across the fleet.
The quote above from the August 2025 Built In listing shows the speed expectation. Flight data no longer waits in a report that a separate group reads months later. It feeds the same engineer who owns the subsystem. That compresses the cycle from test anomaly to hardware change.
From Prototype Shop to Fleet Production
This structure signals manufacturing maturation. A company building one-off demonstration engines can tolerate handoffs because volume is low. When the goal is a reusable fleet flying at high cadence from Starbase and a new Florida site, single-owner accountability scales better. The listing looks forward: “In the future, the team will begin to focus on developing the processes necessary to maintain a large fleet of engines capable of continuous reuse.” That shows a production mindset, not a prototype shop.
Nerra Network reported in a July 4, 2026 episode that static fire runs at Starbase confirmed six Raptor engines performed as expected and that long-duration burns reduce uncertainty around throttle response and shutdown sequencing for orbital refueling. If reliability holds at this scale, the bottleneck moves from individual engine testing to parallel vehicle assembly at both Starbase and Florida. The data also guides production rate planning. SpaceX and contractors target an initial orbital-class flight from the Florida site before year-end, spreading launch cadence risk away from a single Texas location.
The Raptor propulsion engineer role now binds design, fleet operation, and production feedback into one desk. That is the organizational shape of a company moving from proving an engine exists to proving it can be built, flown, and reflown without passing the buck.
The Starbase Engineering Labor Constraint
SpaceX shifted its headquarters from California to Texas, raising a hiring wall at Starbase, the South Texas launch and testing hub the company has run since 2019. Musk named the friction the “significant other” problem: married engineers and technicians hesitate to relocate because partners see few local jobs. The complaint comes as the company expands vehicle production and develops its latest engine family, positions that require single-owner propulsion accountability. The relocation drag directly shrinks the candidate pool for those specialized roles.
Starbase sits in a sparsely populated border strip near the US-Mexico line, across from the undeveloped Las Palomas Wildlife Management Area. The nearest city is Brownsville, a 40-minute drive per Google Maps, with roughly 187,000 residents based on recent US Census figures cited by American Bazaar in February 2026. Other SpaceX sites tell a different story:
| Site | Nearest population center | Approx. population | Commute to urban core |
|---|---|---|---|
| Starbase, TX | Brownsville | ~187,000 | 40 min |
| Giga Texas, Austin | Austin | ~1,000,000 | 30 min |
| El Segundo, CA (former HQ) | Los Angeles metro | millions | embedded |
Musk said in June the odds of a trailing spouse finding a non-SpaceX job near Starbase are “pretty low.” He called the place “a technology monastery thing. Remote and mostly dudes” (Economic Times, June 2026). The joke points at a real deficit: the regional economy outside the rocket gate is thin. American Bazaar reported in February 2026 that many married candidates stall relocation because spouses face limited prospects. For propulsion engineers who must own Raptor systems end-to-end, that stall removes experienced people from the funnel.
SpaceX has tried to engineer a fix. Musk, who predicted in February 2026 that Austin would be “the biggest boomtown that America has seen in 50 years,” built Snailbrook, a company town near Boring Company and SpaceX sites. Starbase is now an official city with 3,400 employees; a giant Gigabay factory is rising to build 1,000 Starships a year. Those steps add housing and some internal jobs, but they don’t birth outside employers for partners. The “significant other” problem stays.
Zero G Talent’s board reveals the geographic spread of new postings. The newest listings cluster in Sunnyvale, Palo Alto, Washington DC, and other non-Texas spots — not Starbase. The lack of fresh Starbase propulsion entries matches Musk’s relocation gripe. When the local two-body math fails, the recruiter spreads the net to California and DC.
Propulsion engineers weighing the SpaceX Raptor openings should price the spouse employment gap before packing. The factory will keep raising rockets; the border county won’t suddenly sprout a second industry.
Working in space? Zero G Talent tracks the openings: see every open SpaceX role, browse space jobs, openings at Blue Origin, and the people building the field.
