Overview
The Payload Firmware Design Lead is primarily responsible for Payload Controller Flight Software. This role involves developing firmware to support payload-specific operations, ensuring effective data acquisition, processing, and communication.
Responsibilities
- Develop and integrate a reliable, high-performance onboard payload firmware system
- Regularly meet with subsystems to develop and integrate drivers to their requirements
- Direct and support a team of highly-dedicated Firmware members in developing software
- Coordinate and maintain a schedule of “builds” to meet launch requirements
- Document information needed to operate and control the onboard software, during integration and flight
- Debug and regularly test code; use good embedded development practices
- Actively participate in lead and technical meetings, and UTAT recruitment promotions
Expected time commitment: 8-16 hours, varying by the week. Includes work sessions, technical discussions with the Firmware team and other subsystems, mandatory meetings (leads + systems + general), and miscellaneous tasks.
Skills
While not required, the following are a list of skills that would be beneficial to the applicant. You should expect to learn all of these skills as Firmware Lead:
- Programming
- Embedded C (occasionally embedded C++)
- Experience working with microcontrollers - we use STM32 (ARM32), but AVR, PIC, or using Arduinos are also a plus
- Real-Time Operating Systems (RTOS), like FreeRTOS or ZephyrRTOS
- Serial and bus protocols (ex. SPI, I2C, UART, CAN, parallel camera data formats)
- Version control systems, like Git (GitHub) or SVN
- Technical
- Interpreting datasheets to find relevant and critical information
- High-level understanding of PCB design and testing
- Basic electronics prototyping (ex. using breadboards, soldering)
- Electrical lab equipment (ex. multimeters, oscilloscopes)
- Leadership
- Managing a team of fellow students (team/1-on-1 meetings, task assignment and followup, assistance when needed)
- Participating in technical and non-technical discussion with other leads (promoting ideas, raising concerns, listening to others)
- Using collaboration platforms (Notion, Slack, Google Workspace)
Note that the majority of responsibilities and skills overlap with Firmware Design Lead
Payload Firmware Role Description (Dec 2022).pdf