Who gets hired and onto which teams
Zero G Talent's live board tracks 809 salaried Blue Origin postings — and every one of the eight captured in the current ingestion window sits at the senior-to-principal tier, clustered in custom silicon and next-generation flight software. This guide links those role families to compensation, maps each step of the selection process, outlines the physical work environments, and distills the characteristics that predict fit, with gaps noted where the research is silent.
Roles the board shows hiring right now
The live feed lists eight salaried Blue Origin postings. All sit at that tier and cluster in two domains: custom silicon (branded "Terawave") and next-generation flight software. The roles, locations, and posted salary bands are:
| Role | Locations | Posted band (USD/year) |
|---|---|---|
| Sr Principal ASIC Design Engineer - Terawave | San Diego, CA; Central Texas; Kent, WA; Bay Area, CA | 308,051 – 431,271 |
| Sr Director NG Software Engineering | Greater Seattle Area (21218 76th Ave S, Kent, WA 98032) | 272,109 – 380,952 |
| Principal Modem PHY IP Design Engineer - Terawave | Central Texas; Bay Area, CA; San Diego, CA | 269,175 – 376,844 |
| Principal Modem PHY IP Design Verification Engineer - Terawave | Central Texas; Bay Area, CA; San Diego, CA | 269,175 – 376,844 |
| Principal System Architect RF SoC - TeraWave | San Diego, CA; Central Texas; Greater Seattle Area; Bay Area, CA | 269,175 – 376,844 |
| Principal ASIC Design Verification Engineer - Terawave | Central Texas; Greater Seattle Area; Los Angeles, CA; Bay Area, CA | 269,175 – 376,844 |
The board's aggregate view across 809 salaried roles shows a company-wide band of roughly $83k–$277k (median $183k). The Terawave and NG Software postings sit at the top of that range, signaling that Blue Origin is investing heavily in in-house radio-frequency and baseband silicon — likely for satellite connectivity and vehicle telemetry — and in the software stack that will fly on New Glenn and follow-on vehicles.
What those titles tell you
Principal and Sr Principal titles repeat across every Terawave listing, and the teams center on deep IC expertise, not junior headcount. When a Principal Modem PHY IP Design Engineer and the verification engineer appear as separate postings, the PHY layer has dedicated design and verification pillars (a structure you see in merchant silicon houses, not typical aerospace avionics groups). The Principal System Architect RF SoC role bridges them, owning the partition between analog/RF, digital baseband, and firmware.
A single Sr Director NG Software Engineering posting at the Kent headquarters — 21218 76th Ave S, Kent, WA 98032, the same address on Blue Origin's facility maps for the New Glenn integration campus — points to a centralized leadership layer for next-gen flight software. The director likely oversees multiple principal engineers and managers. The board has no mid-level or entry-level software postings in this window, which aligns with Blue Origin leadership's public stance that the company hires experienced engineers who can operate with minimal supervision.
Where Blue Origin posts jobs
Four hubs dominate: Greater Seattle (Kent), Central Texas (likely the McGregor test site and nearby design center), San Diego, and the Bay Area. San Diego and the Bay Area are not traditional Blue Origin manufacturing sites. Their presence in every Terawave posting points to a distributed silicon team pulling from the Qualcomm, Intel, and Broadcom talent pools. Central Texas appears in every Terawave posting plus the Sr Director role, which tells you the McGregor campus has expanded beyond test operations into hardware and software development.
What the research leaves out
The board data reveals what roles are open and where, but leaves gaps in educational backgrounds (PhD vs. MS vs. BS) for these principal bands, whether Blue Origin recruits from specific universities or competitors like SpaceX, Kuiper, or defense primes, the internal team names or org-chart relationships (such as whether Terawave sits under Avionics, Communications, or a separate Silicon Engineering org), hiring ratios between IC and management tracks, and any university co-op, new-grad, or early-career programs.
The third-party digest contributes nothing to these questions. If you are targeting these roles, treat the posted bands and locations as the only verified signals; the rest you will need to validate in conversations with current employees or recruiters.
What the pay bands reveal
The posted ranges map directly onto seniority bands visible in the role titles above. The top earner, a Sr Principal ASIC Design Engineer in Terawave, anchors the highest band across San Diego, Central Texas, Kent, and the Bay Area — a ceiling well above the board median, reflecting the scarcity of candidates who can bridge custom silicon design and the demands of satellite communications payloads. The modem PHY roles — design and verification — sit below the Sr Principal tier but well above the board floor, and the same compensation range stretches across four role families (modem PHY design, modem PHY verification, RF SoC architecture, and ASIC verification), suggesting Blue Origin treats these senior IC positions as functionally equivalent in the labor market regardless of whether the work leans toward design or verification.
The sole non-Terawave posting with a published band is the Sr Director NG Software Engineering role, based in Kent, Washington. Its range overlaps with the Terawave Principal bands but falls below the Sr Principal ASIC tier at the top (an ordering that tracks with scope: the Director oversees a software engineering group for New Glenn, while the Sr Principal ASIC role represents the deepest individual technical contribution in a hardware division).
Beyond base salary, Blue Origin's total compensation includes equity and benefits. The company's careers and benefits pages describe an equity package that varies by role level and tenure, and the benefits suite covers health, retirement, and paid leave. However, the specific equity grant sizes, vesting schedules, and benefits dollar values are not itemized in the board data or in the available public postings with enough precision to quote. Candidates should treat the salary ranges above as base compensation and expect total cash and equity to extend those figures further, particularly at the Principal and Director levels, where retention packages in the satellite and launch industries typically include meaningful equity upside.
Cost-of-living differences across those same four regions — the two California hubs, Central Texas, and Greater Seattle — mean that a base salary in Kent, Washington, carries different purchasing power than the same figure in San Jose, California.
A caveat: the board's postings represent only what has appeared on Zero G Talent's board. Blue Origin likely fills additional roles through direct applications, university recruiting, and acquisition-driven hiring that do not surface there.
How the hiring process works and what gets candidates through it
Blue Origin's interview loop runs five to ten weeks (slower than most tech companies, faster than NASA-affiliated roles). Most engineering positions carry ITAR restrictions, so U.S. citizenship or permanent residency is a hard gate for the majority of openings. Background checks are thorough but move quicker than at the traditional defense primes; the company notes that most of its work does not require Secret or Top Secret clearance.
The process has five defined stages. A recruiter screen covers background, role fit, and citizenship status. A hiring manager interview then digs into past projects and motivation for aerospace. A 60-to-90-minute technical phone screen follows. Flight-software candidates write C++ and discuss memory management, RAII, and undefined behavior under real-time deadlines; ground-systems candidates may see Python, Go, Java, or JavaScript instead. The onsite, often a full day, spans five to seven rounds: two to three coding rounds stay C++-heavy for flight software, one to two systems rounds ask you to sketch a real-time or embedded design and defend choices around redundancy, deterministic timing, and graceful degradation, and one domain round tests aerospace fundamentals (propulsion, GNC, avionics) conceptually rather than through code. A final behavioral round centers on "Gradatim Ferociter": how you handle methodical engineering, own failures, and stay motivated through multi-year development arcs.
| Onsite round type | Typical count | Focus |
|---|---|---|
| Coding (C++ for flight software) | 2–3 | Memory management, RAII, undefined behavior, real-time constraints |
| Systems / architecture | 1–2 | Real-time design, redundancy, deterministic timing, fault tolerance |
| Domain (aerospace fundamentals) | 1 | Propulsion, GNC, avionics, or other subsystem specific to the team |
| Behavioral / culture | 1 | Gradatim Ferociter, ownership, long-arc motivation, STAR-structured stories |
A hiring committee reviews the full loop rather than any single interviewer, so consistent signal across every round matters more than one standout performance. The offer is cash-heavy, with base salary plus retention bonuses and no public equity, so negotiation leverage sits on those levers. Blue Origin is private; compensation is cash, retention, and 401(k). There is no equity upside comparable to SpaceX.
Interviewers track every story a candidate tells and enforce a no-repetition rule across rounds. Preparing enough distinct STAR-formatted examples to cover the company's twelve leadership principles (derived from Amazon's framework) without repetition is the practical work that separates those who advance from those who stall. Behavioral questions map to those principles, and candidates who structure answers in Situation, Task, Action, Result format and can pivot their strongest stories across multiple principles perform measurably better. The culture rewards process, redundancy, and analysis over rapid iteration. Engineers who prefer sustainable pace tend to choose Blue Origin; those who want fast iteration cycles gravitate toward SpaceX. New Glenn first-launch and Blue Moon lunar-lander milestones can spike intensity, but work-life balance is generally better here than at companies running on compressed iteration cycles.
Where the work happens
Blue Origin's job postings on our board trace a geographic spread that tells you something specific about where the company concentrates its engineering talent. Roles cluster around four primary regions: Greater Seattle (Kent), Central Texas, the Bay Area, and San Diego, with additional openings in Los Angeles. That distribution matters because each location shapes the kind of work teams do there, from hardware fabrication to systems integration, and the physical environments candidates should expect differ sharply across them.
The Kent, WA headquarters anchors the company's largest footprint. Teams there work on propulsion systems, vehicle assembly, and software that runs across Blue Origin's launch and orbital infrastructure. The physical environment is industrial (large-scale manufacturing floors, clean rooms, and test stands for rocket engines), not a typical office setting. Candidates hired into Kent-heavy roles should expect a workspace that prioritizes hardware access over desk proximity.
Central Texas has emerged as a second major hub. The Terawave roles, in particular, place Central Texas alongside San Diego and Kent, pointing to RF and semiconductor design work in the region. Texas offers lower cost of living than the coastal hubs, which likely supports the company's ability to staff larger engineering teams in semiconductor and communications design. The work environment there is closer to a traditional lab-and-office hybrid (clean-room-adjacent for the chip design work), with collaboration spaces for the cross-functional teams that build communications subsystems.
San Diego and Los Angeles round out the map, with postings spanning both chip design and verification roles. The Bay Area listings span the board's full salary range, though the senior roles sit well above the median. California locations lean into the state's deep pool of semiconductor and systems engineering talent, and the physical environments there tend toward office and lab settings rather than the heavy manufacturing floor work seen in Kent.
The board data provides locations and bands but not detailed site descriptions; the descriptions below follow from the geographic distribution of postings. A candidate evaluating a move to Kent should plan for an industrial, hands-on workspace; someone considering Central Texas should expect a lab-and-office environment built around semiconductor design; and anyone looking at California postings should understand they are entering one of the most competitive talent markets in the country, where the physical setting will likely be a campus-style office or research lab. The locations also suggest that Blue Origin distributes work across sites deliberately: hardware-intensive roles cluster in Washington and Texas, while design and verification roles spread across all four regions, reflecting a model where different parts of a product lifecycle happen in different places.
Who thrives here
The board's postings skew heavily toward senior and principal engineering, with titles like Sr Director NG Software Engineering and Principal System Architect RF SoC. That distribution tells you something about who the company hires and at what stage: these are not entry-level roles. The bulk of the postings call for experienced engineers comfortable working on hardware-software co-design, radio-frequency systems, and modem architectures. A candidate who thrives at Blue Origin, by the evidence on the board, tends to arrive with deep technical specialization and a willingness to work across disciplines that sit at the intersection of hardware and signal processing.
The geographic spread reinforces the point: openings reach Kent, the Bay Area, San Diego, Central Texas, and Los Angeles, all regions with dense aerospace and semiconductor ecosystems. That pattern suggests the company draws talent from clusters where candidates already have exposure to defense, telecommunications, or silicon design cultures. Someone who thrives there likely has experience operating in environments where hardware timelines and software iteration cycles collide daily.
The role families themselves hint at the work style the company rewards. The Terawave-related postings (ASIC design, modem PHY IP, and RF SoC architecture) sit at the boundary of analog design and digital systems engineering. That boundary demands patience for debugging at the physics layer and comfort with ambiguity when a design moves from simulation to silicon. The Principal System Architect RF SoC role implies a position that requires coordinating across teams rather than working in isolation. The person who succeeds in that kind of role typically bridges communication between design, verification, and software groups (someone who can hold a system-level view while still engaging with register-transfer-level detail).
The wide compensation range implies a workforce spanning multiple seniority bands, from junior support roles to principal architects. The spread means the company is not a monolith in its expectations. A junior engineer in a support role and a principal architect in Kent face different demands, and the qualities that predict success in each likely differ. The board does not break down which characteristics correlate with which bands, so any claim beyond "these roles require senior technical expertise" would be speculation.
What the postings do make clear is that Blue Origin hires people who can work in distributed, multi-site teams and who accept that complex hardware projects move slowly by necessity. The concentration of roles in aerospace-adjacent geographies and the emphasis on RF, modem, and silicon design signal a technical culture where deep expertise in those domains matters. If you are evaluating whether you fit, the practical question is whether you have the specialized background these roles require and whether you are comfortable with the pace and ambiguity that come with building hardware for space systems.
The board's data gives you the salary context and role structure to judge that fit. But the deciding test is the one you cannot take from a posting: whether you can walk into a clean-room-adjacent lab in Central Texas or a manufacturing floor in Kent and stay, not for the salary band, but for the slow, deliberate work of building hardware that has to fly.
Working in frontier tech? Zero G Talent tracks the openings: see every open Blue Origin role, browse frontier tech jobs, the companies hiring, and the people building the field.