Skip to content

JD — Technical Writer

Owner Classification Review Date Status
People Operations Internal April 2027 Active

Job Description: Technical Writer

Department: Technology & Digital — Digital Office
Reports to: Digital Office Lead

Role Overview

Simpaisa has a documentation-first culture. The Ways of Work, 79 Architecture Decision Records, 74 technical standards, SDLC v2.0, and the Operating Model are all live in Confluence — and they represent a strategic commitment: knowledge concentrated in individuals is a risk, knowledge in documentation is an asset.

The Technical Writer makes that commitment real. This is not a role that tidies up documentation after engineers are done. It is a role embedded in delivery, working with squads, architects, and the Digital Office to produce documentation that is accurate, usable, and maintained. A runbook that nobody can follow is not documentation. API documentation that doesn't match the actual API is worse than no documentation.

Key Responsibilities

  • Write and maintain technical documentation across Simpaisa's technology estate: API references (OpenAPI), integration guides, runbooks, operator onboarding guides, release notes, and SDLC artefacts.

  • Collaborate with Solution Engineers and Solution Architects during SDLC Phase 5–6 to produce documentation as part of delivery — not after the sprint closes.

  • Own the structure and quality of technical content in the Confluence Digital space: enforce standards, identify gaps, and maintain the documentation architecture.

  • Work with Production Engineering to ensure runbooks are accurate, complete, and tested — a runbook is only useful if an on-call engineer can follow it at 3am without context.

  • Maintain API documentation in sync with code: coordinate with engineering teams to ensure OpenAPI specs and integration guides reflect the current production behaviour.

  • Write partner-facing content: onboarding documentation, integration guides, and webhook specifications for merchants and operators.

  • Contribute to the Architecture space: help architects produce clear ADRs, architecture diagrams with captions, and standards documentation that engineers can implement from.

  • Enforce the writing and documentation standards in the Ways of Work.

  • Identify and close documentation gaps — prioritise by operational risk (undocumented corridors, runbooks that don't exist).

Required Skills and Experience

  • Technical writing: Proven experience producing technical documentation for software products — API documentation, runbooks, integration guides, user-facing content. Portfolio required.

  • API documentation: Familiarity with OpenAPI/Swagger specification format. Experience writing API reference documentation that developers can actually use.

  • Confluence and Markdown: Proficiency in Confluence for structured documentation. Markdown for code-adjacent content. Ability to maintain a large, organised documentation space.

  • Payments/fintech (preferred): Experience documenting payment APIs, financial services integrations, or regulated technical products is a strong advantage.

  • Collaboration: Ability to extract information from engineers and architects who are time-constrained and sometimes reluctant documenters. Does not wait to be given content — goes and gets it.

  • Attention to detail: Technical accuracy is non-negotiable. Incorrect documentation causes real incidents in a payment system.

  • Plain English: Ability to write clearly for multiple audiences — a senior engineer reading an ADR, a junior engineer following a runbook, and a merchant reading an integration guide are not the same reader.

General Requirements

  • Bachelor's degree in English, Communications, Computer Science, Engineering, or a related field.

  • 3+ years of experience in technical writing for software or platform products.

  • Portfolio of technical writing samples demonstrating API documentation, runbooks, or integration guides.

What We Offer

  • Competitive salary benchmarked to your local market.

  • An organisation that genuinely values documentation — this role is embedded in delivery, not bolted on.

  • Broad exposure across the entire technology stack — every squad's documentation is yours to care about.

  • Flexible hybrid working.