Product Manager, Platform

Job description

Job responsibilities

• Astra's core API platform: authentication, versioning, pagination, rate limiting, error taxonomy, and the developer contracts that customers build on
• The control plane product: configuration surfaces, rule engines, programmable routing logic, and the levers customers use to customize money movement behavior
• Webhook and event architecture: delivery guarantees, retry logic, event schema design, and the observability customers need to build reliable integrations
• Developer experience: documentation quality, SDK surface, sandbox fidelity, onboarding flows, and the time-to-first-transaction metric
• Platform extensibility: how customers compose Astra's primitives – triggers, conditions, actions – to build complex payment workflows without custom engineering
• Platform reliability and SLA products: how Astra communicates uptime, exposes status, and gives customers visibility into degradation
• Long-term platform strategy: how Astra evolves from a multi-rail API into a programmable payments infrastructure layer, including agentic payment use cases
• Define and maintain Astra's API contract philosophy – versioning strategy, backwards compatibility standards, deprecation policies, and schema design principles

Job requirements

• 6+ years of product management experience, with at least 3 years building developer-facing platform or API products at a technical infrastructure company
• Deep expertise in API design – REST, webhooks, event-driven architecture – and strong opinions about what makes a platform great to build on
• Experience owning a platform roadmap across authentication, configuration, extensibility, and observability layers
• Strong understanding of how infrastructure companies create lock-in through developer experience, not just features
• Comfort reasoning about systems-level tradeoffs: latency vs. consistency, configurability vs. complexity, generality vs. opinionation
• Track record of operating as a principal-level IC – setting direction, influencing without authority, and driving outcomes across engineering and go-to-market
• Exceptional written communication; you can produce a platform spec that is simultaneously a product document and a technical contract
• Payments context is a plus, not a requirement – but intellectual curiosity about how money moves is required