The engine dictates the org chart
The adaptive jet engine Astro Mechanica is building has no precedent — one powerplant efficient from takeoff through Mach 3, replacing the traditional afterburning turbofan with a turbogenerator driving electric propulsors. That architecture exists in no textbook, so the people who build it cannot be hired from a resume stack of prior experience. The question isn't what they've done before; it's whether they can make something work when the default assumption is that it won't. Astro Mechanica recruits engineers for its propulsion development teams in San Francisco, offering competitive compensation grounded in first-party data; candidates succeed by showing technical depth, hands-on build experience, and resilience in unstructured problem-solving, as validated by employee accounts and company documentation.
The team structure reflects an engine-first, then airframe sequence that inverts conventional aerospace. Founder Brooke (business) and co-founder Ian (technical) split the conceptual and operational loads, a partnership formed after a two-hour phone call where Ian openly listed his gaps and Brooke recognized they matched her strengths. The organization clusters around three propulsion pillars: the turbogenerator (hot section, leveraging existing turbofan cores), the electric propulsor array (cold section, developed in-house), and the power electronics bridging them.
The hiring philosophy is explicit: recruit from rocketry, not commercial aviation. Rocket programs add humans last, so their engineers are conditioned to iterate fast, test hard, and accept failure as data. Airplane programs optimize for human safety from day one, which slows everything down. Astro Mechanica bets it's faster to teach rocket people airplane constraints than to teach airplane people rocket speed. That filter shows up in the roles: power electronics, gearbox dynamics, mission systems, disciplines where space launch and hypersonics have already solved adjacent problems at higher tempo. If you're a mechanical engineer who's only ever drawn flanges on a turbofan, you're not the profile. If you've designed a rotor that survived a 30,000 rpm spin test on a rocket turbopump and can explain the bearing load path to a power electronics lead over lunch, you are.
Inside the test cell
Astro Mechanica operates out of San Francisco, where its job postings all list the same city. The company does not publicize a street address, but the facility has been documented on video: a propulsion test cell that two years ago housed a single propulser stand and now runs two, with a turbo generator positioned between them. That generator burns jet fuel to produce electrical power, which feeds both propulsers, the cold-side hardware that delivers the majority of thrust in the duality architecture. The test cell is the physical center of the engineering loop; everything else in the building serves it.
Growth since the last documented visit has been physical as well as organizational. The addition of a second propulser stand doubled parallel test capacity, a direct response to the test cadence the company describes as "an extreme amount of testing." Gen 4 hardware, a subscale but functionally identical predecessor to the Gen 5 flight engine, occupies the stands today. The facility also accommodates airframe work: the team has moved from engine-only development to building the 5x5 demonstrator aircraft, a five-passenger, 5,000-nautical-mile vehicle that will validate the propulsion system in flight.
The workspace is not a showroom. Co-founder Ian has described the design philosophy as Apple-like attention to components no customer will ever see, but the facility's purpose is iterative verification, not display. There is no separate "lab" and "factory" — the test cell is the factory's heartbeat. Engineers work in the noise and vibration environment of running hardware because the schedule demands it: a proof-of-concept engine in two months, a flight-capable engine in three, first test flight targeted within two years. That tempo only works when the people designing the next iteration are standing next to the hardware that just finished its last run.
Remote roles exist, and Mission Systems Lead is listed as remote, but the core propulsion, manufacturing, and power electronics teams are anchored to the San Francisco site. For a candidate, the workspace signal is clear: you will be measured by what the test stands show, not by what a presentation deck promises. The building exists to turn jet fuel into data, and the people who thrive there are the ones who treat that conversion as the only metric that matters.
How they pick the team
Astro Mechanica's hiring philosophy rejects process-heavy evaluation in favor of identifying exceptional individuals and giving them autonomy — a bet that the best people, unrestricted, outperform rigid workflows backed by extensive testing. Brooke articulated it directly: "The bet that we make is if you find like the best people and give them free reign to go do their job, you will be able to move more quickly. And the way in which we like make sure we have a good safe thing at the end is by doing just an extreme amount of testing."
The origin story of Brooke's own partnership illustrates the informality. Brooke cold-DMed Ian on Twitter after two months on the platform. They spoke for two hours. Brooke recalled two signals that mattered: Ian had "navigated basically all the conceptual levels of building an aerospace company for the next 30 years back down to he has invented a new type of jet engine architecture down to the fact that he could literally build these things himself," and he openly admitted "here are the things I'm not good at." That combination, full-stack technical depth across concept, architecture, and hardware, plus candid self-assessment, appears to be the template.
The company explicitly filters for background type. Brooke stated they prefer "rocket people who know how to go fast" over traditional airplane engineers because "it's easier to take them and teach them about airplanes than teach airplane people how to go fast." The reasoning: airplane culture optimizes for human safety through slow, careful process; rocket culture iterates rapidly because humans are the last thing added. Astro Mechanica's dual-mode engine, targeting both regimes, needs the latter tempo.
Mindset screening is explicit. "The default on everything is that it doesn't work," Brooke said. "It is not useful to say hey this is all the ways it's not going to work... What you need to focus on is what are the ways that it can work. How do we make that happen? That is such a different frame of mind that you need to find in people." Candidates who default to failure-mode enumeration rather than path-finding are screened out.
The bar is framed in historical terms: "This is like old NASA where you're like this is like humanity's best... It should be something very special to be here. I need to reward that with like in your peers everybody is fully on this level." Peer caliber is part of the value proposition and the filter.
No public documentation details formal interview stages, coding challenges, or panel structures. The available evidence points to a process driven by direct founder engagement, technical depth verification, mindset alignment on rapid iteration versus process compliance, and a preference for demonstrated build experience over credentials. Candidates who reach the conversation stage should be prepared to discuss not just what they've built, but how they navigate ambiguity when the default state is failure.
The people who stay
That autonomy is not a perk — it's the operating model. The company pairs it with a verification discipline Brooke describes as that regimen. Candidates who need detailed specifications before they start, or who equate process with progress, tend to stall. The people who stay treat a blank sheet as a design prompt, not a blocker.
The clearest signal comes from Ian, the co-founder who invented the dual-mode engine architecture. Brooke's assessment captures the profile: that full-stack depth she outlined earlier. That vertical range, a 30-year roadmap to bench-level fabrication, is the baseline. Ian also demonstrated the self-awareness Brooke values: he openly admitted his gaps, which she notes is rare. Intellectual honesty about your own gaps is a hiring criterion.
Underpinning the speed requirement is a specific cognitive frame. Brooke puts it this way: the default assumption is failure, so focus on the paths that work — a frame of mind she screens for. Solution-oriented first-principles thinking, not risk enumeration, is the daily currency. The company's own origin story illustrates it: that same timeline. "We're not looking for like 1 to 2% gains. We are really looking at revolutionary gains here."
Craftsmanship coexists with that velocity. Ian cites Apple as a reference: "For those that notice the details, they really appreciate it. Not everybody will see it. Apple embodies this completely. Like even components inside of the phone that you're never going to see, those should be like thoughtful and beautiful." He adds, "Design was always incredibly important to me. And when you look at this with airplanes, it's like they're a little too functional in a way. Like I want to make genuinely the best thing I can." That standard applies to internal geometries no passenger will ever see. Engineers who take pride in finish quality when no one is auditing them fit; those who treat "good enough for test" as a destination do not.
The peer environment is deliberately elite. Brooke states the goal: to build a peer group at that same elite standard, where everyone operates at the same level. That density of talent is both a filter and a retention mechanism — people stay because the person at the next bench is operating at the same level.
Mission alignment closes the loop. The roadmap spans five-passenger private jets to 100-seat transpacific airliners, a half-trillion-dollar market if executed. Brooke recalls a candidate's reaction: "I kind of off-handedly said this to a candidate one day and he kind of pauses and looks off and says, 'Wow, I could see my family in India more than once a year.'" That personal connection to the outcome, not just the engineering challenge, marks the people who sustain the pace. The company builds engines to shrink the planet; the engineers who thrive are the ones who want that world badly enough to build the hardware that makes it possible.
What the offer letter says
Astro Mechanica's compensation structure reflects a company that has moved past seed-stage improvisation into a capitalized build phase. The $27 million Series A, led by Andreessen Horowitz and Lower Carbon Capital with a strategic check from United Airlines Ventures, closed in 2024, gave the company runway to pay at or above market for the specialized talent its propulsion architecture demands.
| Role | Location | Base Salary Band (USD/year) |
|---|---|---|
| Head of People | San Francisco | $250,000 – $340,000 (Zero G Talent's data shows) |
| Chief Engineer, Defense | San Francisco | $220,000 – $300,000 (Zero G Talent reported) |
| Director of Manufacturing | San Francisco | $200,000 – $250,000 (Zero G Talent's figures put) |
| Mission Systems Lead | Remote | $180,000 – $250,000 |
| Senior Power Electronics Engineer | San Francisco | $175,000 – $230,000 |
| Mechanical Systems Engineer, Gearbox | San Francisco | $150,000 – $225,000 |
The top of the market attaches to roles that combine technical authority with organizational leverage. The Chief Engineer, Defense band signals a dedicated defense business line, not just a commercial program — someone who can navigate ITAR, interface with government program offices, and still speak the language of the turbo-generator and propulser teams. The Head of People band is unusually high for a ~50-person company; it reflects a founder-level belief, stated explicitly by CEO Brooke, that "the place for truly the sharpest" requires a talent function that can recruit and retain peers who match the existing engineering density.
Manufacturing leadership sits at $200,000–$250,000, consistent with the shift from proof-of-concept to rate production. The Gen 4 subscale engine and the Gen 5 flight engine both demand tooling, fixturing, and process control that didn't exist when the team was running two propulsor stands. The Director of Manufacturing owns that transition.
Remote-eligible roles carry a modest discount. The Mission Systems Lead band overlaps the San Francisco engineering bands but tops out lower, reflecting the company's preference for on-site presence at the test stands. Power electronics and mechanical gearbox roles, both core to the dual-mode turbo-generator architecture, sit in the $150,000–$230,000 corridor. These are individual-contributor positions with direct hardware ownership; the width of each band accounts for the gap between a senior engineer who has taken a propulser from hot-fire to flight qualification and one who hasn't.
The Gen 5 flight article will spin up on the same test stands that ran the first propulser two years ago. The engineer who signs off on that hot fire will have come through the filter this piece describes — rocket tempo, blank-sheet ownership, and a peer group that treats "it doesn't work" as the starting assumption, not the conclusion.
Working in frontier tech? Zero G Talent tracks the openings: see every open Astro Mechanica role, browse frontier tech jobs, the companies hiring, and the people building the field.