Job Description

Overview

n

Flight software (FSW) engineers write the software that runs on a spacecraft's radiation‐hardened processor. Their work includes attitude control loops, fault‐protection algorithms, command and telemetry managers, payload sequencers, memory scrubbers, and uplink/downlink protocol stacks.

n

Responsibilities

n

n
- Write software for radiation‐hardened processors under real‐time operating systems such as VxWorks 653, RTEMS, FreeRTOS, or NASA's Core Flight System (cFS).
n
- Design and implement attitude‐control loops, fault‐protection algorithms, command and telemetry managers, payload sequencers, memory scrubbers, and uplink/downlink protocol stacks.
n
- Use formal‐methods techniques (SPARK Ada proofs, Frama‐C static analysis), model‐based design (Simulink/Stateflow auto‐code generation), and rigorous unit and integration testing (GMock, Cantata++, VectorCAST).
n
- Maintain traceability from requirements to code using DOORS and conduct peer reviews and configuration‐management tasks.
n
- Conduct hardware‐in‐the‐loop simulation and validate software against flight‐hardware models.
n

n

Qualifications

n

n
- Bachelor's degree in Computer Science, Software Engineering, Electrical Engineering, or a related field.
n
- Master's degree in Real‐Time Embedded Systems, Computer Engineering, or Aerospace Engineering is preferred.
n
- Proficiency in C or C++; experience with Ada/SPARK is a plus.
n
- Hands‐on experience programming for real‐time operating systems (VxWorks 653, RTEMS, FreeRTOS, cFS).
n
- Familiarity with formal‐verification tools, model‐based code generation, and static‐analysis tools.
n
- Experience with DOORS traceability, unit/integration testing frameworks (GMock, Cantata++, VectorCAST), and HIL simulation.
n




- Minimum 3–5 years of relevant industry or research experience; a robust senior/lead background (5+ years) is desirable.
n

n

Key Skills

n

n
- Embedded C/C++ programming
n
- Real‐time scheduler theory (Rate‐Monotonic, EDF)
n
- Formal verification (SPARK Ada, Frama‐C)
n
- Model‐based design and automatic code generation (Simulink/Stateflow)
n
- Static analysis and software‐testing tools (VectorCAST, Cantata++, LDRA)
n
- Hardware‐in‐the‐loop simulation
n
- DOORS traceability and configuration‐management
n
- Space communication protocols (CCSDS, SpaceWire RMAP)
n

n

Salary (U.S.)

n

Entry level (0–3 years): $110 000. Median (4–8 years): $168 000. Senior (9+ years): $250 000. (US‐centric estimates; international compensation varies.)

n

Global Opportunities

n

n
- NASA (USA)
n
- ESA/ESTEC (Europe)
n
- CNES (France)
n
- DLR (Germany)
n
- ISRO (India)
n
- JAXA (Japan)
n
- MDA Space (Canada)
n
- KARI (South Korea)
n
- Satrec Initiative (South Korea)
n

n

Reality Check

n

Good fit if:

n

n
- You find formal verification or proof‐of‐correctness intellectually rewarding.
n
- You are comfortable doing code review on safety‐critical C where a single missing bounds check could destroy a mission.
n
- You enjoy working at the boundary of software and hardware—reading datasheets, writing device drivers, and debugging with a logic analyser.
n

n

Bad fit if:

n

n
- You want modern web‐style development practices; this role has no Docker, no CD pipelines, and 18‐month qualification cycles for a 200‐line change.
n
- You find process documentation (SRS, SDD, test reports per ECSS‐E‐ST‐40C or NASA‐STD‐8739.8) bureaucratic and demotivating.
n
- You are motivated primarily by performance optimisation; FSW correctness constraints often prevent elegant algorithmic solutions.
n

n

#J-18808-Ljbffr

📌 Flight Software Engineer (South Australia)
🏢 UNKNOWN
📍 South Australia