Documentation Strategy & Process Lead
100% Remote
Video Interview
Long Term Contract
JD:
Key Responsibilities
- Develop a documentation/communication strategy for the Client's covering requirements,
design, roadmap, and support content types, and get it approved by ART leadership
- Define a taxonomy/classification scheme and a storage-location decision matrix (what belongs in SharePoint vs. JIRA vs. Confluence)
- Create a communication plan template tailored to different stakeholder groups
- Establish a style guide for documentation consistency across the ART
- Build version management processes: version control procedures, archival policy, retention schedule aligned to compliance requirements, branching strategy aligned to code/release branches, and rollback procedures
- Conduct an initial assessment (Weeks 1 2) of current Confluence, SharePoint, and JIRA content
- Build a prioritization matrix for documentation needs across 19 applications
- Deliver a gap analysis identifying critical missing documentation that poses migration risk
- Map existing documentation to the new structure and flag orphaned/duplicate content
- Produce a Confluence migration playbook, before/after structure comparison, page tagging/labeling standards, per-team cleanup timeline estimates, and success metrics
Required Skills & Experience
- Strong background in documentation strategy, information architecture, or knowledge
management in a large, multi-team engineering organization
- Hands-on fluency in Confluence, SharePoint, and JIRA/JIRA Align administration and content structuring
- Experience running gap analyses and translating findings into prioritized, actionable plans
- Experience building governance artifacts (style guides, taxonomies, retention/version policies) that other teams can actually follow
- Strong stakeholder management - able to get sign-off from ART leadership and buy-in from
individual delivery teams
- Comfortable working across ~19 applications and teams simultaneously without losing coherence
Preferred / Nice to Have
- Experience with Agile Release Train or SAFe-style delivery structures
- Experience in a regulated or compliance-driven environment (financial services, government,
healthcare)
- Prior experience leading a documentation platform migration or consolidation
Why This Role Is Challenging
- This role's deliverables gate the other documentation role's work (templates, taxonomy, and storage decisions need to land before hands-on requirements documentation scales) - sequencing and early clarity matter
- Must drive adoption across 19 application teams with varying documentation maturity and no formal authority over those teams - this is influence-based work, not directive
- Migration risk is real: gaps identified here directly affect cloud migration timelines, so findings need to be both fast and defensible
- Retention/archival policy must satisfy compliance requirements in a Federal Reserve context, raising the bar on rigor
By continuing you agree to our Terms & Privacy Policy.