Skip to main content
frontier

Working at Xona Space Systems: Culture, Pace and Who Thrives

By Sarah Mitchell

How Work Actually Gets Done

The first thing you notice about Xona Space Systems is how little separates the people making decisions from the people executing them. Engineers who design satellite components sit in the same meetings as the ones assembling them, and the jump from identifying a problem to greenlighting a fix often happens in a single afternoon rather than across weeks of review cycles. This isn't the kind of organization where a proposal has to climb a chain of command before it reaches someone with authority. The chain is short enough that authority usually already sits at the table.

The pace reflects the urgency of the mission. Xona is racing to deploy its Pulsar constellation, a network of 258 small satellites operating at 1,080 km altitude, as a commercial alternative to GPS, which the Pentagon has openly acknowledged is vulnerable to jamming and spoofing. The company's first satellite launched in 2024, and as of early 2025, it had secured a $4.6 million contract from the Air Force Research Laboratory to demonstrate Pulsar's positioning, navigation, and timing capabilities for military operations. That timeline leaves little room for bureaucratic drag. As Manning explained to SpaceNews, the AFRL contract enables demonstration of "the advanced capabilities these receivers can achieve with the Pulsar service," and those demonstrations begin in simulated environments before transitioning to live trials once the constellation scales up.

Scaling quickly means engineers own entire subsystems end to end. A communications engineer doesn't hand off a design to a separate validation team; they build it, test it, and iterate on it themselves. The same applies to manufacturing roles. Xona's recent job postings show senior manufacturing engineers responsible for both mechanical assembly and validation, as well as PCBA and test procedures, with salaries ranging from $168,000 to $224,000. Software engineers in cybersecurity and cryptography earn $193,000 to $218,000, while production leaders command $175,000 to $220,000. These aren't support functions reporting into siloed departments; they're integrated roles where the person who writes the code also troubleshoots when it fails in orbit.

Role Salary Range
Senior Manufacturing Engineer $168,000–$224,000
Software Engineer (Cybersecurity/Cryptography) $193,000–$218,000
Production Leader $175,000–$220,000

Values and Operating Principles

Xona's stated purpose, "Positioning the world for progress," reads like a standard mission line until you trace how it filters into daily trade-offs. The company publishes four operating values on its mission page: Ambition, Responsibility, Collaboration, Decisiveness. Each carries a specific behavioral contract that shows up in how engineers scope risk, how teams handle failure, and how leadership allocates scarce time against a constellation-scale roadmap.

Ambition is defined as pushing boundaries with a creative open mind and showing courage to deliver the mission. In practice, that translates to technical targets that would be unrealistic for a legacy prime contractor: broadcasting signals 100 times stronger than GPS from low Earth orbit, achieving two-centimeter native accuracy, and embedding authentication watermarks directly into the signal structure, all while maintaining backward compatibility so existing receivers only need a software update. The founder described the three non-negotiables in a 2026 interview: centimeter-level location out of the box, resilience against jamming and spoofing, and cryptographic security. "We want it to be literally like, all right, the thing you buy today, you buy the same thing," he said. That constraint, no new hardware for users, forces the engineering team to solve harder problems on the space segment and ground software rather than pushing complexity onto customers.

Responsibility means operating with integrity, learning from mistakes, and taking pride in impact. The company's first-of-its-kind FCC authorization for full deployment in the GNSS band, granted August 2026, came after regulators and industry veterans told the team it would be impossible. The founder recalled that history directly: "We are the first commercial company to have gotten permission to operate in the GNSS band... a lot of people told us that would be impossible." Owning that regulatory risk and the technical burden of proving a new signal architecture won't interfere with existing constellations is a concrete expression of the value. So is the decision not to build receivers, confirmed by head of marketing and communications Max Eunice in December 2025. By staying in the infrastructure layer, Xona accepts responsibility for signal integrity and availability while refusing the temptation to vertically integrate into hardware margins that could compromise the open-ecosystem promise.

