Socure · Lead Technical Writer

Leading documentation operations through infrastructure and product transformation

Overview

At Socure, Technical Writers were embedded within vertical cross-functional teams, but there was no formal documentation leader overseeing the broader documentation function.

As Lead Technical Writer, I took ownership beyond content development. I managed the documentation infrastructure, maintained platform dependencies, coordinated Docusaurus upgrades, and owned the CI/CD workflows supporting documentation authoring and publishing. This also meant working closely with engineering to ensure broader DevOps changes did not disrupt documentation operations.

As Socure expanded its offerings into FedRAMP-authorized environments, I established and maintained a separate documentation site for government customers. This introduced additional coordination with SMEs to ensure commercial product releases and FedRAMP-authorized capabilities were accurately reflected in their respective documentation experiences.

Later, following Socure's acquisition of Effectiv, the company began transitioning customers to its new RiskOS platform. With only three weeks before the holiday period, I took on the challenge of quickly learning the new platform while engineers were still adapting and integrating it into Socure's ecosystem. I designed the new documentation experience, established its information architecture and customer onboarding flows, and continuously validated documentation against the latest product changes.

These experiences required me to operate across documentation engineering, product knowledge, quality assurance, compliance requirements, and customer experience.

Project at a glance

AreaDetails
RoleLead Technical Writer
Documentation platformDocusaurus
Platform evaluationReadMe and alternative documentation solutions
InfrastructureGitLab, Docker, Jenkins
ScopeDocumentation infrastructure, dependencies, upgrades, CI/CD, content strategy, and publishing operations
Documentation environmentsCommercial and FedRAMP
Product transformationEffectiv acquisition and transition to RiskOS
Key responsibilitiesPlatform ownership, infrastructure maintenance, information architecture, SME coordination, product validation, and customer onboarding

01. The challenge: Documentation without dedicated ownership

At Socure, Technical Writers were embedded in vertical cross-functional teams, allowing them to work closely with their respective Product and Engineering stakeholders.

However, there was no formal documentation leader responsible for the shared infrastructure, publishing operations, and broader documentation platform strategy.

I stepped into that gap, taking responsibility for keeping the documentation ecosystem operational while supporting the needs of individual product teams.

Fragmented infrastructure ownership

The documentation sites were built using Docusaurus, an open-source documentation framework that required ongoing maintenance and technical ownership.

  • Platform dependencies needed regular maintenance and upgrades.
  • Docusaurus version upgrades required someone to manage the associated changes.
  • CI/CD workflows involved GitLab, Docker, and Jenkins.
  • Infrastructure changes made by engineering could unintentionally disrupt documentation authoring and publishing.

Publishing workflow dependencies

Jenkins configuration was a recurring bottleneck, as engineers unfamiliar with the documentation workflow occasionally made changes that broke publishing until someone tracked down the issue. Without dedicated ownership of the infrastructure, even small adjustments could stall documentation updates.

Expanding compliance requirements

Following Socure's FedRAMP authorization, the company needed a separate documentation experience for government customers.

Commercial product releases did not automatically mean the same capabilities were available to FedRAMP customers. Maintaining accurate documentation across both environments required ongoing coordination with SMEs to understand product availability and authorization status.

Major product transformation

Following the acquisition of Effectiv, Socure was moving toward a new product architecture under RiskOS.

The company wanted to begin onboarding customers to the new platform, creating an immediate need for a new documentation experience. However, the product was still being adapted and integrated into Socure's platform, with engineers actively developing and changing functionality while I was learning it.

With only three weeks before the holiday period, I had to quickly develop an understanding of the platform while its implementation was still evolving. What I learned one day could become outdated the next as engineers introduced changes to functionality and workflows.

This meant documentation development was happening alongside active product development. I needed to continuously validate my understanding against the latest implementation, test workflows, identify discrepancies, and follow up with engineers to understand changes.

In many ways, I was acting as an additional QA layer, ensuring the documentation I was building kept pace with the product as it evolved.

What this project demonstrates

This project reflects how I approach documentation as a product and take ownership beyond the boundaries of traditional technical writing.

  • Documentation leadership: Taking responsibility for shared documentation operations and infrastructure in an organization without a formal documentation leader.
  • Infrastructure ownership: Managing Docusaurus dependencies, upgrades, and CI/CD workflows involving GitLab, Docker, and Jenkins.
  • Operational reliability: Understanding infrastructure dependencies and protecting documentation authoring and publishing from unintended changes.
  • Compliance awareness: Establishing and maintaining separate documentation experiences for commercial and FedRAMP customers.
  • Cross-functional collaboration: Working with Engineering and SMEs to maintain product accuracy and coordinate infrastructure changes.
  • Product adaptability: Quickly developing expertise in a new platform following a major acquisition.
  • Quality assurance: Validating product behavior and keeping documentation synchronized with an actively evolving implementation.
  • Customer experience: Designing information architecture and onboarding flows around the needs of RiskOS customers.
  • Platform strategy: Evaluating documentation solutions based on both product capabilities and long-term operational sustainability.