Lead Software Engineer - Multi-Agent Mission Systems

Job description

Job responsibilities

• Drive the technical vision, architecture, and roadmap for the Autonomous Behaviors and Agents team, and direct execution from concept through delivery
• Lead, mentor, and grow a team of engineers, driving design reviews, setting engineering standards, and raising the bar on code quality and algorithmic rigor
• Guide the design and implementation of multi-agent optimization algorithms for distributed decision-making and coordination problems
• Direct development of temporal logic frameworks and constraint-satisfaction algorithms for complex planning scenarios
• Partner with product, program, and customer-facing stakeholders to translate mission needs into technical priorities, scope, and delivery commitments
• Coordinate cross-team integration and de-risk dependencies across the Axion and Acuity system families

Job requirements

• MS or PhD in Computer Science, Software Engineering, Robotics, or a related technical field, OR 8+ years of professional experience developing intelligent agents or planning systems
• 8+ years of hands-on experience developing performant modern C++ (we use C++20), with 2+ years leading engineering teams or serving as a technical lead on complex software programs
• Depth in one or more of the formal foundations underpinning this work, for example: automated and temporal planning (PDDL, HDDL, HTN);
• A track record of setting technical direction, driving architectural decisions, and delivering complex systems through a team, not just as an individual contributor
• Strong theoretical understanding and practical experience implementing algorithms for constraint satisfaction, scheduling, and optimization problems
• Deep procedural and object-oriented programming experience that employs clean code principles and good OOP design patterns, with the judgment to enforce them pragmatically across a codebase
• Experience developing in Docker and containerized development environments, and using Linux-based operating systems (e.g., RHEL, Ubuntu)
• Understanding of service-oriented architecture and message broker vs. data broker paradigms, and experience making system-level architectural tradeoffs