Lead Technical Writer

**Job Title:** **Lead Technical Writer** **Department:** **Product Development** **Reports to:** **Manager, Technical Publications** **Office:** **Any Owl Office** **Work Location:** **Remote (EST or CST time zones only)** Owl Cyber Defense is a leader and trusted partner in cyber security. We deliver solutions that protect and connect the world’s most critical networks. Owl’s product lines of cross domain, data diode, and portable media solutions provide the strongest available security checkpoints for threat prevention and secure data availability. Our in\-depth expertise in security engineering at the operating system level enables us to help government and commercial customers meet ever\-evolving cyber security threats. **Job Summary:** The Lead Technical Writer sets the direction for how Owl's Technical Publications team works, the standards it holds, the tools it uses, and how AI and docs\-as\-code change what the team is capable of. You bring a strategic view of content architecture and information design, and you use that view to make decisions other writers can build on. That direction\-setting starts with the fundamentals: this role requires a working knowledge of Git, and you're expected to actively drive and champion scalable, AI\-augmented content workflows and ways of working that meaningfully increase what the team can produce without a matching increase in headcount. You'll be one of the people the rest of the team looks to when deciding how documentation should be structured, tooled, and produced going forward. That shift is already underway. Owl's Technical Publications team is moving from Word\- and SharePoint\-based authoring to a docs\-as\-code model built on Git, with Confluence and Jira as the backbone for planning and collaboration. Day to day, the role also means working across two separate environments: because our products span both standard and air\-gapped networks, every writer on this team regularly moves between two systems and machines over the course of a day. Comfort re\-orienting quickly, keeping work organized across systems, and not losing momentum during that switch is essential. **Essential Duties and Responsibilities:** * Own the team's transition from Word/SharePoint to a Git\-based docs\-as\-code workflow (currently planned around Sveltia, GitLab, and Docusaurus), including tooling, training, rollout sequencing, and adapting the plan in partnership with DevOps if a chosen tool doesn't hold up in practice. * Set content strategy, standards, and information architecture across the Technical Publications team and product portfolio. * Define and champion the team's AI\-augmented content workflows, treating AI as a tool to redefine how documentation work gets done, not just a productivity add\-on. * Personally use AI\-assisted authoring tools in your own writing process daily, modeling the workflows you expect the rest of the team to ado