ZT
Technical Writer
Zolon Tech
- 🌏 Worldwide
- Remote
- 12 hours ago
- AWS
- AWS Cloud
- Devops
- DNS
- Performance Testing
- Incident Response
- IaC
- EC2
- RMF
- Disaster Recovery
- Microsoft Word
- Excel
- PowerPoint
- Visio
- Configuration Management
12 hours ago
The Technical Writer works directly with Program Management, AWS/Cloud DevOps Engineers, Database Engineers, Application Developers, Cybersecurity Engineers, QA/Test Engineers, Operations personnel, and WMA Government stakeholders to convert technical activities into clear, controlled, repeatable documentation.
The position is responsible for ensuring migration documentation follows WMA-approved templates, naming conventions, version-control practices, and documentation standards. The Technical Writer will support migration planning through final operational handoff and project closure.
Key Responsibilities:
Migration Plans and Documentation
• Develop and maintain the AFPIMS AWS Cloud Migration Plan.
• Document migration phases, activities, dependencies, prerequisites, assumptions, and completion criteria.
• Maintain technical implementation plans and supporting procedures.
• Capture technical inputs from engineering teams and convert them into formal documentation.
• Maintain documentation throughout planning, development, testing, migration, cutover, and stabilization.
• Ensure documentation accurately reflects the final AWS implementation and operational environment.
• Support development of migration schedules, checklists, readiness documentation, and status reporting artifacts.
Migration and Operational Runbooks
Develop and maintain detailed, step-by-step runbooks supporting AFPIMS migration and AWS operations, including:
• Pre-migration readiness procedures.
• Migration execution procedures.
• Application migration procedures.
• Database migration procedures.
• Data and file migration procedures.
• DNS and network transition procedures.
• AWS environment configuration procedures.
• Security configuration and validation procedures.
• Production cutover procedures.
• Post-migration validation procedures.
• Rollback and recovery procedures.
• Troubleshooting and escalation procedures.
• Operational startup and shutdown procedures.
Runbooks will identify responsible personnel, prerequisites, execution steps, validation points, expected results, escalation paths, and completion criteria.
Backup and Recovery Runbook
Develop and maintain the AFPIMS AWS Backup and Recovery Runbook, including:
• AWS backup procedures.
• Backup schedules and retention requirements.
• Application and database backup procedures.
• Configuration backup requirements.
• Recovery and restoration procedures.
• Recovery validation procedures.
• Backup monitoring and failure-response procedures.
• Roles and responsibilities.
• Recovery Point Objective (RPO) and Recovery Time Objective (RTO) documentation where defined by WMA.
• Evidence required to demonstrate successful backup and recovery testing.
COOP and Continuity Procedures
Support development and update of AFPIMS Continuity of Operations (COOP) documentation for the AWS-hosted environment.
Responsibilities may include:
• Documenting AWS continuity and recovery procedures.
• Updating existing AFPIMS COOP documentation to reflect the cloud architecture.
• Documenting system recovery priorities.
• Documenting alternate operating procedures.
• Identifying dependencies and critical services.
• Documenting recovery sequencing.
• Maintaining emergency contact and escalation procedures.
• Supporting COOP exercises and documenting results.
• Recording lessons learned and corrective actions.
• Ensuring COOP procedures align with the final AWS operational architecture.
WMA Templates and Naming Conventions
Ensure all AFPIMS migration documentation complies with WMA documentation requirements.
Responsibilities include:
• Use WMA-approved document templates.
• Establish and maintain standardized document naming conventions.
• Maintain document numbering and identification standards.
• Establish version-control conventions.
• Maintain revision histories.
• Track draft, review, approved, and final document status.
• Ensure consistent terminology across migration documentation.
• Maintain document repositories and folder structures.
• Ensure final documents are properly labeled and prepared for Government acceptance.
The Technical Writer will coordinate with WMA stakeholders to identify applicable templates and documentation standards before finalizing deliverables.
Test Plans and Test Evidence
Work closely with QA/Test, Engineering, Security, and Operations teams to capture and organize evidence demonstrating successful migration and system validation.
Documentation may include:
• Test plans.
• Test procedures.
• Test cases and scripts.
• Expected versus actual results.
• Screenshots and supporting evidence.
• Application functionality validation.
• Infrastructure validation.
• Network connectivity testing.
• Database validation.
• Performance testing.
• Security validation.
• Backup and recovery testing.
• Failover/recovery testing.
• Defect and remediation tracking.
• User Acceptance Testing (UAT) documentation.
• Final test summary reports.
Ensure test evidence is organized, traceable, version-controlled, and available to support Government review and acceptance.
Training Documentation
Develop training materials supporting the transition of AFPIMS operations into AWS.
Training documentation may include:
• AWS environment orientation.
• Operations procedures.
• System administration procedures.
• Monitoring and alert-response procedures.
• Backup and recovery procedures.
• Incident escalation procedures.
• Troubleshooting guides.
• Quick-reference guides.
• Standard Operating Procedures (SOPs).
• Knowledge-transfer presentations.
• Service Desk support documentation.
• Frequently Asked Questions (FAQs).
Coordinate with technical SMEs to validate training materials before delivery.
Operations Handoff
Develop the documentation package required to transition AFPIMS from the migration team to steady-state Operations.
The operational handoff package may include:
• Final system architecture documentation.
• As-built documentation.
• AWS configuration documentation.
• Application support procedures.
• Network and connectivity documentation.
• Monitoring and alerting procedures.
• Backup and recovery runbooks.
• COOP procedures.
• Incident response and escalation procedures.
• Routine maintenance procedures.
• Troubleshooting procedures.
• Known issues and workarounds.
• Administrative procedures.
• System dependencies.
• Support contact information.
• Knowledge-transfer materials.
• Operations acceptance checklist.
Support formal knowledge-transfer sessions between the migration engineering team and AFPIMS Operations personnel.
Migration Closure Documentation
Support formal project and migration closure following successful transition to AWS.
Closure documentation may include:
• Migration Completion Report.
• Final Migration Summary.
• Final test results and evidence.
• Government acceptance documentation.
• Outstanding issues and action items.
• Known risks and limitations.
• Lessons learned.
• Final configuration documentation.
• Final architecture diagrams.
• Completed migration and cutover checklists.
• Documentation inventory.
• Operations handoff confirmation.
• Legacy environment disposition/decommissioning documentation.
• Final deliverable acceptance tracking.
Documentation Management
The Technical Writer will maintain a controlled documentation library for the migration effort.
Responsibilities include:
• Maintain a Master Document Register.
• Track document owners and SMEs.
• Track document status and approval.
• Maintain revision histories.
• Manage review/comment cycles.
• Identify missing documentation.
• Track Government-requested changes.
• Maintain consistent terminology and formatting.
• Ensure final documentation reflects the production AWS environment rather than outdated migration designs.
Coordination with Migration Team
The Technical Writer will work closely with:
Program Manager: Migration planning, schedules, risks, deliverables, Government reporting, and closure.
Cloud DevOps Engineer: AWS architecture, Infrastructure as Code, EC2, networking, deployment, migration, and operational procedures.
Database Engineer: Database migration, backup, restoration, validation, and recovery procedures.
Application Developers: Application configuration, deployment, dependencies, troubleshooting, and support documentation.
QA/Test Engineer: Test plans, test cases, test evidence, defects, acceptance criteria, and validation results.
Security Engineer: RMF/ATO documentation, security procedures, vulnerability remediation, security evidence, and AWS security configuration.
Operations Team: SOPs, monitoring, backup, troubleshooting, maintenance, incident escalation, and operational handoff.
Potential Technical Writer Taskers
The Technical Writer may be assigned taskers including:
• AFPIMS AWS Cloud Migration Plan
• Detailed Migration Runbook
• Production Cutover Runbook
• Rollback Runbook
• AWS Backup and Recovery Runbook
• COOP Procedures
• Disaster Recovery Procedures
• Operational Readiness Plan
• Test Plan
• Test Evidence Package
• UAT Documentation
• AWS Operations SOP
• Monitoring and Alert Response SOP
• Incident Escalation Procedures
• Troubleshooting Guide
• Training Plan
• Training Materials
• Knowledge Transfer Package
• WMA Documentation Templates
• WMA Naming Convention Standard
• Master Document Register
• Configuration/As-Built Documentation
• Operations Handoff Package
• Migration Completion Report
• Lessons Learned Report
• Final Documentation Inventory
• Project Closure Package
Required Qualifications:
• Experience developing technical documentation for IT infrastructure, cloud, application, or system migration projects.
• Experience developing technical plans, SOPs, runbooks, procedures, and training materials.
• Ability to translate complex technical information into clear and repeatable procedures.
• Experience working directly with engineers, developers, cybersecurity personnel, testers, and operations teams.
• Strong Microsoft Word, Excel, PowerPoint, Visio, SharePoint, or equivalent documentation-tool experience.
• Experience with document configuration management, version control, and formal review processes.
• Strong organizational, writing, editing, and communication skills.
• Ability to manage multiple technical documentation tasks simultaneously.
Location: Remote
Clearance: DoD active Secret
Technical Writer · Zolon Tech