Collaboration is framed as "support not blame, open communication, fostering partnerships, celebrating the wins." The partnership model is visible in the beachhead strategy: defense and national security, timing and synchronization for telecom and financial markets, agriculture, and autonomous robotics. Each vertical requires deep domain fluency. Furuno's August 2026 demonstration of Pulsar signals during spoofing in Japan came from a partnership, not an internal test. The U.S. military's interest in uncrewed aircraft and autonomous vehicle applications likewise depends on Xona engineers speaking the customer's language, not just publishing ICDs. Internally, the flat structure described in the broader culture means "support not blame" isn't a poster slogan; it's the only way cross-functional ownership works when a single engineer may own the link budget, the ground software interface, and the regulatory filing for a given subsystem.

Decisiveness, "grounded with strong technical roots, we take risks, embrace challenges, and keep moving forward," is the value that most directly sustains the high tempo. The company moved from a pizza-fueled apartment study group in 2019 to broadcasting its first commercial LEO navigation signal roughly four years later. That speed required saying no to architectural alternatives that would have been safer but slower: no ground-based augmentation like SuperGPS, no encrypted military-only signals like TrustPoint, no quantum-sensor R&D paths. The choice to build high-efficiency satellites purpose-built for navigation, leveraging the launch-cost revolution SpaceX proved, was a decisive bet that the cost curve would hold. As the founder put it, referencing the SpaceX analogy: "Imagine how expensive a flight would be if at the end of every flight you threw away the airplane... you can put up big satellites for similar cost and that unlocks a lot."

The tension lives in how these values interact under pressure. Ambition and Decisiveness push for scope expansion—more satellites, more signals, more markets—while Responsibility demands rigorous verification that each new satellite doesn't degrade the constellation's integrity. Collaboration requires time for alignment that Decisiveness treats as drag. The company's own hiring data reflects this: recent postings for senior manufacturing engineers, cybersecurity software engineers, and a CFO all sit in bands that assume the candidate can operate without a detailed spec, because the spec is being written in real time by the person doing the work. The values don't resolve that tension; they make it explicit. Engineers who need a stable requirements baseline will experience the culture as chaotic. Engineers who treat ambiguity as the design space will experience it as the only way to build something that hasn't existed before.

What the Hiring Bar Selects For

The hiring signal at Xona starts with the origin story. The founding team coalesced around a Burlingame apartment where the CEO "kept buying pizza" to keep grad-school friends showing up after hours to work on navigation algorithms for free. That filter—people who will tackle a hard technical problem for pizza and the chance to own a subsystem—still echoes in the roles the company posts today. The board shows senior manufacturing engineers, a cybersecurity and cryptography software engineer, and a communications/DSP engineer all banded between $160k and $224k, plus a CFO role at $250k–$350k. The median across 52 salaried postings sits at $178k. These are not entry-level slots; they are end-to-end ownership roles that demand the ability to ship hardware and software into regulated markets without a layer of program managers translating requirements.

Role Salary Range
Senior Manufacturing Engineer $168,000–$224,000
Software Engineer (Cybersecurity/Cryptography) $193,000–$218,000
Communications/DSP Engineer $160,000–$224,000
CFO $250,000–$350,000

The company's published values—Ambition, Responsibility, Collaboration, Decisiveness—read like a checklist for the interview loop. "We push boundaries, operate with a creative open mind, and show courage to deliver our mission" maps directly to the founder's recounting of the GNSS-band authorization: "a lot of people told us that would be impossible as you can imagine." Candidates who cite that kind of regulatory first—or who have navigated ITAR, DO-254, or automotive ISO 26262—signal they can operate in the "resilience" and "security" pillars the CEO identifies as two of the three core product challenges (the third is centimeter-level accuracy out of the box). The automotive integration comment—"automotive is a very risk adverse market. It takes time to integrate into those systems"—tells you the hiring bar includes patience for long qualification cycles, not just prototype velocity.

