About Obin AI
Obin AI is an AI-native startup building the operating platform for institutional finance back- and middle-office work — starting with private equity fund servicing, insurance claims, and private credit valuation and portfolio monitoring. We combine deep domain expertise (sourced from a global network of senior operating SMEs) with AI/agentic systems to replace manual, judgment-heavy workflows like corporate-action processing, claims adjudication, and NAV/valuation oversight. Our platform runs natively inside customer cloud environments and speaks open protocols (MCP, A2A) so agents can be extended, composed, and integrated rather than locked into a single vendor stack. We're early, moving fast, and building for customers — and developers — who will not tolerate a product that "mostly" works.
The Role
We're hiring a Platform PM to own Obin's platform and make it the easiest, best-documented, most trusted way to build agentic workflows in financial services. This is a hybrid product + devrel role: you'll define the roadmap for our APIs, SDKs, and protocol integrations (MCP, A2A) as a product in their own right, and you'll personally write the documentation, sample code, and technical content that get internal teams, customer technical stakeholders, and (eventually) external partners building on Obin quickly and correctly. You'll work at the intersection of engineering, forward-deployed delivery teams, and the outside developer/technical community — and as the platform and ecosystem grow, you'll build out the function.
What You'll Do
- Own the platform-as-product roadmap: APIs, SDKs, protocol surfaces (MCP, A2A), and the "extension points" that let internal delivery teams, customer technical staff, and partners build on Obin without waiting on core engineering.
- Be the voice of the developer — internal forward-deployed engineers, customer IT/architecture teams, and (as we open up) external partners — bringing their friction points and feature requests into a coherent roadmap, not just a backlog of tickets.
- Partner closely with Engineering on the technical trade-offs of a protocol-driven platform: what belongs in the core orchestration layer (Robin Harness) versus what should be exposed as a stable, documented extension point; versioning and backward compatibility; and where opinionated defaults should override low-level flexibility.
- Build the technical content that makes the platform legible: quickstarts, reference architectures, sample agents, reusable blueprints, and API/SDK documentation — written and maintained by you, not just commissioned.
- Run developer relations end-to-end: technical blog posts, conference talks and demos, workshops for customer technical teams, and community engagement in the agentic-AI and MCP ecosystems.
- Define and own developer experience metrics — time-to-first-successful-integration, documentation satisfaction, support-ticket deflection, protocol adoption — and treat them with the same rigor as customer-facing product metrics.
- Champion inner-sourcing and technical advocacy internally, so reusable blueprints and reference architectures actually get adopted across delivery teams instead of every engagement reinventing the wheel.
- Operationalize strategy into shippable increments, running a tight build-measure-learn loop on the developer/platform surface and adapting as adoption data comes in.
Must-Haves
- 5+ years in product management, with meaningful time specifically in platform, API, or developer-tools product roles — you've shipped things developers actually adopted, not just documented.
- Direct, hands-on developer relations or technical evangelism experience: you've personally written documentation, sample code, or technical content that developers used to successfully integrate with a product.
- Genuine technical fluency: comfortable reading and writing code, understands APIs/SDKs/protocols at a real level (concepts like REST, webhooks, auth, or newer agent-to-agent/tool-use protocols such as MCP), and can have a credible technical conversation with engineers as a peer, not an "arms-length" requester.
- Experience building for a technical audience (developers, solution architects, technical integrators) as distinct from building for business end-users — you understand that "good docs" and "good DX" are product features, not an afterthought.
- 0-to-1 platform or developer-program building experience at a startup or new business line — comfortable defining what "the platform" even is before there's a mature audience asking for it.
- Strong written and verbal communicator: you'll personally author docs, blog posts, and conference talks, and represent the platform externally.
- Comfortable with ambiguity and a small team — this is a builder's role, not a steady-state maintenance role.
Good-to-Haves
- Direct experience with agentic-AI or LLM tooling ecosystems — MCP, A2A, LangChain, AutoGen, or similar — as a builder, integrator, or evangelist.
- Prior experience running a developer community, meetup, open-source project, or contributing to a protocol specification.
- Public speaking or conference track record (technical conferences, meetups, webinars).
- Background in financial services or another regulated/compliance-sensitive enterprise software domain, where auditability and controls shape what a "good" developer experience even looks like.
- Experience partnering with or enabling a network of solution architects/forward-deployed engineers (vs. a purely self-serve developer audience).
- Track record of scaling a platform/devrel function from a first hire to a small team.
- Network within the agentic-AI, MCP, or AI-in-financial-services developer ecosystems.