<candidate>The Aerospace Corporation Pays Up to $278,260 for RF Payload Analysts — and Competes Directly with SpaceX and Anduril for the Same Engineers</candidate>

Why an FFRDC Is Competing with SpaceX and Anduril for the Same Engineers

The job postings tell the story before any press release does. In the past seven days, SpaceX added 100 roles to the market: RF engineers, Starlink manufacturing leads, and Starshield materials specialists. Anduril Industries added 224, spanning counter-intrusion program managers and sentry-systems engineers. Boeing posted 39 more, including a spacecraft harness engineer at its Millennium Space Systems subsidiary in El Segundo. All of them need people who understand how radio-frequency systems behave in orbit.

The Aerospace Corporation needs the same people.

That fact alone would have surprised most engineers five years ago. The Aerospace Corp — the federally funded research and development center chartered exclusively to the U.S. space enterprise — occupied a niche few considered. It sat in the room during acquisition reviews, ran independent technical assessments, and advised the Space Force and NRO on whether a program's architecture would survive contact with reality. The work was essential and largely invisible.

Now it's hiring competitively. The corporation's careers page frames the pitch in mission language: "We don't just support missions; we help define them." But the subtext is workforce strategy. Aerospace operates the only FFRDC devoted entirely to space, and its technical staff spans every discipline of space-related science and engineering, including the RF payload analysis at the center of next-generation military satellite communications, radar payloads, and multi-domain sensing.

What makes this a genuine talent competition rather than parallel hiring is the specificity of the overlap. SpaceX's Starshield program builds proliferated LEO constellations for defense customers. Anduril builds autonomous sensing and counter-intrusion systems that increasingly integrate with satellite downlinks. Both need RF payload analysts who can model link budgets, evaluate antenna performance, and assess electromagnetic interference across contested spectrum. Aerospace Corp needs those same analysts, not to build the hardware, but to provide the independent technical judgment about whether the hardware will work. The skill set is nearly identical.

Zero G Talent's board data quantifies the scale: SpaceX offers $135,000–$190,000 for a lead supplier development engineer on Starlink. Anduril's staff technical program manager for counter-intrusion work tops out at $253,000. Aerospace Corp's compensation structure, shaped by federal pay scales and FFRDC cost models, can't always match those numbers dollar for dollar, which makes the competition asymmetric but real. The corporation counters with clearance stability, mission access, and a career arc that doesn't depend on the next funding round.

The significance goes beyond one employer's hiring cycle. Aerospace Corp's expansion reflects a structural shift: the U.S. government's most trusted technical advisory body is growing its in-house RF payload workforce at the exact moment that SpaceX, Anduril, and Boeing are scaling theirs. The same engineering talent pool is being pulled in three directions — build, advise, and integrate — and the FFRDC, long the quiet player, is now competing openly for the same résumés.

What the Job Postings Actually Require

The postings for RF payload analysts at The Aerospace Corporation read differently from anything you'll find at SpaceX or Anduril. Where those companies want you to build and ship hardware fast, Aerospace Corp wants you to evaluate whether someone else's hardware will actually work (and survive) in the specific threat environment the U.S. military is planning for.

The core technical ask is RF payload design and performance analysis for national-security space programs. That means understanding how radar, communications, and sensing payloads behave once they're in orbit, not just on a test bench. The LinkedIn posting for the senior RF analyst role puts it directly: the job requires "engineering judgment, deep knowledge of current technology, and understanding of national systems to influence critical decisions on RF payload design and performance." This isn't a role where you optimize a single subsystem in isolation. You're assessing how an entire payload fits into a larger architecture of satellites, ground stations, and cyber infrastructure.

The clearance requirement is the first filter. These positions sit inside an FFRDC that supports classified defense and intelligence programs. A Secret clearance is the baseline for many postings; some roles require TS/SCI. That clearance gate alone shrinks the applicant pool dramatically, and it's one reason Aerospace Corp competes for the same RF engineering talent as SpaceX's Starshield and Anduril's counter-intrusion teams, even though the day-to-day work looks nothing alike.

What makes the role distinct from a private-sector RF engineering job is the advisory function. Aerospace Corp doesn't manufacture satellites. It provides the independent technical oversight that the Space Force, NRO, and allied programs rely on to avoid costly mistakes. An RF payload analyst there might evaluate a contractor's antenna design, model link budgets for a new military communications constellation, or assess whether a radar payload can meet its performance specs under jamming conditions. The work spans satellite, launch, ground, and cyber systems, a scope that most private-sector RF roles, focused on a single product line, don't come close to matching.

