Who Gets Hired: And Who Stays
Terran Orbital sits in an unusual spot: a smallsat manufacturer inside Lockheed Martin's orbit that refuses to be swallowed by it. The CEO describes the last few years as a drift toward the very bureaucracy Terran was founded to disrupt — prime contractors' processes, prime contractors' pace, prime contractors' headcount. Under a "Terran 2.0" reset, the hiring mandate has flipped. The question isn't whether you know aerospace. It's whether you'll break the way aerospace has always been done.
That pivot defines the profile Terran now selects for: cross-disciplinary engineers who have lived inside slow defense primes, want to build flight hardware at startup velocity, and can operate without a safety net of process. Zero G Talent's job board shows 23 salaried positions clustered in Irvine, California, spanning $76,000 to $207,000, with a $155,000 median. Candidates who understand this hybrid space-defense culture and prepare for its technical-behavioral interview loop are most likely to receive an offer.
The postings reveal three core teams driving the current cycle. Flight software and avionics absorb the heaviest engineering demand: FPGA design, embedded software, and independent verification roles signal a push to own the full stack, from radiation-tolerant hardware up through on-orbit autonomy. The CEO has been explicit: the company burned through capital iterating on its identity. Now "time to be grown-ups" means delivering repeatable, high-throughput buses for DoD and commercial constellations. That requires engineers who cross the hardware-software boundary without waiting for a requirements document to clear a committee.
Mission assurance and program management form the second pillar. The Mission Assurance Manager sits at the intersection of Terran's commercial speed and its defense customers' rigor — "support the war fighter" is how the CEO frames the mission. Program managers are expected to run lean, decide in days not months, and push back when production asks for ten more heads or another test rack. The CEO's litmus test: "Are we fully utilizing who we have and what we have?" If the answer is no, the request dies.
Manufacturing and integration shape the third vector, though fewer roles appear on the board. The CEO tracks throughput and capacity utilization as his primary metrics. He has publicly challenged production leads who default to "more people, more equipment" — a habit imported from prime-contractor alumni who flooded in during the scale-up. The new finance chief, a 30-year Boeing veteran, called the decision velocity "giddy as a school kid." That culture shock is intentional. Terran wants hires who have lived inside slow systems and want out.
Across all three teams, the screening filter is consistent: aptitude and attitude outweigh pedigree. "You can teach the skills, but the attitude you can't." The CEO looks for "change agents": people who ask why a process exists and have the confidence to propose a faster path, provided they can pull it off. The distinction between confidence and arrogance, in his words, is the ability to deliver. Remote work is limited; a strict return-to-office policy applies unless an employee lives beyond a defined radius from an operating site. The rationale is blunt: impromptu collaboration drives the speed Terran 2.0 demands.
The net effect favors mid-career engineers who have seen prime-contractor inertia up close, fit that profile. Junior candidates who demonstrate the same bias for action — and a tolerance for failure as a learning mechanism, also fit. What doesn't fit: specialists who need a mature ecosystem to be productive, or applicants treating the role as a seat rather than a mission.
Cross-disciplinary fluency appears non-negotiable. A Staff FPGA Design Engineer earning up to $220,000 must interface across flight software, embedded software, and mission assurance teams. The same posting sits beside a Flight Software Engineering Manager role capped at $210,000: evidence that Terran expects technical leads to bridge domains without a translator.
Practical experience trumps credential signaling. The board data shows no entry-level bands; every posted role starts at staff or manager level. That aligns with the Space Coast pattern where hiring managers prioritize practical experience and team fit over intense algorithmic puzzles. A candidate who has taken a CubeSat from CDR through on-orbit checkout carries more weight than one with a publication record but no flight heritage.
Mission-assurance mindset separates candidates. The Mission Assurance Manager band ($150,000–$195,000) sits squarely in the engineering range. That placement tells you quality is a line function, not a checkbox. Engineers who instinctively write test procedures while they code, who document failure modes before the design review, and who treat waivers as exceptions rather than expectations accumulate trust fast.
Adaptability to hybrid space-defense workflows rounds the profile. Terran's customer base spans commercial constellations and DoD prototypes; the same flight software stack may need commercial-grade CI/CD one week and defense-grade controls the next. Employees who can context-switch between speed and rigor without culture shock become the architects others build around.
What the Pay Looks Like
Terran's compensation structure reflects its position at the intersection of commercial smallsat production and defense-grade engineering. Zero G Talent's live listings show a salaried band running from that range across 23 active roles. That range sits above the $84,000 average Florida Today cited in 2021 when the company announced its Space Coast factory and 2,100 projected jobs, and well above third-party estimates for the region.
The highest bands belong to hardware and flight-software specialists, Zero G Talent reported a $220,000 top for Staff FPGA Design Engineer, and Zero G Talent found $210,000 tops for Flight Software Engineering Manager and Staff/Principal Flight Software Engineer roles:
| Role | Location | Salary Band (USD/year) |
|---|---|---|
| Staff FPGA Design Engineer | Irvine, CA | 170,000 – 220,000 |
| Flight Software Engineering Manager | Irvine, CA | 150,000 – 210,000 |
| Staff/Principal Flight Software Engineer (IV/V) | Irvine, CA (Hybrid/Remote) | 150,000 – 210,000 |
| Staff Embedded Software Engineer | Irvine, CA | 160,000 – 190,000 |
| Mission Assurance Manager | Irvine, CA | 150,000 – 195,000 |
| Program Manager | Irvine, CA | 140,000 – 175,000 |
These are base-salary ranges only; equity and bonus components are not disclosed in postings. For comparison, a 2026 survey of the Palm Bay–Melbourne corridor places senior AI/ML roles at major defense contractors between $130,000 and $220,000, with principal autonomy positions at Northrop Grumman reaching $221,000. Terran's top bands are competitive with that peer set.
The Florida operation adds a structural advantage: no state income tax. For a $155,000 median earner, that translates to roughly $7,000–$9,000 more take-home pay versus California or Colorado peers. The region's prevalent 9/80 schedule — every other Friday off — further shifts the effective hourly rate without changing the headline number. Cost of living in Brevard County runs below Los Angeles or Denver, so the real purchasing power of these bands is higher than the nominal spread suggests.
Entry-level and associate roles are not explicitly listed in the current board snapshot, but the $76,000 floor and the 2021 projection of a $84,000 average across 2,100 hires imply a pipeline of early-career positions in integration, test, and production engineering. Candidates should expect the lower third of the band ($76,000–$110,000) to correspond to early-career titles, while the upper third ($170,000+) maps to staff and principal IC tracks or first-line management.
Negotiation leverage comes from demonstrated flight heritage (hardware that has survived launch and on-orbit commissioning) and from clearance eligibility. The company's hybrid commercial/defense portfolio means roles touching classified programs may carry a premium over equivalent commercial-only seats, though the board does not break that out explicitly.
How the Interview Loop Works
Terran's interview process reflects its position as a smallsat manufacturer pushing toward high-rate production: fast-paced, practical, and built around fundamentals. The loop favors first-principles thinking over rehearsed algorithm patterns, a necessity when building satellites that must operate on orbit with limited power, compute, and thermal margin.
Recruiters screen first for clearance eligibility and domain fluency. Terran's hybrid space-defense posture means many programs require a U.S. security clearance. The initial phone screen typically verifies citizenship, clearance status, and whether the candidate has shipped flight hardware, not just simulated it. Resumes that list "CubeSat experience" without specifying bus architecture, interface control documents, or environmental test campaigns get deprioritized.
The technical panel is where the fundamentals test lives. Expect whiteboard sessions on power budgeting for a 6U bus, thermal modeling for a high-duty-cycle radar payload, or fault-tree analysis for a propulsion subsystem. Software candidates walk through a flight software fault scenario: watchdog reset during a critical maneuver, memory scrub failure on a rad-hard processor, or RTOS priority inversion. The interviewers — often the same engineers who will sit on the design review — evaluate whether the candidate isolates root cause, proposes a fix that fits within existing flight code margins, and articulates the verification evidence needed to close the anomaly.
Behavioral rounds use STAR-format prompts tied to program milestones: "Describe a time you traded mass margin for schedule risk on a flight program." "Walk us through a design review where you disagreed with the chief engineer." The company's public statements about building "the world's largest constellation of software-defined synthetic radar satellites" and using robotics to "speed up what we do and do it much more efficiently and more accurately" indicate they value candidates who have navigated volume production trade-offs, not just one-off missions.
Common disqualifiers include: inability to obtain or maintain a U.S. security clearance; no prior flight hardware delivery (ground test only); gaps in ITAR/EAR compliance awareness; and treating the interview as a generic software exercise rather than a systems engineering conversation. Candidates who frame their experience exclusively around cloud-native DevOps, container orchestration, or high-level ML frameworks, without connecting those tools to bare-metal, radiation-hardened constraints, signal a mismatch.
The loop typically spans three to four weeks from screen to offer. Reference checks focus on program-level impact: did the candidate's work fly, and did it meet on-orbit performance specs? Offers are benchmarked against the board's observed band ($76k–$207k, median $155k) and structured with base, equity, and milestone bonuses tied to launch cadence.
Where You'll Work
Terran's job postings consistently list Irvine, California as the primary work location across engineering, software, and program management roles. Staff FPGA Design Engineer, Flight Software Engineering Manager, Staff/Principal Flight Software Engineer (IV/V), Mission Assurance Manager, Staff Embedded Software Engineer, and Program Manager positions all reference Irvine, with the flight software role explicitly noting hybrid or remote flexibility. This concentration suggests the company's core engineering and manufacturing workforce operates from a single Southern California campus rather than a distributed multi-site footprint.
The Irvine facility anchors Terran's satellite production line. The company describes it as a manufacturer delivering "flight-proven spacecraft and advanced mission capabilities" with platforms featuring "interchangeable components and modules" that allow customization for various mission requirements. Building and delivering more spacecraft than most competitors, as the company claims, requires integration floors, environmental test cells, and machine shops capable of fabricating and qualifying flight hardware at volume. The March 2026 appointment of Kwon Park as Senior Director of Manufacturing Operations signals continued investment in production capacity at this site.
What the public record and job data do not specify is the internal layout: whether cleanroom integration bays, thermal-vacuum chambers, vibration tables, or radiation-test facilities sit on-site or are accessed through partner ranges. The Nebula Bus program for Mitsubishi Electric's LEO demo mission, the AFRL Oracle-Prime milestone, and NASA's CAPSTONE 02 lunar mission all imply a test campaign that moves hardware through functional checkout, environmental qualification, and pre-ship review: steps that typically demand dedicated lab space. The company's star tracker product line introduction at SATSHOW 2026 further suggests optical calibration and characterization capability.
For candidates, the practical takeaway is geographic: most roles are Irvine-based with hybrid flexibility for select software positions. The concentration of manufacturing, flight software, FPGA, and mission assurance openings in one location means cross-disciplinary collaboration happens in person, a factor that aligns with the company's described hybrid space-defense culture where rapid iteration between design, test, and operations is routine. Engineers who need daily access to flight hardware, test racks, or integration teams will work on-site; those in pure flight software or FPGA verification may negotiate remote days. The board data shows no postings for other U.S. sites (Florida, Virginia, Colorado) or international subsidiaries, though the ESA planetary defense mission selection hints at European program office activity not yet reflected in hiring.
If your role requires touching flight hardware, plan for Irvine.
The Signal in the Noise
Terran's board data shows sustained demand for senior cross-domain engineers at defense-prime compensation levels. In this sector, that demand pattern is its own signal: the people who stay are the ones who treat every integration bay like a clean room and every schedule slip like a personal failure. The company that once drifted toward prime-contractor bureaucracy now hires only engineers willing to do so — and prove they can deliver what comes after.
Working in frontier tech? Zero G Talent tracks the openings: see every open Terran Orbital role, browse frontier tech jobs, the companies hiring, and the people building the field.