Anduril’s Mission Autonomy team builds the software ecosystem used to command and control collaborative combat aircraft (CCA). Our software is deployed both onboard air vehicles and within operator-controlled Ground Control Stations, and it supports the complete “Day-in-the-Life” of these vehicles: operator training, mission planning, mission execution, and mission debrief. Our software is deliberately built to be agnostic to any single air vehicle or software platform, and it is integrated against government reference architectures and interfaces so that it can operate across a competitive vendor ecosystem. Our responsibilities include autonomy software development, air vehicle and ground system integration, flight test support, and the technical documentation that lets operators, integrators, and developers use our autonomy stack correctly. We are seeking an experienced senior technical writer to build and maintain autonomy software documentation in accordance with program and customer requirements. We believe that the quality of our documentation should reflect the quality of our products, which are world-class.
As a senior technical writer, your mission is to partner with our autonomy, platform integration, and flight test teams to deliver accurate, updated, and easy-to-understand documentation on how to integrate, configure, and operate Anduril’s Mission Autonomy software. You will do whatever it takes to organize our engineering and program delivery functions in this mission. In this role, you will work closely with engineers, autonomy behavior developers, test engineers, and various subject matter experts to understand our software, identify integrator and operator workflows, and use documentation to close the gap. As such, the technical writer will play a foundational role in setting the bar for tone, voice, and quality across our written artifacts.
With Anduril’s focus on defense and national security, autonomy documentation plays a critical role in ensuring operators in every role, from Air Vehicle Controller to Quarterback, understand how our autonomy behaves across its operating modes, what it will and will not do on its own, and how to task, override, and approve its actions. Your mission is to make the process of learning how to employ autonomous systems as easy and seamless as possible, with exceptionally written and presented artifacts.
You will identify relevant stakeholders and lead them through a documentation roadmap with established key milestones and targets. This will require an in-depth understanding of what teams are relevant to documentation, and what an organized effort toward collaboration entails. You are to ensure that stakeholders are engaged at the right time, and you will guide them towards a finished user-facing document that plainly meets customer needs. Finally, you will work with our account teams to ensure that contract deliverables are accurate, on time, and in the right format, including documentation that must align to government reference architecture releases and flight test event schedules.
Written content artifacts under this charter may include things like: mission planning, execution, and debrief user guides; autonomy task and behavior overviews; deployment, configuration, and management manuals; message and API reference catalogs; architecture and design documents; integration and test procedures; flight manual and checklist inputs; glossaries; and release notes. You will partner with ILS, product, and engineering teams across all phases of product development to ensure users have the right documentation available, including the third-party air vehicle and ground control vendors who integrate against our autonomy interfaces.
Another critical aspect of this role is to build the infrastructure and tooling needed for creating and maintaining our documentation content at scale. This role spans two authoring environments, and you will be fluent in both. Internally, we run a docs-as-code pipeline so that technical documentation stays aligned with engineering. For customer and contract deliverables, we author structured content in S1000D using RapidAuthor against our Common Source Data Base. A significant part of your charter is keeping these two environments coherent, so that engineering-authored source content flows into formal deliverables without being rewritten from scratch. This structure will enable technical writing contributions from elsewhere across the business. In this role, you will co-lead efforts to define requirements, identify software solutions, and then implement them while also building process and training to scale this function across other teams.