Flight Software Engineer

Katalyst

Description:

Katalyst is an American technology company focused on d ynamic space operations . We are building a fleet of dual-use multipurpose robotic space vehicles to creat e the future where maneuvering, upgrading, refueling, resupply and exploration are as routine as they are on Earth. Getting to space and overcoming the gravity well is only half the story. What you do there is the future.

We are not building the trains. We are building the machines that lay down the tracks. By developing the foundational capabilities that make sustained, responsive operations possible, we enable a new era of space exploration that strengthens national security and ensures freedom of action in an increasingly contested domain.

Working at Katalyst is intense, hands-on, and deeply rewarding. You'll take real ownership and see your work move from concept to operations in an environment where the problems are hard and the impact is real. We value humility, craftsmanship, and doing things the right way, even when it's harder. You'll work closely with thoughtful, driven teammates who push each other to do their best.

Broomfield, CO. Onsite. Full time. This position may be filled at Engineer, Senior, or Principal level depending on experience. Pick the level where you are strongest, we interview against that bar.

Katalyst builds spacecraft that rendezvous with, capture, and service other spacecraft. Our first vehicle is in orbit right now, flying real proximity operations, and the flight software running it is what you would own: the core platform every subsystem, sensor, and radio on the vehicle talks through. Small team, real hardware, your code flies, and you watch it fly from the console.

• Own core flight software subsystems end to end: telemetry and messaging, the command and sequencing path, fault detection and recovery, hardware interfaces (UART, CAN, TCP/IP, RS-422), and the radios that keep us commandable
• Write modern C++ on a Linux flight computer, Python where it moves faster, and keep it memory-safe and thread-safe under schedule pressure, because the schedule belongs to a spacecraft
• Take changes from design through review, flatsat and hardware-in-the-loop verification, deploy, and on-orbit behavior, and close them, verified and handed over, not demoed
• Run point on anomalies: diagnose from telemetry and logs, decide what is safe to command, then fix the class of defect, not the instance
• Make the team stronger: review flight code with rigor, hand systems off with documentation that outlives you, and coach less experienced engineers to shippable instead of rewriting their work
• Defend your design decisions to GNC, avionics, operations, and leadership, with data

• Deep, hands-on C++ on real-time or resource-constrained systems that had to work, RTOS or embedded Linux
• Fault-tolerant thinking: what happens when this module fails, how the vehicle stays safe and commandable, how it recovers without waiting for the ground
• The habit of finishing: you close what you commit to, you verify before you call it done, and when a date slips we hear it from you first
• The instinct to challenge an assumption, back the challenge with data, and convince people. Engineers here make the call and defend it.

Engineer: 2+ years. Senior: 6+ years. Principal: 10+ years. Years are a guide, not a gate. Spacecraft or launch vehicle experience helps a lot, real-time software on real hardware that had to work is what we actually need, and at Engineer level we care more about how fast you learn than what you have already flown.

BS in computer science, computer engineering, aerospace, electrical engineering, or equivalent proficiency. We mean the "or".

US person (ITAR). No security clearance…