Technical Writer Product Documentation

”

This is a remote position.

**Engagement: 6-month contract, with potential conversion to part-time/FTE based on remaining scope at contract end

**About the Role

Saasify (by Spektra Systems) is a B2B SaaS platform helping ISVs manage cloud marketplace transactions, co-sell workflows, private offers, and partner funding programs across AWS, Azure, and GCP. Were hiring a technical writer to build the foundational layer of product documentation we currently lack: API references, integration guides, and end-to-end user journeys across our core modules.

This is not a marketing or content-writing role. You will not be writing launch announcements, blog posts, or campaign copy. You will be documenting how the product actually works for ISVs, partners, and internal teams who need accurate, current reference material.

**What Youll Document

• API and integration documentation for our core modules: CSP listing and transaction workflows, co-sell registration and status tracking (AWS ACE, Partner Center), private offer automation, partner funding and incentives, and CRM sync (Salesforce and HubSpot)
• End-to-end user journeys/flows for each core workflow currently a significant gap; today we only have integration-level documentation, not journey-level
• Structured FAQ and self-serve reference content (replacing an outdated, unstructured FAQ)

• Documentation that stays accurate as we ship updates (Funding, Co-sell, and Marketplace modules over the coming months) and as AWS/Azure/GCP platform capabilities evolve

  Requirements - Proven experience writing technical/API documentation for a B2B SaaS product (portfolio or samples required) - Comfortable reading API specs and working directly with engineering to verify accuracy not writing from assumptions - Experience documenting integration-heavy or workflow-heavy products (marketplace, CRM, or partner-ecosystem experience is a strong plus, though not required) - Ability to work independently against a backlog with minimal hand-holding, while flagging ambiguity rather than guessing - Strong bias toward accuracy over polish comfortable flagging when a stated capability isnt actually confirmed/built, rather than documenting it as-is

  **Nice to Have
  - Familiarity with Cloud Marketplace, Partner Central/ACE, Azure Partner Center, or GCP Producer Portal - Experience with docs-as-code tooling or structured documentation platforms

  ","********
  

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.