Robotic Software Engineer, Perception

Job description

Job responsibilities

• Develop, integrate, and adapt cutting-edge AI/ML algorithms running on the perception autonomy stack to collect relevant information across a suite of platform sensors
• Create interfacing software to autonomously control sensors (e.g., EO, IR, acoustics, radar, and RF)
• Collaborate across the sensor, tracking, and autonomy teams to ensure seamless deployment of heterogeneous platform swarms in on-site DoD testing and demonstration events
• Deploy containerized solutions to embedded Linux devices, leveraging computer-in-the-loop testing and profiling, and efficiently collecting performance data
• Interact with the DoD customer to understand their use cases, requirements, and triage needs during field events to deliver a superior customer experience
• Work closely with our existing team to internally triage technical problems and scope
• Carefully communicate and document ongoing work to ensure internal flexibility in a fast paced environment as well as clarify progress with external customers
• Drive execution of simulation tooling to playback sensors, platforms, and autonomy in post processing field test analysis

Job requirements

• MS or PhD in Electrical Engineering, Computer Engineering, Robotic Engineering, Computer Science, Optimization, or equivalent OR 5+ years of relevant experience working with sensor algorithms, hardware, and HIL…
• Experience with multiple sensor modalities (e.g., EO, IR, lidar, radar, sonar, acoustics, etc.)Core understanding of sensor physics and sensor control parameters
• Experience training and deploying ML algorithms (python, pytorch, tensorflow) onto integrated systems (onnx, C++ models)
• Familiarity with tracking basics (e.g., Kalman filters) and optimal sensor fusion
• Experience working comfortably in Linux and Docker
• Prior experience with remote software development, ability to handle and process large datasets, and learn new software and algorithms as needed with little supervision
• Must be willing to travel as projects requires, usually for SW/HW integration and/or demonstrations; estimated average travel is every 1-2 months for 2-5 days (10-20%)
• Must be a U.S. Citizen