Flight software intern

Pay in the destination countries

Monthly, in US dollars. Each country is an Imora admission package — open one for that route's fees, language requirement and deadline.

What does the day look like?

Only 10% of your day is spent writing novel flight logic or control algorithms, which is the part most people imagine. The largest share, 45% of the day, goes into writing automated unit and regression tests in Python, simulating fault injections, and tracing testbench telemetry. Another 30% involves debugging hardware-in-the-loop (HIL) test rigs, reading hardware data sheets, and fixing bus timeouts across protocols like CAN bus, SpaceWire, SPI, I2C, or MIL-STD-1553. The remaining 15% is spent on safety documentation, code reviews against ECSS-E-ST-40C or NASA-STD-8739.8 standards, and standups.

You typically work a standard schedule of 35 to 40 hours per week. Flight software is developed in C and C++ for on-board computers (OBC) running real-time operating systems such as FreeRTOS, RTEMS, or VxWorks. Night shifts are rare for interns, occurring only during critical launch simulations or continuous flat-sat testing campaigns. On-call duties do not apply to interns.

Where does this lead?