AEOS (Above Earth Operating System) is Axiom Space’s orbital compute orchestration platform—a federated software layer that manages distributed spacecraft compute nodes across LEO and beyond. AEOS enables autonomous workload scheduling, deterministic state reconciliation across intermittently connected domains, and ISL-aware (inter-satellite link) DAG execution across GPU-accelerated flight hardware. The platform treats optical inter-satellite links as first-class schedulable resources alongside compute, power, and thermal budgets, enabling distributed AI inference, secure data processing, and resilient space-based computing for defense, intelligence, and commercial customers. AEOS is architected around patent-pending federated autonomous control planes that allow each orbital node to operate independently during connectivity gaps and converge deterministically upon reconnection—a foundational capability for sovereign, cyber-resilient space infrastructure. Axiom Space fosters a work environment inclusive of all perspectives. We are the pioneers of commercial space, leading the transformation of low-Earth orbit into a global space marketplace. Our mission-driven team is seeking a bold and dynamic Chief Engineer who is fueled by high ownership, execution horsepower, growth mindset, and driven to understand our world, science/technology, and life itself, for the benefit of all on Earth and beyond. POSITION SUMMARY The Chief Engineer’s job is to integrate these domains into a working system. You own the architecture. You own the sprint. You own the coordination between AEOS’s engineers and QDSC’s crypto specialists. You translate between the FPGA engineer’s RTL, the orbital engineer’s contact window models, the platform engineer’s distributed systems code, and QDSC’s key derivation algorithms — and you make sure they all converge into a system that encrypts optical inter-satellite links at 10 Gbps Built secure embedded systems for defense or space — not just software, not just hardware, but the integration of both under real constraints (SWaP, radiation, operational tempo). Shipped something that flew, or something that went through FIPS/CC validation, or ideally both. Thinks in system architecture, not just code or RTL. Doesn’t need to design a cryptographic algorithm — QDSC does that. But you need to understand what a FIPS 140-3 module boundary is, why key zeroization matters, what an AEAD cipher does, and how a key pre-distribution system differs from PKI. Need to review QDSC’s integration spec and catches the assumptions that don’t hold in a space environment.
Stand Out From the Crowd
Upload your resume and get instant feedback on how well it matches this job.
Job Type
Full-time
Career Level
Senior