Technical Writer

Job role: Technical Writer 

Employment Type: Permanent/Full Time

Location: Remote or from the Edinburgh office

About BR-DGE

BR-DGE is an award-winning FinTech founded in Edinburgh. Our platform enables enterprise e-commerce and technology businesses to design, optimise, and scale complex payment infrastructures with confidence.

Since 2018, we’ve been building a modern payment orchestration platform that gives merchants control, flexibility, and resilience across their payment stack. Our customers include household names across travel, retail, and regulated gaming sectors, supported by world-class partners such as Visa and Worldpay.

We operate in a highly regulated, technically demanding environment, where reliability, clarity, and execution quality matter. As our platform and customer base continue to grow, high-quality technical documentation is becoming a critical part of how we ship products and support our merchants and will play a central role in allowing us to scale rapidly. 

About the Role:

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.

What You’ll Be Doing:

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.

What we're looking for:

Core requirements 

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.

Nice to have

Experience investigating issues beyond API usage, such as logs, tracing, or database behaviour.

Background in payments, fintech, or other regulated industries.

Experience improving or redesigning documentation workflows and publishing pipelines.

Hybrid backgrounds such as former engineers, Technical Support Engineers, or API specialists who have moved into documentation.

Tools & Environment:

Documentation platform: ReadMe

API tooling: Postman

Close collaboration with Engineering, Product, and Technical Solutions teams

Access to staging and sandbox environments provided

What success looks like:

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 

What We Offer:

• Flexible, remote-first working
• 33 days holiday including public holidays
• Birthday off
• Family healthcare
• Life insurance
• Employee assistance programme
• Investment in learning and development
• Regular team events and off-sites
• A collaborative culture where documentation is treated as a first-class product