FlightSoftwareEngineer

The work

Flight software runs the vehicle. It is written against strict standards, reviewed line by line, tested on representative hardware, and deliberately conservative, no dynamic allocation after boot, no surprises. It is also one of the most accessible routes into aerospace for someone who already writes code.

A typical day

• 01Implement and review flight-critical modules
• 02Run tests on hardware-in-the-loop rigs
• 03Trace every requirement to a test that proves it
• 04Debug something that only happens once every ten thousand cycles

How people get in

• Computer science or engineering degree

  The common route. Embedded and robotics projects count for a lot.

• Self-taught plus portfolio

  Harder, but real: demonstrable embedded work on real hardware opens doors.

How it unfolds

1. DegreeComputer science or engineering, with real depth in low-level programming.
2. Years 1-3Test software and tooling. Flight code is not where anybody starts.
3. Years 4-8Flight software for a subsystem, under a standard with an auditor behind it.
4. LaterSoftware architect, or safety and certification.

Is there a job in it

The hard parts

Coding standards, reviews and traceability slow everything down and exist because the alternative has been tried. There is no patch after launch on most of these vehicles. The discipline required is closer to structural engineering than to web development.

What you would need

• C and C++
• Real-time systems
• Verification
• Version control