Technical Writer , BR-DGE

• Proven experience writing technical documentation for APIs, developer tools, or complex platforms
• Strong written English, with excellent attention to clarity, structure, and audience
• Hands-on experience using Postman or similar tools to exercise APIs
• Solid understanding of back-end concepts such as APIs, authentication, data flows, and environments
• Comfortable working directly with Engineers and Product teams in an agile environment
• Ability to drive documentation proactively, rather than waiting for requests
• Strong organisational skills and ability to manage multiple documentation streams in parallel

Desirable

• We are looking for a Technical Writer to take ownership of our developer and API documentation, with a strong focus on ensuring new functionality is documented clearly, accurately, and on time
• This is a hands-on role embedded within our product and engineering workflows. You will work closely with Engineers and Product Owners to shape, write, and maintain documentation as features are delivered, reducing the gap between development completion and merchant-ready documentation
• The role is proactive by design. You’ll work with a visible pipeline of upcoming features, engaging early with design and implementation to ensure documentation is ready when customers need it
• Establish and run a robust, repeatable process for documenting new product functionality as it is released
• Own the creation of high-quality, merchant-facing documentation for APIs, integrations, and platform features
• Work directly with Engineers during feature delivery to:
• Review design documents
• Exercise APIs using tools such as Postman
• Ask clarifying questions and validate behaviour
• Partner with Product Owners to validate that documentation reflects intended product behaviour, while removing documentation workload from POs
• Maintain and improve documentation structure, clarity, and discoverability within our existing platform (ReadMe)
• Allocate roughly 70% of time to net-new documentation and 30% to cleanup and restructuring of existing docs
• Contribute to defining what “good” documentation workflows look like, and collaborate with stakeholders to simplify and improve publishing processes
• Ensure documentation is timely, accurate, and aligned with release timelines
• Within the first 90 days:
• A clear, reliable process for documenting new features is in place and being followed
• Documentation for new releases is consistently being delivered to a high standard
• Within 6 months:
• The time between feature completion and merchant-ready documentation is significantly reduced
• Documentation quality supports faster merchant adoption and fewer clarification loops with Product and Support
• Beyond:
• Positive feedback about quality of documentation, ease of integration, and our team's contribution to the successful outcomes of our commercial and implementation teams
• Reduction in time spent on request servicing, with self-serve resources enabled to free our Product and Customer Support teams' time for other high-value activity