Skip to main content

AnySignal

Software Engineer (Python)

Los Angeles, CA$120k–$170kfulltimemidAdded 1 month ago

About this role

AnySignal, a space and defense RF technology startup, seeks a Python Software Engineer to design and maintain a comprehensive testing and automation framework. You'll develop tools for data aggregation, automated test execution, and UI systems that support rapid iteration across hardware, software, and DSP components.

What you'll do

  • Develop and maintain Python libraries and frameworks for automated testing across engineering teams
  • Design systems for data aggregation and analysis to support testing workflows
  • Build user interfaces that integrate with hardware and software systems
  • Create extensible software architectures that scale across multiple company projects
  • Develop test automation tools including equipment drivers and debug utilities

What they're looking for

  • Python library development expertise
  • Networking concepts and protocols
  • Software architecture and system design
  • SQL/NoSQL database design (preferred)
  • Test automation and equipment driver development (preferred)
  • Docker containerization (preferred)
  • RF and DSP signal processing knowledge (preferred)
  • GNU Radio familiarity (preferred)
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.

AnySignal

AnySignal builds advanced RF communications systems and power electronics for space and defense missions. The company is hiring Forward Deployed Engineers, Power Electronics Engineers, RF Hardware Engineers, Embedded Software Engineers, and EMC Engineers to develop and deploy mission-critical systems from concept through integration.

View all jobs at AnySignal

Likely interview questions

  • Describe your experience architecting Python libraries for reuse across projects. How do you ensure extensibility and maintainability?
  • Walk us through how you've designed a test automation framework. What challenges did you encounter with equipment drivers or socket interfaces?