DCGS-N Technical Writer (Job 1202) at DLH Corporation

North Charleston, South Carolina, United States -

Full Time

Start Date

Immediate

Expiry Date

28 Jan, 26

Salary

0.0

Posted On

30 Oct, 25

Experience

2 year(s) or above

Remote Job

Yes

Telecommute

Yes

Sponsor Visa

Skills

Technical Writing, Documentation, Git, Markdown, Python, Ansible, Security Compliance, C4ISR, DevOps, IAT Level II, Docs as Code, Version Control, Static Site Generators, Build Automation, Infrastructure as Code, Scripting

Industry

technology;Information and Internet

Description

About Us DLH delivers improved health and national security readiness solutions for federal programs through science research and development, systems engineering and integration, and digital transformation. Our experts in public health, performance evaluation, and health operations solve the complex problems faced by civilian and military customers alike by leveraging advanced tools – including digital transformation, artificial intelligence, data analytics, cloud enablement, modeling, and simulation, and more. With over 2,400 employees dedicated to the idea that “Your Mission is Our Passion,” DLH brings a unique combination of government sector experience, proven methodology, and unwavering commitment to innovation to improve the lives of millions. Responsibilities Write, edit, and maintain a variety of technical documentation, including: User manuals System administration guides API documentation Software development guides Installation guides Training materials Release notes Troubleshooting guides Security documentation Compliance documentation (e.g., FedRAMP, DoD security standards) Ensure all documentation is accurate, clear, concise, and consistent with established style guides. Update documentation to reflect changes in software, hardware, or processes. Work with subject matter experts (SMEs) to gather information and validate documentation. Manage the entire documentation lifecycle, from planning and creation to review, approval, and publication. Docs-as-Code Implementation & Management: Version Control: Use Git (or other version control systems like Mercurial) to manage documentation source code (typically Markdown, reStructuredText, or AsciiDoc). Branching & Merging: Implement branching strategies for documentation development (e.g., feature branches, release branches). Manage merge requests/pull requests. Build Automation: Set up and maintain build pipelines (using tools like Make, Ant, Maven, Gradle, or scripting languages) to automatically generate documentation outputs (HTML, PDF, etc.) from the source code. Static Site Generators: Utilize static site generators (e.g., Jekyll, Hugo, Sphinx, MkDocs) to create websites from documentation source files. Configure and customize the site generators to meet specific documentation needs. Continuous Integration/Continuous Delivery (CI/CD): Integrate documentation builds and deployments into CI/CD pipelines to automate the process of publishing updates. Infrastructure as Code (IaC) for Documentation: Manage the infrastructure required for documentation (e.g., servers, storage) using IaC tools like Terraform or Ansible. Contribute to Tooling: If the organization is building its own documentation tools or extending existing ones, contribute to the development and maintenance of those tools. Security & Compliance (DoD Specific): Adhere to all applicable DoD security regulations, policies, and procedures related to documentation, including: Proper handling and marking of classified information. Data security and access control. Compliance with DoD cybersecurity standards (e.g., NIST 800-53). Ensure that documentation accurately reflects security configurations and procedures. Contribute to the development of security documentation, such as security plans, incident response plans, and vulnerability assessments. Participate in security audits and inspections. Be aware of data spillage prevention techniques when handling documentation. IAT Level II certified Qualifications Education: Bachelor’s degree in English, Journalism, or Technical Writing. Experience: Three (3) years of experience creating, editing, and reviewing technical documentation, procedures and guidelines for C4ISR or similar systems or equipment. Active TS/ SCI clearance walking through the door. Specific Experience One (1) year of experience with DCGS-N, other C4ISR programs, or Software engineering program/projects. Within 30 days of assignment, the individual should have or be able to obtain Information Assurance Technical (IAT) II certification. Individual should demonstrate knowledge and skills in scripting using Yaml, Python, or similar language; proficient with utilizing DevOps tools for CM automation (Ansible, Chef, Puppet, BMC, or Similar); Proficient in “Docs as Code” approach, writing scripts in Markdown, reStructuredText, or similar; proficient in using GIT for version control or similar. Benefits DLH Corp offers our employees an excellent benefits package including - Personal Time Off (PTO), medical, dental, vision, supplemental life with AD&D, short and long-term disability, flexible spending accounts, parental leave, legal services and more. We want our employees to save for their future, therefore we offer a 401(k) Retirement Plan, which includes a matching component. DLH is dedicated to your career development, providing training to help drive success, with access to our best-in-class e-Learning suite for formal and informal learning, professional and technical certification preparation, and education assistance at accredited institutions. EEO DLH Corporation is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment. DLH will provide reasonable accommodation to individuals with disabilities and disabled Veterans who need assistance to apply.

How To Apply:

Incase you would like to apply to this job directly from the source, please click here

Responsibilities

The Technical Writer will write, edit, and maintain a variety of technical documentation, ensuring accuracy and consistency with established style guides. They will manage the entire documentation lifecycle and implement Docs-as-Code practices.