Allen Control Systems
Software Engineer - Mission Systems/Integration
About this role
Allen Control Systems, a defense startup founded by former Navy engineers, seeks a Software Systems-Integration Engineer to connect their autonomous targeting platform to external systems. You'll integrate third-party sensors, build APIs for command-and-control systems, and manage subsystem communication in a high-impact technical environment.
What you'll do
- Integrate third-party sensors (radar, RF, EO/IR) into the autonomous platform
- Connect sensor fusion and target tracking outputs from the Perception team
- Design and build external APIs for command-and-control and partner system consumption
- Manage networking, transport protocols, and messaging between subsystems
- Maintain command-and-control integrations and system interoperability
What they're looking for
- C++ and Python
- Networking fundamentals (TCP/IP, sockets, protocol debugging)
- API design and consumption
- Distributed systems
- REST, WebSockets, gRPC/protobuf
- Pub/sub and middleware (Zenoh, DDS, ROS 2, MQTT)
- Sensor and radar integration
- Defense C2 standards
Benefits
- Competitive salary
- Equity package
- Health, dental, and vision insurance
- Paid time off
- Engineering-first culture with technical innovation focus
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.
Allen Control Systems
Allen Control Systems builds autonomous defense systems, including gun turrets and drone-defense technology, using computer vision, control systems, and robotics. The company is hiring across software engineering, mechanical engineering, testing, and operations roles to support product development and scaled production.
View all jobs at Allen Control SystemsLikely interview questions
- Walk us through your experience integrating third-party sensors or hardware into a software system. What challenges did you face and how did you overcome them?
- Describe a time you designed an API for external consumption. What protocols or formats did you use, and how did you handle versioning or breaking changes?