SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
True Anomaly is building autonomous spacecraft, advanced payloads, mission software, and space-based interceptors to secure the space environment and counter threats. As Engineering Manager, Autonomy, you will lead a team of autonomy engineers developing multi-agent resource allocation systems and edge-deployed physical AI capabilities for spacecraft operations.
Your primary responsibility is people leadership: building and growing the team through recruiting, hiring, and retention; conducting 1-on-1s and performance reviews; setting goals; and developing individual contributors into technical leaders. You will foster a culture of technical excellence, rigorous evaluation, and rapid iteration from concept to flight.
You will also own the team roadmap in collaboration with autonomy leadership, balancing near-term delivery (flight demonstrations, customer test campaigns) with long-term capability development (continuous learning, end-to-end neural planning). You will translate organizational strategy and technical vision into actionable team objectives aligned to customer missions, prioritize work across competing demands, manage cross-functional dependencies, and track progress and risks to leadership.
Technically, you will spend approximately 35% of your time on strategic contributions: providing direction on multi-agent coordination architectures, edge deployment strategies, and validation approaches; reviewing and approving technical designs for optimization algorithms and distributed coordination protocols; participating in design, implementation, and verification; defining autonomy standards and explainability requirements; and driving decisions on compute allocation and real-time performance trade-offs. You will maintain technical credibility in operations research, reinforcement learning, and edge AI deployment, and bridge air domain autonomy expertise with space domain constraints including orbital mechanics, communication latency, and compute/power budgets.