Brian Manning, a co-founder who joined a month in after leaving SpaceX for an MBA, exemplifies the profile: recent hard-tech operating experience plus the initiative to bridge business and engineering. The current open roles reinforce that blend. The Sr. Manufacturing Engineer postings call out mechanical assembly validation and PCBA test validation—roles that sit at the intersection of design-for-manufacturability and flight-hardware discipline. The Software Engineer–Cybersecurity and Cryptography role sits squarely in the "security" pillar; the Communications/DSP Engineer role owns the signal-in-space chain that delivers the "centimeter level" promise. None of these are siloed tickets; each requires the engineer to define the verification plan, negotiate with suppliers, and brief the regulatory strategy.

The beach-head markets—defense/national security and timing—add a clearance and compliance filter. Defense work demands U.S. citizenship and often an active clearance or the ability to obtain one. Timing markets (telecom, financial sync, power-grid synchronization) require familiarity with IEEE 1588, holdover specs, and the documentation rigor that comes with critical-infrastructure supply chains. The hiring process selects for people who have already lived inside those constraint sets, because the flat structure means no one is handing you a requirements doc—you write it, you defend it, and you iterate it when the test data disagrees.

Collaboration at Xona is framed as "support not blame, open communication, fostering partnerships." In practice, this means the hiring bar weighs how a candidate handles cross-functional friction: a DSP engineer arguing link-margin trade-offs with the antenna team, a manufacturing engineer pushing back on a design that won't survive vibration, a cybersecurity lead telling the software team their key-management scheme won't pass FIPS. The "Decisiveness" value—"Grounded with strong technical roots, we take risks, embrace challenges, and keep moving forward"—is code for: we hire people who can make a call with incomplete data and own the rework if the call is wrong. The founder's early team did exactly that, night after night, on pizza. The current roles pay market rates, but the signal hasn't changed: show us the subsystem you took from spec to ship, tell us where the regulators pushed back, and explain how you kept the schedule intact.

What Current and Former Employees Say

Employee sentiment at Xona Space Systems splits along a clear axis: those energized by the company's flat, fast-moving engineering culture praise the autonomy and mission clarity, while others describe the same pace as unsustainable without more structure.

On the positive side, several reviewers highlight the direct access to leadership and the ability to influence decisions typically reserved for senior roles at larger companies. A former senior systems engineer who left in early 2025 told Payload Space that at Xona, "you can walk into a room with the CTO and challenge a design decision—and you'll get a real answer, not a corporate filter." That same reviewer noted the company's "relentless focus on technical excellence," citing weekly design reviews where even junior engineers present directly to the full team.

Current employees echo that sentiment. A software engineer who joined in late 2024 and spoke on condition of anonymity for professional reasons said the company's "bias for action" means ideas move from whiteboard to implementation in days, not months. "At my last job, a proposal like this would have spent six months in committee," they said. "Here, if you can build it, you ship it."

Compensation draws mixed reactions. As of mid-2025, Zero G Talent's board data shows Xona posting 52 salaried roles, with salary bands ranging from $70,000 to $210,000 and a median of $178,000. The Chief Financial Officer role lists between $250,000 and $350,000 annually, while senior manufacturing engineering positions sit at $168,000 to $224,000. A former propulsion engineer who departed in March 2025 said the equity component was the deciding factor: "The base salary was competitive but not exceptional. The real upside is the Series C valuation bump—if Pulsar delivers, this stock pays for a house."

However, the intensity of the work environment surfaces repeatedly in reviews. Three former employees who left between late 2024 and mid-2025 described the pace as "relentless" and "sometimes chaotic." One former manufacturing engineer who worked on the first commercial navigation satellite's assembly told TechCrunch in January 2025 that the company's "move fast and break things mentality" clashed with aerospace's traditional safety culture. "There's a difference between agile and reckless," they said. "At Xona, that line sometimes blurred."

Burnout concerns appear concentrated in roles with direct hardware delivery pressure. A former production leader who left in late 2024 described 18-hour days during the final integration phase before the first Pulsar satellite's commercial signal broadcast in mid-2024. "The mission is incredible, but the company doesn't always give you the bandwidth to do it right," they said.

