<div class="content-intro">At Relativity Space, we’re building rockets to serve today’s needs and tomorrow’s breakthroughs. Our Terran R vehicle will deliver customer payloads to orbit, meeting the growing demand for launch capacity. But that’s just the start. Achieving commercial success with Terran R will unlock new opportunities to advance science, exploration, and innovation, pioneering progress that reaches beyond the known. Joining Relativity means becoming part of something where autonomy, ownership, and impact exist at every level. Here, you're not just executing tasks; you're solving problems that haven’t been solved before, helping develop a rocket, a factory, and a business from the ground up. Whether you’re in propulsion, manufacturing, software, avionics, or a corporate function, you’ll collaborate across teams, shape decisions, and see your work come to life in record time. Relativity is a place where creativity and technical rigor go hand in hand, and your voice will help define the stories we’re writing together. Now is a unique moment in time where it’s early enough to leave your mark on the product, the process, and the culture, but far enough along that Terran R is tangible and picking up momentum. The most meaningful work of your career is waiting. Join us.</div>About the Team:  The Interplanetary Sciences Program was established to expand access to scientific exploration across our solar system. Its mission is to make planetary research faster, more affordable, and more capable than ever before by rethinking how science missions are designed, built, and operated. The program aims to enable scientists to send instruments to distant worlds without decades of development or prohibitive costs. By creating a sustainable model for interplanetary exploration, we are transforming space science from an occasional event into a continuous process of discovery that accelerates knowledge, broadens participation, and inspires the next generation of explorers. About the Role: <ul> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Own the complete storage platform software stack for a space-based data center: custom Linux kernel drivers, OpenZFS pool design, NFS data serving, and automated fault recovery, shipping a platform that preserves up to a petabyte of mission data through years of radiation exposure</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Design and implement custom Linux kernel drivers for NVMe fault recovery and GPIO overcurrent protection, working across PCI/PCIe, block layer, and interrupt subsystems to detect and recover from radiation-induced upsets without data loss</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Lead the ZFS pool topology architectural decisions by building quantitative reliability models that balance upset probability, resilver risk, and capacity over a 6+ year mission, then validate through fault injection testing</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Develop the integration layer between NVMe controller reset and ZFS, ensuring that a drive recovering from a transient fault re-enters the storage pool cleanly, bridging driver-level recovery with filesystem-level fault tolerance</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Rapidly prototype on commodity hardware, from first boot through sustained 10 Gbps writes with automated fault recovery, de-risking the architecture before committing to the target platform, then carry the design through integration and launch </li> </ul> About You: <ul> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">5+ years writing Linux kernel code, actual driver development involving PCI/PCIe devices, block storage, or interrupt-driven hardware, with meaningful time spent in kernel space </li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Experience with storage systems: ZFS or other copy-on-write filesystems, RAID, NVMe internals, or high-throughput network storage (e.g., NFS) </li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Depth in one or more: filesystem internals, block layer / device management, or storage protocol implementation </li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Strong working knowledge of OS internals: virtual memory, interrupt context constraints, synchronization primitives, and I/O stack behavior</li> </ul> Nice to haves but not required:   <ul> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Hands-on experience at the driver hardware software boundary: DMA coherency, MMIO semantics, PCIe enumeration, and cache behavior  </li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Strong working knowledge of data structures and systems reasoning for storage (Merkle trees, NVMe submission/completion queue ring buffers, hash tables, radix trees) </li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Experience testing storage systems, including fault injection (PCIe/NVMe resets, error storms), low-level tracing (ftrace/perf/bpftrace), and crash dump analysis (kdump/vmcore) </li> <li style="font-family: arial, helvetica, sans-s

Staff Software Engineer, Storage Platform