Partly - Principal/Staff Product Manager – Infrastructure APIs & Developer Ecosystem
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT
Requirements
• 💻 What you'll own • Partly Rails. The end-to-end transactional job flow - from job creation through estimation, procurement, reconciliation, and close. You own this as a product: opinionated in design, reliable at scale, and compelling as a value proposition for any system that runs on it. Key metrics: API feature coverage of the job flow, jobs processed on Rails APIs, uptime, latency, error rates. • External Integration APIs. The full external API program - API governance, versioning policy, and the standards that define how the outside world connects to Partly. Key metrics: API adoption rate, integration depth, versioning health. • Developer Portal & Experience. The developer platform - documentation, tooling, sandbox environments, and everything a third-party integrator needs to go from first call to production. Key metrics: time to first test job, time to first production job, developer satisfaction. • Developer Ecosystem. The global network of integration partners building on Partly's infrastructure - identifying them, activating them, and creating the conditions for the ecosystem to grow. Key metrics: active external integrations, ecosystem growth rate, partner retention. • Agentic API Evolution. As AI agents become a new class of API consumer alongside traditional system integrations, you own evolving Partly's API offer to serve them - designing for autonomous, context-aware, and reliable agentic usage patterns. Key metrics: agentic integration adoption, reliability under autonomous consumption. • Non-negotiables • Proven experience owning developer-facing API products: API design, versioning, governance, and lifecycle management. • Practical experience building or scaling a developer ecosystem - partner programs, integration networks, or developer communities. • Deep understanding of developer experience as a product discipline: what good onboarding, documentation, and tooling actually look like at each stage of maturity. • Commercial and technical depth - you can engage credibly with engineers on API architecture and translate developer needs into clear business outcomes. • 5+ years owning platform or infrastructure products with clear accountability for adoption metrics, not just delivery. • You build rapid prototypes yourself - with AI-assisted tools, LLM-assisted development, or code - as a first instinct for testing ideas. • Strong analytical instinct: you define the metrics, build the view, read the data, and act on it - without waiting for a data team to hand it to you. • Strong signals we look for • Experience designing APIs for agentic or LLM-based consumption, beyond traditional system integrations. • Familiarity with transactional or workflow APIs in domains such as payments, logistics, supply chain, or insurance. • Experience running a partner or ISV program at scale. • Comfort owning reliability, observability, and non-functional requirements as first-class product concerns. • Founder background, or early employee at a platform-first startup that scaled materially. • You've killed or radically changed something you personally believed in, and can explain why. • Domain knowledge in automotive aftermarket, collision repair, or insurance claims. • Experience scaling developer platforms across multiple geographies. • Experience with product-led growth motions applied to a developer or API product. • Experience building or operating products with meaningful agentic or automation components. • 🧭 How you'll think and operate • "I shipped a sandbox version of the new flow yesterday. Two integration partners have already tried it. Here's what they got stuck on." • "The p99 latency spike on job creation is the highest-priority issue this week — not the feature request in the backlog." • "Here's what the integration telemetry shows. Here's what I think it means. Here's what I'm changing. Here's when I'll know if I'm wrong." • "An agent just tried to consume this API autonomously and failed in a way we didn't design for. That's the most interesting problem we have right now." • Speed, ownership, and judgment are the baseline. What differentiates the best candidates is the ability to operate fluently across both the developer-facing surface - documentation, DX, partner programs - and the infrastructure layer beneath it, and to shrink the distance between intent and outcome.
Responsibilities
• Own your product, end-to-end • Define and evolve the product vision, strategy, and roadmap for Partly's infrastructure and developer platform. • Own the metrics that reflect the health of the Rails transaction layer and the growth of the developer ecosystem - and use them to steer all decisions. • Lead go-to-market alignment for API releases, ecosystem programs, and integration partnerships. • Act as the single accountable owner - for successes, failures, and everything in between. • Stay close to customers • Maintain direct, regular contact with integration partners and developers - not as an escalation path, but as a core weekly input to prioritisation. • Understand the difference between what developers ask for and what they actually need to ship successfully. • Combine qualitative developer feedback with API usage data, integration telemetry, and support signals - and reconcile them. • Build and ship, not just specify • Prototype API experiences, documentation flows, and developer tooling yourself using AI-assisted development - fast and disposable. • Treat the prototype as the hypothesis. Test with real integrators before writing the spec. • Work hands-on with data: define metrics, build dashboards, query logs, read the signals directly. • Lead in the human loop • Partner closely with engineering leads to balance platform capability, developer experience, and technical sustainability. • Align partner success, GTM, and support teams around the ecosystem strategy. • Communicate API roadmap and deprecation decisions clearly and early - external developers depend on stability and deserve advance notice. • Lead in the agent loop • Design APIs and instrumentation with agentic consumption in mind - not as a future consideration, but as a present design constraint. • Define what "working" means for agent-consumed APIs: reliability, observability, graceful failure, and context fidelity. • Think in systems: how does a change to the API surface propagate through every integration downstream? • Raise the bar • Set the standard for API design, documentation quality, and developer experience across Partly. • Help define what an excellent external developer program looks like as the ecosystem scales.
Benefits
• Healthy, Catered Lunches - Enjoy fresh, healthy lunches every workday in our Auckland, Christchurch, London and San Francisco offices. With no meal prep needed, you can eat, connect, and refuel with your team. (And yes, snacks and drinks are always on hand.) • Healthy, Catered Lunches • Healthy Body, Healthy Mind - We care about performing at our peak. Every team member gets a $1,500 annual wellness allowance (or local equivalent) on a Partly-branded card. Use it on things such gym memberships, rock climbing, physio, massage, GP visits, prescriptions; anything that you or your family, need! • Healthy Body, Healthy Mind • Family Comes First - Primary caregivers receive 3 months of fully paid parental leave, plus a flexible return-to-work (four days on full pay for your first three months back). • Family Comes First • Getting Here Is On Us - If you commute to a Partly office or co-working space, choose from a paid 24/7 car park or commute allowance. One less thing to think about! • Getting Here Is On Us • Workspaces That Inspire - Our brand new, architecturally designed offices are built for collaboration and creativity, with great coffee, social spaces, and some of the best cafes a few steps away. • Workspaces That Inspire • Office-First with Flexibility - In cities where we have an office (Christchurch, Auckland, London, San Francisco), we default there every day. This lets us move faster, make better decisions and build strong relationships. We also operate with a very high trust environment, so you can manage your time around your life, and flex your schedule to get your best work done. • Office-First with Flexibility • We Celebrate Together - From weekly happy hours and monthly lunches to quarterly season openers and an annual global offsite, we make time to connect, celebrate, and have fun as one team. • We Celebrate Together • Take time when you need it. We don't ask questions or care if people have a negative leave balance. We work extremely hard and trust our team to take the time they need to recharge. • Take time when you need it.
No credit card. Takes 10 seconds.