Product Manager, Core Integrations & API

CallRail•Atlanta, GA

18h•Hybrid

About The Position

CallRail is looking for a Product Manager to join our team that supports our core integrations, public API and webhooks products. This is a build role. You’ll ship net-new integrations with platforms our customers depend on — automotive and healthcare tools, scheduling systems, workflow platforms like Zapier — and you’ll deepen the ones we already have. You’ll also own the shared service and framework those integrations run on, and the developer-facing API and webhook surface that thousands of customers and partners build on top of. The other half of the job is keeping the ecosystem healthy. Integrations break in ways ad campaigns don’t, and you’ll be the person who decides what gets fixed first. That means working shoulder to shoulder with Support, Sales, and Marketing — they hear about problems before dashboards do, they know which integration is blocking a deal, and they need you to tell them what’s coming and when. This role suits a hands-on, technically fluent PM who wants to ship real integrations, cares about customer product experience, and works in an environment where AI is a daily tool rather than a talking point.

Requirements

3-5 years of product management experience , including meaningful time on integrations, APIs, developer tools, or platform-oriented work.
Background in marketing tech, communications tools, or call tracking ecosystems.
A track record of actually shipping B2B SaaS integrations end to end — not just governing a platform others built on.
Strong technical fluency. You read API documentation comfortably, reason about data models and auth flows, understand webhooks and event delivery semantics, and can scope edge cases with engineers without needing a translator.
Hands-on experience with public or partner APIs — REST, OAuth, versioning, rate limiting, pagination, and webhook reliability patterns.
Demonstrated fluency with AI tools (Claude or similar) in your actual day-to-day product work.
Comfort working directly with Support, Sales, and Marketing — turning their signal into prioritized work and keeping them informed without being asked twice.
Comfort with the unglamorous half of integration work: bugs, migrations, and reliability — and the judgment to prioritize it against net-new.
Ability to prioritize clearly across business goals, customer needs, and technical feasibility, and to explain your reasoning to both engineers and executives.
Experience in Agile teams working closely with engineers and designers.
Excellent written communication. Integration decisions live or die by how well they’re documented.
Familiarity with tools we use: Jira, Confluence, Miro, Looker, Fullstory, Figma.
Use AI daily as a working tool — clustering support tickets to find the real bug patterns, drafting and pressure-testing specs, exploring API data, and building throwaway scripts and prototypes to answer questions faster than a meeting could.

Nice To Haves

Experience building or scaling a developer platform, API program, or developer portal.
Experience with vertical software ecosystems — automotive, healthcare, home services, or legal.
Experience with MCP, agent frameworks, or designing APIs intended for AI consumption.

Responsibilities

Build and deepen integrations: Ship net-new core integrations — new verticals like automotive and healthcare, scheduling and workflow platforms, and the partners our roadmap calls for next. Deepen existing integrations past MVP: fill functional gaps, expand data coverage, and make the ones customers already rely on genuinely good. Own the shared service and framework every integration inherits — data sync, authentication, error handling, and retries — and the tooling that makes the next integration cheaper to build than the last. Own the integrations UI and library: how customers discover, connect, configure, and troubleshoot what we’ve built.
Own the API and webhooks: Own CallRail’s public API and webhooks as a product, not a byproduct: new capabilities, versioning strategy, deprecation paths, and the developer experience around them. Drive parity between our API and webhooks so developers get consistent data and behavior regardless of how they consume it. Own API documentation, the developer dashboard, and the administration and billing experience for API access. Define and monitor the health metrics developers actually feel — latency, error rates, rate-limit behavior, webhook delivery reliability — and act on them.
Prioritize and triage: Own the integrations bug queue. Triage incoming issues, and make the reliability work that keeps the ecosystem healthy visible and scheduled rather than invisible and endless. Make the call on sequencing net-new work against fixes and migrations, and be able to explain that call to anyone who asks. Close the loop with Support — build the intake path that turns ticket patterns into prioritized work, and give them the answers and workarounds they need in the meantime. Keep Sales and Marketing ahead of the roadmap: what’s shipping, what’s fixed, what’s still broken, and what they can confidently sell and promote.
Cross-functional: Write clear, actionable epics, user stories, and acceptance criteria with real technical context and edge cases identified up front. Lead discovery with customers, developers, and internal teams to validate problems before scoping solutions. Partner with Marketing, Sales, and Customer Experience on launches, enablement, and adoption. Represent core integrations and the API in planning cycles and cross-functional initiatives.
Continuous adoption of AI technologies is essential to this role. You will be expected to leverage AI platforms to streamline operations, solve complex problems, and stay ahead of industry benchmarks.
Build your own leverage rather than waiting for it — writing Claude skills, agents, and internal workflows that make you and your team faster.
Think about CallRail’s platform as something AI agents will consume, not just humans. MCP servers, agent-friendly API design, and tool-calling patterns are increasingly part of what a modern integrations platform is expected to offer, and you’ll help shape our point of view there.
Stay genuinely current. The tooling changes every few months, and we want someone curious enough to keep up and pragmatic enough to know when a new tool actually helps. We’re looking for evidence that you’ve already changed how you work because of these tools — not just enthusiasm about them.