Senior Technical Writer - Solutions Engineering *EU​/UK remote* (m​/f​/d

ABOUT US

Pliant is a European fintech specializing in B2B payment solutions. Our modular, API-first platform helps businesses streamline spending, improve cash flow, and integrate payments into their financial workflows. Designed for industries with complex payment needs, such as travel and fleet, Pliant enables greater efficiency, control, and profitability.

We serve two primary customer segments:

• Companies looking to optimize operational processes through intuitive apps and APIs, gaining control, automation, and financial flexibility through extended credit lines.
• Businesses such as financial software platforms, ERP providers, and banks that want to launch or enhance their credit card offerings using Pliant’s embedded finance and white-label solutions.

Founded in 2020 and headquartered in Berlin, Pliant supports over 4,000 businesses and more than 20 partners globally. As a licensed e-money institution (EMI), we issue credit cards in 11 currencies across more than 30 countries, helping companies streamline and simplify payments.

Learn more at

As Senior Technical Writer - Solutions Engineering EU/UK remote (m/f/d), you will own how developers, customers, and partners experience Pliant through our documentation. Our API and developer documentation is one of the most important brand and product assets we have as an infrastructure‑focused B2B fintech; customers and partners judge our platform by it, and we want it on par with the very best in the industry.

You will lead a full overhaul of Pliant’s developer documentation: rebuilding the information architecture from the ground up, raising consistency and quality across the entire surface, and unifying our Direct and Partner API documentation into a single coherent Pliant API story that works for both direct customers and embedded‑finance partners.

This is not a write‑things‑after‑launch role. You will work embedded with Product and Engineering, reading code, calling endpoints, validating integration flows end‑to‑end, and act as the engineering partner who turns complex payment infrastructure into documentation developers genuinely enjoy using. You will turn tribal knowledge that today lives in the heads of engineers, solution engineers, and product managers into durable, well‑structured content that lets customers and partners integrate faster and with fewer back‑and‑forth.

This role sits within Pliant’s Solutions Engineering team and reports to the Head of Solutions Engineering.

• Own Pliant’s developer documentation end‑to‑end: API reference, guides, recipes, quick starts, and conceptual content for both direct customers and embedded‑finance partners.
• Lead a full rework of our information architecture, designing structures around the jobs developers and integrators are trying to get done, so each audience finds their path quickly.
• Drive the unification of our Direct and Partner API documentation into one coherent surface as the underlying APIs converge into the Pliant API.
• Validate documentation hands‑on: read code and API specs, call endpoints, run integration flows, and surface gaps, inconsistencies, and rough edges before customers or partners do.
• Establish and uphold documentation standards, voice and style guide, contribution model, review process, so engineers and PMs can contribute consistently with you as the editorial owner.
• Partner with Product and Engineering on API governance, pushing for consistent naming, error handling, and behavior across endpoints, and feeding learnings from documentation work back into the platform itself.
• Shape and improve our developer portal and docs tooling so publishing is fast, content is easy to maintain, and the reader experience is best‑in‑class.
• Use modern AI tooling as a leverage point, to draft, restructure, identify blind spots, and keep large surfaces of content consistent, while owning quality, accuracy, and editorial judgment yourself.
• Define and track quality signals such as time‑to‑first‑successful‑API‑call, support deflection on documented topics, content freshness, and doc‑related integration friction, and use them to prioritize work.

• 5+ years of technical…