Lead Technical Writer

Owl Cyber Defense•Morrisville, NC

4d•Remote

About The Position

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. This role requires a strategic view of content architecture and information design, and uses that view to make decisions other writers can build on. The team is transitioning 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. This role also involves working across two separate environments (standard and air-gapped networks), requiring comfort in re-orienting quickly, keeping work organized across systems, and maintaining momentum during system switches.

Requirements

Bachelor's degree in Technical Writing, English, Communications, Computer Science, Engineering, or a related field, or equivalent practical experience.
8+ years of technical writing experience, including experience leading projects, workflows, or people.
Knowledge of Git, Jira, Confluence, Word, SharePoint, Teams, Adobe products, and AI-assisted authoring tools.
Strong working knowledge of Git.
Demonstrated success leading a significant tooling or process transformation (e.g., a docs-as-code migration, a new content management approach, or comparable change).
Proven experience designing and driving adoption of AI-augmented workflows that measurably increased team output or capability.
Strong strategic thinking around content architecture and information design at a team or organizational scale.
Excellent planning, prioritization, and cross-functional communication skills; comfortable operating with significant autonomy.
Candidates must be able to obtain/maintain a US Government security clearance.

Nice To Haves

Background in cybersecurity, defense, or another regulated/technical hardware-software industry.
Experience operating across segmented or air-gapped network environments.

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.
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.
Personally use AI-assisted authoring tools in your own writing process daily, modeling the workflows you expect the rest of the team to adopt.
Mentor and develop writers on the team, including hands-on training in Git-based workflows and AI-assisted authoring.