Technical Writer/Content Strategist
ECSEverforth ECS is looking for a Technical Writer/Content Strategist to join its hybrid team in Arlington, Virginia. This role supports the Cybersecurity and Infrastructure Security Agency’s TESS program, with work focused on documentation and content management for the CISA Office of the Chief of Staff (OCOS) CIRCIA team. It’s a fit for someone who enjoys turning complex technical and regulatory material into clear, accessible content and who thrives in a federal environment.
The company behind the role operates as the federal arm of Everforth and brings a mission-driven, delivery-focused culture to the federal space. If you like collaborating with cyber SMEs, engineers, and policy staff to produce runbooks, SOPs, and user guides, you’ll feel at home here. The position is hybrid, based in Arlington, and sits at the intersection of technology, governance, and communications.
In this job you’ll help shape how information is created, reviewed, and published across multiple platforms, with an emphasis on quality, accessibility, and consistency. It’s a chance to impact content that supports security programs and federal operations while growing your own skills in documentation strategy and knowledge management.
A day in the life of a content pro at TESS
Your mornings might start with audits to verify the accuracy of existing material, followed by coordinating updates in coordination with cyber subject matter experts and engineering staff. You’ll draft and refresh technical documents, map content to standardized templates, and ensure alignment with federal requirements and accessibility standards. Throughout the day you’ll manage version control and content lifecycles, track changes, and help push updates across PDFs and web-based formats.
Part of the role is orchestrating the look and feel of graphics and documents across multiple channels, making sure formats stay consistent whether teammates are viewing PDFs or online learning modules. You’ll interview SMEs and cloud engineers to extract key details, then translate those details into practical, user-facing content such as runbooks and knowledge-management deliverables. Collaboration with external vendors and a broad set of stakeholders is common, and you’ll be part of initiatives to standardize templates and governance across the team.
What you’ll bring to the table
- Must-have: you’re a US citizen who can obtain and maintain Public Trust Suitability for federal work.
- Must-have: you communicate clearly in writing and speech, stay organized, and keep a steady eye on detail while working well with others.
- Must-have: at least five years of technical writing or editing experience, producing documentation with guidance and collaborating across technical and non-technical teams.
- Must-have: a minimum of two years in content management, including content curation and digital workflows.
- Must-have: comfort with Word, Excel, and PowerPoint, plus hands-on experience with content management systems and learning management systems (Moodle is preferred).
- Must-have: at least two years coordinating with engineering and management to complete documentation efforts.
- Must-have: basic knowledge of cloud infrastructure concepts (AWS or similar).
- Must-have: familiarity with cybersecurity frameworks, Authority to Operate processes, vulnerability management, and POA&M tracking.
- Must-have: ability to create operational runbooks, standard operating procedures, and user guides for technical platforms.
- Must-have: experience working with external vendors and multiple stakeholders to manage content updates and review cycles.
- Must-have: a detail-focused, quality-driven mindset and a proactive approach to continuous improvement.
- Must-have: flexibility and adaptability in a shifting environment with competing priorities.
- Must-have: a basic grasp of Agile processes and methodologies.
- Must-have: capability to handle multiple tasks, shifting priorities, and deadlines.
- Must-have: proficiency with version control and documenting repositories (examples include SharePoint, Confluence, Git).
- Nice-to-have: a bachelor’s degree in Technical Communication, Instructional Design, Information Management, English, or a related field, or equivalent professional experience.
- Nice-to-have: familiarity with Software Development Life Cycle and Agile frameworks.
- Nice-to-have: knowledge of accessibility standards (Section 508, WCAG 2.1) and creating accessible content.
- Nice-to-have: training or coursework in content strategy, information architecture, or knowledge management.
Pay, benefits and practical details
The role comes with a salary range of $100,000 to $120,000 per year. The work arrangement is hybrid, and the position is based in the Arlington, VA office. General benefits information is available at the linked page: General Description of Benefits.
Everforth ECS is the federal arm of Everforth, a large global organization with thousands of professionals delivering technology solutions across data, AI, cybersecurity, and enterprise transformation for defense, intelligence, and federal civilian agencies. The company emphasizes excellence in delivery, a culture of innovation, and opportunities for professional growth, with a focus on attracting top talent and building high-performing teams.
Advice for applicants
Lead your resume with evidence of your most relevant experience: highlight five-plus years as a technical writer or editor and two-plus years in content management, plus any Moodle or LMS work and your experience with CMSs like SharePoint or Confluence.
Show how you prove you can handle the must-have skills by sharing tangible examples: for instance, describe a runbook or SOP you created, how you collaborated with cyber SMEs, and how you managed version control across revisions and platforms.
Prepare for interviews by detailing your approach to content governance, your process for interviewing subject matter experts, and a concrete example of improving content quality and accessibility in a federal project.
Ask a smart question to gauge the team’s current practices: how do you enforce standardized templates and governance across PDFs and web content, and what tooling do you use for content lifecycle management and metadata tagging?