<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: The storage platform is one of the foundations for accelerating scientific discovery: science instruments write to it, onboard AI reads from it, and the communications subsystems downlink the data on it to Earth.    You will define the storage architecture and build it yourself. This is not a role where someone else hands you a design and you implement it, and it's not a role where you write architecture documents and hand them to someone else to build. You will make the foundational architectural decisions (redundancy topology, replication strategy, failure domain boundaries, consistency guarantees, write-lifecycle management), build and test prototypes on commodity hardware, and then build the low-level systems code that makes those decisions real: storage drivers, filesystem integration, and fault recovery systems that survive radiation upsets across the full mission lifetime. You'll carry the design from proof-of-concept on commodity hardware through integration on flight hardware, validating every architectural assumption with fault injection testing along the way.  <ul> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Own the redundancy and replication architecture across multiple NAS units on two independent hardware strings, defining the consistency model for cross-string replication, the precise bound on acceptable data loss during a radiation-induced crash, and the storage platform's contractual guarantees in every degraded state: drive level, NAS unit, or full string failure. Codify this as the failure mode matrix that drives every implementation decision downstream </li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Select the filesystem and design the pool architecture, confirming or revising the current ZFS baseline and owning the final configuration. Validate through quantitative reliability modeling that balance upset probability, rebuild risk, write endurance, and usable capacity over the full mission</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Define the write-endurance budget for a multi-year operational lifetime, allocating write capacity across continuous science ingest, continuous data reduction, periodic bulk reanalysis by onboard AI, and archival snapshots to produce data retention policies that retain key science data through end of mission</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Design the interface contracts between the storage platform and the science instrument, compute, and communication subsystems, defining what the storage platform guarantees, what it doesn't, and what happens when a consumer violates the contract while the platform is already in a degraded state </li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Build the storage fault detection and recovery path at the hardware boundary (e.g., kernel driver, block layer, or firmware level) to take a radiation-induced upset from initial detection through filesystem re-integration and ensure transient failures never become data loss </li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Build automated fault recovery that handles every scenario in the failure mode matrix, validated through sustained fault injection campaigns on the hardware-in-the-loop testbed to confirm the architecture performs as specified under real failure conditions. </li> </ul> About You: <ul> <li style="fo

Storage Platform Software Responsible Engineer

About the Role

Related Searches

Ready to apply?

Similar Roles

Senior Backend Engineer

Full Stack Developer

Full Stack Developer