Why this role exists

For a payment-infrastructure company, the product is in large part the API. Developers are both the buyers and the daily users, and the quality of the APIs, SDKs, docs, sandbox, and integration path is the product's real surface. This role owns the developer's journey from first API call to production and scale, the difference between a developer who integrates in an afternoon and one who gives up before their first successful transaction.

What you'll own

• The roadmap for the developer experience: integration flow, SDKs, documentation, sandbox, error handling, and time-to-first-successful-call.
• Developer activation and retention as headline metrics, from sign-up to first production transaction and beyond.
• Discovery grounded in developer behavior: integration analytics, support and community signals, and direct developer research.
• Partnership with Engineering on API design and DX standards, and prioritization of DX debt against new capabilities.
• Clear communication of trade-offs to senior stakeholders, and translation of platform changes into a coherent developer-facing experience.

How you will work

You report to the Product Design & UX Director for Customer Lifecycle and work most closely with Engineering, whose API and platform decisions shape the experience you own. Part of your early work is helping define where developer-experience ownership sits, since this surface has not had a dedicated product owner before. You are the strategic owner of the developer journey from first API call to production. Your time splits between developer discovery and roadmap delivery, with constant engineering partnership. The domain works from validated findings rather than assumptions and values direct, candid critique.

What we're looking for

• PM experience with API, platform, or developer-facing products. You have owned products where developers are the user.
• Genuine technical fluency. You can read API docs and discuss schemas, auth, and webhooks with engineers, here this is a requirement, not a nice-to-have.
• Demonstrated empathy for developer workflows. You understand how developers actually work and where they get stuck.

A strong plus: a background as a developer, or having built SDK, docs, or DX products; payments or fintech experience.