> Markdown version of [/jobs/ext/2657993-technical-writer-it-disaster-recovery-and-infrastructure-3](https://www.wearedevelopers.com/jobs/ext/2657993-technical-writer-it-disaster-recovery-and-infrastructure-3). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Technical Writer IT Disaster Recovery and Infrastructure 3

- **Company:** Choctaw Nation of Oklahoma
- **Location:** Durant, OK, United States
- **Experience:** Experienced
- **Contract:** Permanent contract
- **Skills:** Information Systems, Data Loss, Disaster Recovery, IT Management, Real-Time Operating Systems, Runbook, Information Technology, Software Version Control
- **Published:** August 29, 2026
- **Apply:** https://www.careerjet.com/job/usc85c6d4737823d2a780dd4ecd7686b39/eaa

## About the Role

Bachelor's degree in Technical Communication, Information Systems, Computer Science, Business, or a related field
5+ years of technical writing experience supporting IT organizations
2+ years of experience creating or maintaining Disaster Recover (DR), Business Continuity (BC), operational runbooks, recovery procedures, or IT governance documentation
Working knowledge of DR concepts including RTOs, RPOs, recovery testing, tabletop exercises, runbooks, and system restoration procedures
Experience facilitating documentation reviews, governance processes, audits, or compliance assessments related to DR programs

## Description

Full Time| Monday-Friday 8:00AM-4:30PM| Hybrid Position| Weekly Earned Wage Access is an option for this position.
Job Purpose or Objective(s): The Technical Writer focuses on coordinating, developing, monitoring, and implementing IT disaster recovery plans to ensure that critical IT functions can be restored quickly and with minimal data loss following a business interruption, cybersecurity event, or disaster. The Technical Writer will work with leadership to analyze organization-wide initiatives and contingency plans. Will work with technical SMEs to define and document the critical steps necessary to properly restore IT services. Will lead the disaster recovery preparedness governance needed to ensure the disaster recovery playbooks are kept up to date and tested on a regular basis.
Primary Tasks:

 1. Create and continuously update detailed, system-specific recovery playbooks documenting step-by-step restoration procedures, sequencing, and dependencies for mission-critical systems.
 2. Translate infrastructure, application, and operational recovery processes into standardized, repeatable documentation to ensure consistent recovery execution across IT divisions.
 3. Serve as the owner and curator of the centralized Disaster Recovery (DR) documentation repository, ensuring version control, secure access, and availability during disaster scenarios.
 4. Lead the documentation governance process, ensuring all artifacts align with CNO standards, regulatory requirements, and industry best practices.
 5. Organize and facilitate structured read-throughs, tabletops, simulations, parallel tests, and full cutover tests to validate accuracy, completeness, and usability of DR documentation with SMEs and recovery teams.
 6. Collaborate with IT teams to ensure documentation supports real-world recovery testing, capturing results and refining procedures based on test outcomes and lessons learned.
 7. Engage with infrastructure, application, security, and business stakeholders to gather detailed inputs required to document recovery steps, dependencies, and escalation paths.
 8. Implement and manage a recurring cadence to review, update, and enhance DR documentation to reflect system changes, team member changes, new implementations, and evolving risks.
 9. Maintain documentation artifacts that support audit, insurance, and regulatory requirements-ensuring traceability, completeness, and measurable coverage across all systems.
 10. Other duties as assigned., 1. Create and continuously update detailed, system-specific recovery playbooks documenting step-by-step restoration procedures, sequencing, and dependencies for mission-critical systems.
 2. Translate infrastructure, application, and operational recovery processes into standardized, repeatable documentation to ensure consistent recovery execution across IT divisions.
 3. Serve as the owner and curator of the centralized Disaster Recovery (DR) documentation repository, ensuring version control, secure access, and availability during disaster scenarios.
 4. Lead the documentation governance process, ensuring all artifacts align with CNO standards, regulatory requirements, and industry best practices.
 5. Organize and facilitate structured read-throughs, tabletops, simulations, parallel tests, and full cutover tests to validate accuracy, completeness, and usability of DR documentation with SMEs and recovery teams.
 6. Collaborate with IT teams to ensure documentation supports real-world recovery testing, capturing results and refining procedures based on test outcomes and lessons learned.
 7. Engage with infrastructure, application, security, and business stakeholders to gather detailed inputs required to document recovery steps, dependencies, and escalation paths.
 8. Implement and manage a recurring cadence to review, update, and enhance DR documentation to reflect system changes, team member changes, new implementations, and evolving risks.
 9. Maintain documentation artifacts that support audit, insurance, and regulatory requirements-ensuring traceability, completeness, and measurable coverage across all systems.
 10. Other duties as assigned.


## Related Videos

- [Technical Documentation - How Can I Write Them Better and Why Should I Care?](https://www.wearedevelopers.com/videos/681-technical-documentation-how-can-i-write-them-better-and-why-should-i-care)
- [Your Manager Doesn’t Come with a User Manual (But You Can Totally Write One)](https://www.wearedevelopers.com/videos/1495-your-manager-doesn-t-come-with-a-user-manual-but-you-can-totally-write-one)
- [How to Avoid LLM Pitfalls - Mete Atamel and Guillaume Laforge](https://www.wearedevelopers.com/videos/1328-how-to-avoid-llm-pitfalls-mete-atamel-and-guillaume-laforge)
- [Offline-First Engineering for Disaster-Ready Applications](https://www.wearedevelopers.com/videos/2083-offline-first-engineering-for-disaster-ready-applications)
- [Bridging AI and Nomad: a Go-based MCP Server for Cluster Control](https://www.wearedevelopers.com/videos/2063-bridging-ai-and-nomad-a-go-based-mcp-server-for-cluster-control)
- [Engineering/Manager Pendulum: Generating compound interest on your career](https://www.wearedevelopers.com/videos/100348-engineering-manager-pendulum-generating-compound-interest-on-your-career)

## Related Articles

- [Technical Documentation For Developers](https://www.wearedevelopers.com/magazine/128-technical-documentation-for-developers)
- [7 Best Steps For Writing Good Software Technical Documentation](https://www.wearedevelopers.com/magazine/113-7-best-steps-for-writing-good-software-technical-documentation)
- [WWC24 Talk - Brenda Romero - Stay: Surviving and Thriving in Tech](https://www.wearedevelopers.com/magazine/467-wwc24-talk-brenda-romero-stay-surviving-and-thriving-in-tech)
- [Data Science & more: The Lopez dilemma](https://www.wearedevelopers.com/magazine/10-data-science-more-the-lopez-dilemma)
- [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)
- [Humanizing Your Documentation](https://www.wearedevelopers.com/magazine/133-humanizing-your-documentation)