The postings also signal a preference for engineers who can operate across the full program lifecycle, from early design review through on-orbit performance assessment. That breadth is unusual. At a company like Boeing's Millennium Space Systems, an RF engineer might spend years on one spacecraft bus. At Aerospace Corp, the same engineer could touch half a dozen programs in a single year, each with different payload architectures and mission requirements.

The Programs Driving Demand

The Aerospace Corporation's RF payload analyst hiring surge doesn't exist in a vacuum. It maps directly to a wave of next-generation satellite programs (U.S. military, intelligence, and allied) that need exactly the kind of independent technical evaluation an FFRDC is built to provide.

The most visible driver is the Space Force's MILNET constellation. Under a contract administered by the National Reconnaissance Office, SpaceX is building roughly 480 Starshield satellites to provide high-bandwidth, resilient military communications, a dedicated architecture separate from the 7,000-plus Starlink satellites already in orbit. SpaceX is prime contractor for design, manufacturing, and day-to-day operations, with Space Force's Delta 8 embedding a mission director to oversee operations. The scale alone creates demand for payload analysts who can evaluate RF performance, spectrum use, and bus-payload integration across a production run of that size, work that falls squarely within Aerospace Corp's role as the Space Force's FFRDC.

MILNET also signals a broader shift in how the Pentagon thinks about satellite communications. Ars Technica reported that the constellation sits at the center of a sensor-to-shooter targeting architecture, meaning the RF payloads aren't just relay nodes; they're part of a kill chain. That raises the technical bar for anyone analyzing these systems. Payload analysts need to understand not just link budgets and antenna patterns but how RF performance degrades under jamming, how waveforms hold up in contested spectrum, and how a 480-satellite mesh behaves when individual nodes go dark.

The common thread across MILNET and similar programs is that none of them can afford to treat RF payload evaluation as an afterthought. A communications satellite with a flawed payload is a half-billion-dollar antenna that doesn't work. A radar satellite with miscalibrated RF returns useless imagery. The Aerospace Corporation exists to catch those failures before launch, and the current hiring wave suggests the pipeline of programs needing that scrutiny is growing faster than the existing workforce can handle.

Two Campuses, Two Mission Profiles

The corporation's RF payload analyst roles don't just list two locations; they map onto two distinct national-security ecosystems. Chantilly, Virginia, and El Segundo, California, function as separate talent pipelines feeding different corners of the space enterprise, and the difference matters for anyone deciding where to plant a career.

Chantilly sits inside the National Capital Region's dense cluster of defense and intelligence agencies. The campus is a short drive from the National Reconnaissance Office's headquarters, the Pentagon, and the constellation of SETA contractors and program offices that manage military satellite procurement. The job postings reflect this: the Mission Engineering Specialist role based in Chantilly calls for experience with DoD, NSS, NASA, NOAA, and NNSA customers, and the posting explicitly requires a TS/SCI clearance, the baseline credential for work touching classified satellite programs. The Enterprise Effects Division and Mission Engineering Department, both anchored in Chantilly, focus on end-to-end mission threads across the national security space enterprise, which means analysts there are embedded in the architecture and requirements phase of programs before hardware is built.

The El Segundo campus operates in a different orbit — literally and organizationally. Located in the heart of the Los Angeles aerospace corridor, El Segundo places Aerospace Corp engineers alongside the production lines and program offices of prime contractors. The El Segundo campus also hosts the SpaceWERX Technology Readiness Level bootcamp lab, a partnership with the Space Force's innovation arm that focuses on guiding emerging technologies from lab to operational deployment. That's a fundamentally different workflow from Chantilly's mission-architecture focus: El Segundo is closer to the hardware, the test ranges, and the transition-to-operations phase.

The LinkedIn job data reinforces the split. Chantilly postings skew toward mission engineering, systems integration, and software-defined capabilities. The Associate Principal Director role for the Information Systems and Cyber Division, based in Chantilly, is explicitly framed around expanding Aerospace's role with East Coast national security customers and building AI-enabled mission solutions. El Segundo's open roles, by contrast, cluster around payload engineering, production support, and the kind of technical assessment that happens when satellites are being built and tested rather than designed on a whiteboard.

