Role Overview
K2 is building the largest and highest-power satellites ever flown, mass-producing platforms for missions from LEO to deep space. The software team builds our stack primarily in Rust, developing mission-critical code that controls propulsion, attitude control, and power systems for spacecraft operating in harsh radiation environments.
Responsibilities
- Create software architecture for real-time, fault tolerant control of a 20kW+ spacecraft
- Develop software applications for control of spacecraft subsystems including propulsion, guidance/attitude control, thermal, power, and communications systems
- Design and implement state machines for robust spacecraft operation
- Author drivers for microcontroller peripherals and external sensors
- Create and utilize robust tools for rapid deployment of quality code
- Perform data analysis and anomaly investigation to identify and resolve software bugs
- Support integration and testing of spacecraft subsystems
- Build and maintain infrastructure to increase reliability in software development and testing
Qualifications
- Bachelor's degree in computer science, computer engineering, electrical engineering, math, or STEM discipline or 3+ years of professional experience in software engineering
- Development experience in C/C++ or Rust
Nice to Have
- Experience with spacecraft flight software development
- Fluency with Linux systems programming and driver development
- Experience with continuous integration and continuous delivery systems
- Experience working with hard real-time embedded systems (bare-metal or RTOS)
- Experience authoring no_std systems in Rust
- Basic knowledge of electronics, computer architecture, and control systems
- Experience developing or working with state machines
- Experience with software verification and testing methods
- Experience with software and network performance analysis and debugging
- Experience working in Rust production environments
- Experience with fault tolerant software design and implementation
- Experience defining and creating test systems for both hardware-in-the-loop and hardware-out-of-the-loop