In this role, you will be responsible for creating clear, structured, and highly technical documentation for internal engineering systems, partnering closely with senior developers and infrastructure teams. You'll apply a strong foundation in software engineering along with hands-on knowledge of cloud and DevOps environments- including Azure GovCloud, infrastructure provisioning with Terraform, CI/CD pipelines, PostgreSQL operations and disaster recovery, configuration management, and observability best practices. You'll produce concise how-to guides, installation and troubleshooting procedures (PowerShell/Bash), and standardized content organized for developer audiences using defined templates. Success in this role requires proficiency with Confluence, GitHub, Jira, and diagramming tools, plus excellent information architecture skills. You'll also independently manage limited SME availability through effective interviewing and scheduling, while communicating directly with Directors and Lead Engineers to deliver accurate, user-friendly documentation.

Skills and expertise needed:

Software Engineering Foundation:

• A deep understanding of software development and engineering principles is a primary requirement.
• Cloud & DevOps Literacy: The writer must be comfortable documenting highly technical, internal-facing systems.
• Cloud Infrastructure: Azure (specifically GovCloud/IL4), cloud architecture, Infrastructure as a Service, terraform, and provisioning.
• CI/CD: Complex continuous integration and deployment pipelines.
• Databases: PostgreSQL provisioning, operations, and disaster recovery (DR).

Configuration Management:

• Documenting unified configuration systems and migration from legacy tools.
• Observability: Writing best practices for monitoring and alerting.

Core Documentation & Writing Skills:

• Clarity and Conciseness: The ability to create clear, concise, and user-friendly documentation.
• Procedural Writing: The writer must be able to create clear how-to guides, particularly for installation (using Powershell/Bash) and troubleshooting.
• Information Architecture: The project requires standardizing formats and organizing content logically for a developer audience (e.g., "Onboarding," "Infrastructure," "Troubleshooting") to improve findability .
• Template Adherence: The writer must be able to follow specific templates, such as the MSF Docs Single Page Design, which outlines a precise structure for content.

Tool Proficiency:

• Content Platforms: The writer must be proficient in using Confluence and GitHub as the primary documentation platforms.