For an RF payload analyst, the choice of campus shapes the work. Chantilly means requirements analysis, architecture reviews, and advising program offices on what the next generation of military communications satellites should look like. El Segundo means evaluating vendor payload designs, supporting integration and test campaigns, and working the boundary between Aerospace Corp's independent assessment role and the primes who are actually building the spacecraft. Both paths require the same core RF expertise, but the day-to-day context (and the professional network you build) diverges sharply.

How Boeing's Millennium Space Scales — and Why Aerospace Corp Is the Hidden Complement

Boeing is targeting 26 satellite deliveries in 2026. Kay Sears, vice president and general manager of Boeing Space, Intelligence & Weapons Systems, stated the number as a production commitment, not a forecast, backed by new investment in common products, repeatable manufacturing, and tighter integration with subsidiary Millennium Space Systems. The scale of the ramp matters because it creates a class of technical risk that only an independent FFRDC is positioned to absorb.

Millennium, which Boeing acquired in 2018, builds small satellite constellations ranging from 50 kg to over 3,000 kg for national security and defense missions. The new Resolute platform — a mid-class spacecraft designed for communications, sensing, and multi-orbit missions — sits between traditional smallsats and the large, multi-year programs that Boeing has built for decades. Tony Gingiss, Millennium's CEO, framed the effort as building "production depth, common architecture and capacity to scale with demand." The company is expanding into mission areas that need more capability than a cubesat can deliver but can't wait the five to seven years a flagship-class program demands.

That middle ground is exactly where The Aerospace Corporation's RF payload analysts come in. Boeing and Millennium are combining Boeing's payload and mission expertise with Millennium's rapid production lines. But when a defense customer needs an independent technical assessment of whether a Resolute-class radar payload will perform as specified across orbital regimes, or whether a scaled production line is cutting corners on RF performance, the program office doesn't ask the builder to grade its own homework. It asks Aerospace Corp.

This is the structural relationship that most job seekers in frontier tech never see. SpaceX and Anduril compete for the same RF engineers that Aerospace Corp hires, but the roles are fundamentally different. At SpaceX, an RF engineer designs and ships product. At Aerospace Corp, an RF payload analyst evaluates whether someone else's product will work — and whether the government is buying what it thinks it's buying. The Aerospace Corporation has provided specifications and standards leadership for the space industry for over 25 years, working directly with program offices to define mission assurance baselines. That institutional role doesn't scale with production volume, but it scales with production complexity. Every new satellite platform Boeing and Millennium bring to market creates another stream of independent oversight work.

The geographic overlap is direct. Millennium operates out of El Segundo, California, one of the two campuses where Aerospace Corp is actively hiring RF payload analysts. Boeing's own job board shows 39 roles added in the past week, including spacecraft harness engineers and network designers at Millennium's El Segundo facility. Aerospace Corp's Chantilly campus, meanwhile, sits inside the Beltway customer base that funds and oversees the programs Millennium is building for. The two organizations are not competing for the same work. They occupy adjacent positions in the same pipeline: one builds, the other verifies.

Salary, Clearance, and Career Path — An Underrated Frontier Career

The numbers tell a story most RF engineers outside the defense world never see.

Those figures sit comfortably alongside what SpaceX and Anduril offer for comparable cleared roles, but the comparison misses the point. The compensation structure at an FFRDC is built on a different foundation.

Aerospace Corp's 401(k) plan alone is worth pausing on. The company contributes 8%, 10%, or 12% of eligible compensation based on years of service, with employees fully vested from day one. That's not a match; it's a guaranteed contribution on top of whatever you defer. Layer on comprehensive health plans, paid leave, flexible spending accounts, variable pay for exceptional contributions, and education assistance, and the total package starts to look less like a government-adjacent salary and more like a deliberate retention strategy for people who could walk to a prime tomorrow.

The clearance pipeline is the other half of the equation. Both postings require an active Top Secret clearance with SCI access. That's not a nice-to-have; it's a prerequisite. The polygraph requirement on the senior role narrows the field further. Engineers who already hold that access are expensive to replace and hard to poach, which is partly why Aerospace Corp pays to keep them. For someone early in their career who can obtain the clearance, the ROI compounds over decades — cleared RF engineers with SIGINT domain expertise are among the most constrained talent pools in the defense sector.

The career trajectory diverges from the private sector in a way that matters after year five. At Aerospace Corp, the postings explicitly call out mentoring junior engineers, shepherding payload designs from requirements through end-of-life, and serving as a trusted technical advisor during program direction decisions. That's not a management track; it's a technical authority track, the kind that lets a senior engineer shape national-security satellite architecture without leaving the engineering work they trained for. Glassdoor data shows meaningful headroom for advancement across the enterprise.

