Skip to main content

Array Labs

Embedded Software Test Engineer

Redwood City, CA$150k–$250kmidAdded 1 month ago

About this role

Array Labs seeks an Embedded Software Test Engineer to validate complex radar payload systems for earth observation satellites. You'll develop firmware and automation tools to test FPGAs, RF components, and antenna arrays, ensuring hardware reliability in space conditions.

What you'll do

  • Develop firmware to exercise FPGAs, RF front-ends, and antenna arrays
  • Create Python automation scripts to orchestrate and execute test campaigns
  • Conduct hands-on lab testing to validate system performance under extreme conditions
  • Bridge hardware and software validation throughout the development lifecycle
  • Document test results and identify performance issues or failures
  • Collaborate with hardware and systems teams to refine test methodologies

What they're looking for

  • Embedded software development (C/C++)
  • Python automation and scripting
  • FPGA testing and validation
  • RF systems and antenna testing knowledge
  • Hardware-software integration experience
  • Test framework development
  • Lab equipment operation
  • Problem-solving and debugging skills
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

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

Array Labs

Array Labs builds advanced radar satellite constellations that provide real-time Earth observation and 3D mapping for disaster response, infrastructure monitoring, and intelligence applications. The company is hiring engineers across hardware design, systems architecture, software development, RF testing, and signal processing to develop and validate next-generation satellite payloads and coordinated fleet operations.

View all jobs at Array Labs

Likely interview questions

  • Describe your experience testing FPGA-based systems. How have you validated FPGA functionality and debugged issues in embedded hardware?
  • Walk us through a time when you wrote firmware to test or exercise hardware components. What challenges did you face and how did you overcome them?