Skip to main content

Rocket Lab Corporation

Avionics Automation Test Engineer I/II

Long Beach, CAFrom $107kmidAdded today

About this role

Rocket Lab seeks an Avionics Automation Test Engineer to develop automated testing software and improve efficiency for spacecraft avionics and satellite systems. You'll collaborate with hardware engineers on test strategies, enhance design for testability, and support manufacturing tools while contributing to engineering processes.

What you'll do

  • Develop automated testing software for avionics and satellite test programs
  • Design efficient acceptance and qualification testing strategies with hardware engineers
  • Enhance spacecraft hardware design for improved testability and manufacturability
  • Support and improve manufacturing and production software tools
  • Contribute to engineering and business process improvements for company growth

What they're looking for

  • Python programming
  • Linux software development
  • Electronics test engineering
  • Electrical test equipment and instrumentation knowledge
  • Data acquisition systems
  • Test procedures and methodology
  • Hardware development experience
  • Communication protocols (TCP/UDP, serial)
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

Rocket Lab Corporation

Rocket Lab builds spacecraft and satellites that it launches on its own rockets, developing the avionics, flight software, and ground systems needed to operate these vehicles in orbit. The company is hiring software engineers, test automation specialists, and spacecraft operations engineers to develop embedded flight software, design testing systems, and manage satellite fleet health across commercial and government missions.

View all jobs at Rocket Lab Corporation

Likely interview questions

  • Describe your experience automating test procedures for hardware systems and what tools or frameworks you've used.
  • Tell us about a time you collaborated with hardware engineers to improve design testability—what was your approach?