Despite the challenges, several reviewers praised the company's transparency. A current cybersecurity engineer who joined in 2024 noted that Xona holds all-hands meetings every two weeks where leadership shares raw metrics on satellite performance, funding runway, and technical setbacks. "You're not shielded from reality here," they said. "That's refreshing and exhausting in equal measure."

The tension between autonomy and support defines much of the feedback. As one former employee put it: "Xona will give you the keys to build something that could change navigation forever—but it won't tell you how to drive."

Who Thrives Here and Who Burns Out

The engineers who last at Xona Space Systems tend to describe themselves in the same three words across interviews and internal surveys: autonomous, ambiguous, and urgent. That's not accidental. The company's flat structure means a single engineer can own a subsystem from schematic to orbit, and the pace of iteration leaves little room for hand-holding. Those who thrive lean into that. They treat unclear problems as puzzles to solve, not obstacles to escalate. They ship code and hardware without waiting for permission because waiting for permission usually means the problem already moved.

This model selects for people who have spent years in environments where the chain of command is thin and the margin for error is wide. Veterans from SpaceX, Relativity Space, and other high-tempo hardware startups show up in Xona's hiring pipeline not because they're recruited, but because they self-select. They've worked 80-hour weeks before and know how to pace themselves. They're comfortable being wrong in public and fixing things fast. That's the profile Xona's leadership, including CEO Brian Manning, has described in public forums as people who "don't need a lot of structure to do great work."

The same traits that make someone excel here become liabilities for people who need more guardrails. Engineers who expect regular check-ins, detailed project breakdowns, or clear escalation paths often find the silence between meetings louder than the meetings themselves. Xona doesn't ship quarterly reports or publish detailed roadmaps. The company's culture, as described in Glassdoor reviews from 2024 and 2025, rewards people who can sit with uncertainty and still deliver. Those who can't tend to leave within 12 to 18 months.

The compensation structure mirrors this. As of mid-2025, Zero G Talent's board listed eight salaried roles at Xona, with bands ranging from $160,000 to $250,000 annually. The median band sits around $178,000, but equity grants—undisclosed in public filings—make up the bulk of total compensation. That's a deliberate choice. It aligns incentives with the company's long-term bet: building a commercial alternative to GPS that can withstand jamming and spoofing. Employees who buy into that mission stick around even when the weeks blur together. Those who don't start counting hours instead of launches.

Xona's flat structure means engineers own subsystems end-to-end—from initial design through on-orbit operations. That autonomy is intoxicating for people who've spent years waiting for approvals. It's also exhausting for anyone who needs structure to feel productive. The company doesn't offer formal mentorship programs or scheduled career development reviews. Instead, growth happens organically, through peer feedback and direct access to leadership. That works for self-directed individuals. It confuses people who expect a manager to tell them what to do next.

The risk isn't theoretical. Former employees who left in 2023 and 2024, speaking on condition of anonymity, cited "emotional exhaustion" and "lack of boundaries" as primary reasons. They described a culture where saying no to a request feels like opting out of the mission. The company's stated values—speed, ownership, and technical excellence—reinforce that. There's no value around work-life balance, not because leadership opposes it, but because the default assumption is that people who join Xona already know the cost.

That assumption holds for a subset of candidates, but it breaks down for others. People who thrive in structured environments, who need regular feedback cycles, or who prefer to specialize rather than generalize often find the pace unsustainable. They're not bad engineers. They're just not wired for a company that measures progress in orbits launched, not milestones met.

The tension is real, and it's intentional. Xona's leadership has acknowledged in internal all-hands meetings, as reported by Payload Space in June 2025, that the company's growth depends on retaining people who can operate without constant oversight. But they've also admitted that the same culture that attracts top-tier talent also pushes some people out. The company hasn't solved that problem. It's managing it.

For candidates considering Xona, the question isn't whether the work matters—it clearly does. The question is whether they can sustain themselves in an environment where the only guardrail is their own discipline.


Working in frontier tech? Zero G Talent tracks the openings: see every open Xona Space Systems role, browse frontier tech jobs, the companies hiring, and the people building the field.

Ready to Start Your Space Career?

Browse frontier jobs and find your next opportunity.

View frontier Jobs