Docs Team Lead

Payabli is the Intelligent Fintech Operating System for software platforms. If you are a software company, you are a fintech company, and Payabli is your operating system. Built by payments industry and SaaS veterans and powered by its own models, Payabli gives platforms everything they need to embed, manage, and monetize financial services through a single developer-friendly API spanning Pay In, Pay Out, and Pay Ops. Intelligence is not a layer on top, it is the foundation, expressed through Amigo™, Payabli's native AI Agent Suite, and a growing set of capabilities that make payment operations smarter and more autonomous.

Payabli gives software companies PayFac capabilities without the heavy lift, administrative burden, or cost of becoming a payment facilitator themselves. With PayFac-as-a-Service, embedded payment acceptance and issuance, and intelligent payment operations, platforms turn payments into a meaningful revenue stream while staying focused on their core product.

Payabli is backed by world-class fintech investors including QED Investors, Fika Ventures, TTV Capital, and Bling Capital, and was recently named to the Forbes Fintech 50.

For more information, visit payabli.com.

About the role

Payabli’s docs are how partners integrate with us. We want Payabli to be the easiest payments company to integrate with, and documentation is a big part of that. We’re a small, high-ownership team situated alongside the Product and Engineering teams. We treat documentation as a product, and we write for humans and for the AI agents developers now build with.

As Docs Team Lead, you’ll set the direction for our developer and product docs. You’ll lead a team of two technical writers and stay hands-on. You’ll write, review, build tooling and own the API reference. This is a player-coach role. Expect to spend about three quarters of your time on your own technical work and a quarter leading the team.

You’ll report to CTO. This role is remote.

What you’ll do

Lead the team

• Manage and mentor two skilled technical writers. Hold 1:1s, develop careers, and keep ownership areas clear.

• Trust people to own their work. Unblock them fast, and protect the team from burnout.

• Run the team’s rituals, including quarterly goal setting, backlog grooming, the PTO and coverage plan, and the culture work, such as writing workshops and blog posts.

Own the developer docs

• Own the API reference for our embedded payments API across Pay In, Pay Out and Pay Ops. It’s a multi-file OpenAPI 3.1 source.

• Own information architecture, docs CI/CD, and our style guide and linting rules.

• Use AI agents in your own daily workflow, with human review gates on everything they produce.

• Help review PRs that touch the docs before they go to subject matter experts. You’re the last human gate on quality.

Run docs operations

• Triage incoming engineering and product work every day, and turn it into docs tickets with priorities and ship dates and delegate to the team.

• Ship docs with every monthly production release, including the API changelog, release notes and the docs each feature needs to launch.

• Hold the team to its published SLAs and release tiers, and keep stakeholders informed when something slips.

Own our agentic resources

• Own our public agent skills plugin, which partners install in their coding agents. Keep it accurate as the API changes, using the evals that test it across several agents.

• Own the skills, agent instructions, and agent tooling our Docs team depends on.

Measure and report

• Publish a monthly State of the Docs report from product analytics, AI chat and search data.

• Track team velocity, post-release docs work and AI answer coverage, and set targets for each.

What you bring

Must have

• 8+ years in technical writing or developer documentation, with real API reference experience

• Experience leading or mentoring technical writers

• Deep OpenAPI experience, plus docs-as-code workflows with Git, pull requests, CI and Markdown/MDX

• Ability to read API responses, write scripts (TypeScript or Python) and build docOps tools

• Hands-on experience using AI coding agents in a docs workflow, and judgment about where they fail

• A habit of verifying everything, and saying “I don’t know yet” instead of guessing

• Clear written communication, async-first

Nice to have

• Payments or fintech experience, such as card processing, ACH, payouts and merchant onboarding

• Experience with Fern or a similar docs and SDK platform

• A portfolio that shows API docs you wrote and docs tooling you built (We strongly prefer candidates with a portfolio site.)

How the docs team works

• Users first. Our docs should help partners get in, get out and get back to what matters to them.

• Safe hands. We want to be the most dependable team in the company. We don’t guess, and we flag what we can’t verify.

• Written and async by default. Questions go in public channels. Feedback on work happens in PRs and tickets.…