The trade-off is real: on-site work in Chantilly, occasional domestic travel, and the pace of government program timelines rather than a startup's sprint cycles. But for an RF engineer who wants to work on SIGINT payloads, maritime surveillance systems, and electronic warfare applications at the classification level where the actual decisions get made, and get paid to do it without the equity-lottery risk of a venture-backed defense startup, this is the career path that doesn't show up on most job boards.

FFRDCs: The Silent Backbone of the Space Talent Ecosystem

The Aerospace Corporation's hiring surge is not an isolated recruiting story. It signals something structural: the U.S. government's dependence on FFRDCs as the stable, mission-critical talent pipeline that the private sector cannot replicate, and the pressure that model is now under.

FFRDCs exist because federal agencies determined, going back to World War II, that certain research and engineering needs could not be met effectively by government employees or private contractors alone. Congress codified the model in the Federal Acquisition Regulation, requiring that FFRDCs operate with independence, avoid organizational conflicts of interest, and maintain long-term strategic relationships with their sponsoring agencies, typically five-year contracts renewed in five-year increments. The design was deliberate: stability and continuity to attract people who would not otherwise work for the government.

That model now consumes over $31 billion in annual federal R&D spending across 41 centers, according to the Congressional Research Service's May 2026 report. The Department of Defense alone sponsors 10 FFRDCs, including The Aerospace Corporation, which it classifies as a systems engineering and integration center. The Department of Energy runs 16. The share of all federally financed R&D performed by FFRDCs has climbed from 5 percent in 1953 to 17 percent in FY2024.

The workforce numbers tell the same story. DOD FFRDCs are capped at 6,053 staff technical equivalents by congressional appropriations language, a ceiling that has held roughly flat for years even as demand from sponsoring agencies consistently exceeds it. The Aerospace Corporation, as the Air Force's primary systems engineering FFRDC, sits at the center of that constraint: it cannot scale headcount the way SpaceX or Anduril can, yet the complexity of the programs it supports keeps growing.

This is where the talent war gets interesting. The private sector (SpaceX adding over 100 roles in a single week, Anduril listing 224) competes on speed, equity, and compensation visibility. FFRDCs compete on something else entirely: access to classified programs, long-term mission continuity, and the ability to work on problems that do not have a commercial market. The Aerospace Corporation's new "government furnished talent" program, announced by CEO Tanya Pemberton, is an explicit acknowledgment of this dynamic — it offers private companies access to Aerospace Corp's people, facilities, and laboratory infrastructure, effectively making the FFRDC's talent a shared resource for the broader space industrial base.

The structural tension is real. A 2025 QEM Network white paper argued that the current FFRDC model is "outdated" and underutilized in domestic talent production, noting that the top 100 research universities (which receive roughly 45 percent of federal R&D obligations) produce only 23 percent of American S&E degrees. FFRDCs, the paper argued, could be redesigned as workforce development engines, not just research centers. Congress has pushed in the same direction: since 1993, defense appropriations bills have prohibited DOD from establishing new FFRDCs and imposed annual staffing ceilings, a sign that lawmakers see the model as necessary but want tighter control over its growth.

Meanwhile, the broader talent pipeline is under strain. The aerospace and defense sector faces an 8 percent vacancy rate, with engineering and cybersecurity roles going unfilled at even higher rates, according to Talenbrium's 2025 benchmark report. The National Science Foundation's data on federal R&D obligations per student shows that R1 universities receive roughly $10,000 per student in federal R&D funding, nearly double the $5,500 average across all institutions, concentrating resources at a small number of schools while the majority of domestic S&E talent graduates from institutions with far less federal investment.

The Aerospace Corporation's RF payload analyst hiring is a microcosm of this larger system. The roles require clearances that take months to obtain, domain knowledge that takes years to build, and a tolerance for the slower pace of government-funded work that most startups cannot match. The people who fill these roles tend to stay — FFRDC retention rates benefit from the same long-term contract structure that defines the centers themselves. That stability is the product. It is also the bottleneck.

The Aerospace Corporation employs more than 4,800 people across the enterprise. Every new satellite platform that enters production, from MILNET to Resolute, adds another stream of oversight work that only an FFRDC can perform. The hiring surge is the visible edge of a system under pressure it was not designed to absorb.

Working in space? Zero G Talent tracks the openings: browse space jobs, openings at SpaceX, Anduril Industries and Boeing, and the people building the field.