How Work Gets Done: Pace, Structure, and Decision Making
A satellite the size of a school bus, built once every 5 to 10 years for billions of dollars — that is the Lockheed Martin model, as CEO Peter Krauss describes it. Terran Orbital exists because customers now want dozens of satellites, delivered in months, at a fraction of the cost. The gap between those two realities defines every workflow, meeting cadence, and approval chain inside the company today. This piece maps how Terran Orbital's engineering workflow and decision-making structure connect to its hiring criteria and employee realities to show which professionals will thrive or struggle.
Since the November 2024 merger, Terran Orbital has operated as a wholly owned but independent subsidiary ("arms length or more," in Krauss's phrasing) with a mandate to remain a merchant supplier to the broader market, not a captive Lockheed shop. That structural independence sets the operating tempo. Krauss, a 30-year entrepreneur who took the reins to lead "Terran 2.0," describes the organization as an "old startup": 12 years old, but having spent the prior three to four years scaling by hiring heavily from Northrop Grumman, Boeing, and Lockheed itself. The result was a culture drift toward prime-contractor bureaucracy (committees briefing committees, five sign-offs for a change) that the current leadership is actively unwinding.
The contrast is deliberate. A newly hired SVP who spent 30 years at Boeing told Krauss he was "giddy as a school kid" after six weeks because "how fast we move, how quick we make decisions, how decisive we are." Krauss frames it as risk mitigation versus risk avoidance: primes avoid risk; Terran manages it. That philosophy shows up in authority distribution. Krauss personally challenges headcount and capital requests from production, asking "Do you really need those 10 additional people? Are we fully utilizing who we have and what we have?" and rejects them if utilization isn't maximized. Throughput and capacity utilization are the manufacturing KPIs he watches most closely, alongside "people focus metrics" tied to the ongoing culture transformation.
Physical presence reinforces the speed mandate. A strict return-to-office policy requires most staff on-site; remote exceptions exist only for employees beyond a set radius from a company location. Krauss argues that impromptu collisions (break room conversations and the ability to "get in a room and even bang heads sometimes") produce faster consensus than scheduled video calls. The team tried distributed work during the pandemic; leadership considers that chapter closed.
Decision rights are concentrated but not bureaucratic. Krauss describes his own style as "say yes and then figure it out," distinguishing confidence from arrogance by the ability to deliver. That same bias for action is what he screens for in leaders: people willing to accept a challenge, focused on mitigating risk rather than avoiding it, and unbothered by the perception of a misstep. The organization's size, smaller than Lockheed, Boeing, or Northrop, lets it execute a "quick 180" when a call proves wrong, a luxury the primes rarely afford.
The workflow is built around manufacturing discipline applied at startup velocity. "Business is business, manufacturing is manufacturing," Krauss says, even when the output is a highly technical spacecraft. Cross-disciplinary accountability replaces sequential handoffs; capacity is squeezed before it's expanded. For engineers and managers coming from prime environments, the shift means fewer gates, tighter loops, and direct exposure to the consequences of their calls.
Values in Practice: What the Work Reveals
Terran Orbital's public materials do not present a canonical list of operating principles. What the research shows is a pattern of project choices, partnership structures, and technical commitments that function as de facto values, observable in the work the company takes on and the way it delivers that work.
The clearest signal comes from the CAPSTONE mission. Terran Orbital built the 12U CubeSat bus that carried NASA's Cislunar Autonomous Positioning System into a near-rectilinear halo orbit around the Moon. The spacecraft launched on Rocket Lab's Electron in June 2022, survived communications and propulsion anomalies during a four-month transit, and achieved orbit insertion on November 13, 2022. NASA extended the mission through December 2025, then confirmed in June 2026 that all primary and extended objectives were met. Advanced Space and Terran Orbital jointly managed operations for the duration. A mission that overcomes early anomalies, meets extended objectives, and stays operational for nearly four years reflects an organizational tolerance for risk during development and a discipline for recovery during operations — both cultural traits, not just technical ones.
The Lockheed Martin Next-Generation Space Dominance partnership reinforces that pattern. Lockheed selected Terran Orbital to supply core bus subsystems (avionics, software, radios, and cameras) for a modular spacecraft line built on LM LINUSS and LM 50 heritage. The NGSD program is explicitly framed around speed, cost efficiency, and "mission agility at scale." Tim Lynch, Lockheed Martin's Mission Strategy and Advanced Capabilities Vice President, stated the customer need: "Our customers are not always able to wait years for custom-made satellites. They want proven, production-ready capability that can be delivered on a deadline that aligns with the operational timeline of their mission." Terran Orbital's role as subsystem integrator for that production-ready line suggests a value placed on repeatability, manufacturing maturity, and schedule credibility — the ability to say "we can deliver this bus on this date" and have a prime contractor stake its program on it.
The CAPSTONE bus had to fit a 12U form factor, survive a low-energy lunar transfer, and host a novel navigation payload. The NGSD subsystems must slot into two common-core variants (Vanguard and Sentinel) with interchangeable payload units and autonomous rendezvous and proximity operations capability. In both cases, the engineering problem is not "build the best possible subsystem" but "build the subsystem that integrates, qualifies, and flies on the customer's schedule." That constraint-driven mindset shows up in hiring: the board lists Program Manager at $140,000–$175,000, a role that exists to translate technical risk into schedule certainty. The research does not capture internal rituals, such as design reviews, anomaly response protocols, or how trade studies are adjudicated. But the external evidence points to a company that treats reliability as a production capability, not a research outcome.
Hiring and Employee Reality: What the Data Shows
Terran Orbital's live job board on Zero G Talent reveals a hiring profile weighted heavily toward senior engineering and assurance disciplines. The six most recent postings, all based in Irvine, California, with one flight software role open to hybrid or remote work, cluster in a narrow compensation band, with Zero G Talent's board data putting the flight software ceiling at $210,000:
| 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 |
| Mission Assurance Manager | Irvine, CA | $150,000–$195,000 |
| Staff Embedded Software Engineer | Irvine, CA | $160,000–$190,000 |
| Program Manager | Irvine, CA | $140,000–$175,000 |
The role titles themselves signal the selection criteria. "Staff" and "Principal" prefixes appear on four of six postings, indicating an expectation of deep technical ownership — not just execution but architecture decisions, cross-subsystem integration, and mentorship. The FPGA role points to payload and bus electronics where radiation-hardened logic and timing closure are non-negotiable. The flight software roles, including a dedicated IV&V (independent verification and validation) track, show that flight code quality gates are a first-class hiring priority, not an afterthought. Mission Assurance at the manager level suggests the company treats reliability as a programmatic function with dedicated leadership, not a checklist item. Program Manager sits alongside engineering leads at comparable pay, signaling that schedule and technical risk ownership are peer disciplines.
The geographic concentration in Irvine, with only one role explicitly offering hybrid/remote flexibility, implies a culture where hardware bring-up, integration testing, and daily cross-discipline stand-ups happen in the lab. Candidates who need full remoteness will self-select out; the board data makes that constraint visible before a recruiter screens them.
What the board does not show, and what the research digest fails to provide, is any first-party description of Terran Orbital's stated hiring values, interview rubrics, or candidate evaluation frameworks. The digest supplied consists entirely of Foot Locker, Inc. career pages and contains zero Terran Orbital–specific hiring collateral. No published competency matrix, no "bar raiser" equivalent, no public engineering blog posts describing interview loops. That absence is itself a signal: either the company keeps its hiring criteria internal, or it has not invested in external employer branding around talent selection.
From the posting pattern, a reasonable inference emerges: the bar selects for engineers who have already operated at staff/principal scope in flight hardware or mission-critical software, who can demonstrate IV&V rigor, and who accept Irvine-lab presence as a condition of the work. The median $155,000 across 23 salaried roles suggests the broader organization includes mid-level contributors, but the visible senior roles set the tone. Candidates without flight heritage, without FPGA or embedded flight software ship history, or without experience writing requirements that survive vibration and thermal vacuum will likely stall at the technical screen.
Public employee-review data for Terran Orbital is notably thin. As of this writing, neither Glassdoor nor Blind nor comparable platforms surface a statistically meaningful sample of attributed, dated reviews for the company — a gap that itself signals something about the organization's size, opacity, or the tenure of its workforce. Zero G Talent's live board shows 23 salaried Terran Orbital postings with a band of $76,000–$207,000 (median $155,000). The absence of junior or mid-level listings suggests either that those roles are filled internally, that hiring is currently skewed to experienced hires, or that the company recruits earlier-career engineers through channels not captured on this board. The salary ceiling at $220,000, as Zero G Talent's board data shows, for a Staff FPGA role is competitive with Southern California defense-space peers but does not reach the top of the Bay Area scale — consistent with an Irvine-based cost structure.
The press-release record provides a proxy for operational tempo. Between January and July 2026, Terran Orbital announced six material milestones: a Nebula bus delivery for Mitsubishi Electric's LEO demo (January); a Star Tracker product line debut at SATSHOW (March); subsidiary selection for ESA's Apophis planetary-defense mission (March); Kwon Park's appointment as Senior Director of Manufacturing Operations (March); AFRL Oracle-Prime milestone advancement (April); NASA CAPSTONE 02 lunar mission award (July). Six announcements in seven months implies a shipment or milestone roughly every five weeks. For hardware teams, that cadence translates to overlapping integration-and-test flows, frequent design reviews, and limited schedule margin — conditions that reward engineers who thrive on parallel workstreams and penalize those who need long, uninterrupted design cycles.
Park's appointment (March 2026) is the only named personnel move in the public record during this window. His title, Senior Director of Manufacturing Operations, and the timing, coinciding with multiple flight-hardware deliveries, suggest the company is investing in production throughput and yield. Employees in assembly, integration, and test (AIT) or supply-chain roles would feel that shift directly: new work instructions, revised inspection points, likely a push toward first-time-right metrics. Whether that pressure is experienced as "support to hit rate" or "squeeze without headcount" is not documented in any attributable employee comment.
The Star Tracker product-line introduction (March 2026) marks a move from bus-level integration into component-level supply. That expansion typically pulls systems engineers into new qualification campaigns, pulls FPGA and firmware staff into sensor-level firmware, and pulls program managers into new customer interfaces. The Mitsubishi Nebula delivery (January 2026) and the ESA Apophis selection (March 2026) deepen the portfolio across commercial, civil, and defense customers — each with distinct documentation, security, and review regimes. The cross-program complexity is real; the staffing response to it is not visible in the open data.
The lack of public employee narratives may reflect a workforce bound by ITAR, NDAs, or simply a culture that discourages public commentary, common in defense-adjacent space firms. It may also reflect a workforce that has not yet turned over enough to generate a review corpus. "How many concurrent flight builds is AIT supporting today?" "What does the handoff between design and production look like on the Star Tracker line?" The answers will reveal more than any aggregated rating.
No attributable quotes from current or former employees exist in the research provided. No tenure distributions, no voluntary-attrition rates, no internal-survey results, no exit-interview themes. The board data shows what Terran Orbital is buying in the labor market; the press data shows what it is delivering to customers. The lived experience between those two surfaces remains undocumented in public sources.
The Engineer on the Floor
Lockheed builds one school-bus satellite every 5 to 10 years. Terran Orbital ships a bus every five weeks. That cadence does not come from heroics — it comes from a manufacturing line where the FPGA engineer, the flight software lead, and the mission assurance manager stand at the same bench, argue the same trade, and own the same schedule. The CAPSTONE bus survived a propulsion anomaly mid-transit because the team treated it as a debugging session with a hard deadline, not a reason to slip the mission. The NGSD subsystems will slot into Vanguard and Sentinel cores because Terran proved it can qualify hardware to a prime contractor's timeline, not just its own.
The hiring board makes the bargain explicit: staff-level pay, Irvine-lab presence, IV&V rigor, and the autonomy to call a "quick 180" when a decision proves wrong. What the board cannot show is whether the culture Krauss is building (risk mitigation over risk avoidance, throughput over headcount) holds when the backlog deepens and the primes come calling for the same talent. The next bus is already in integration. The one after that is in design. The engineers who stay will be the ones who prefer the bench to the briefing room.
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.