▪Partner with the other integrations PM on the shared design patterns every integration inherits — data sync, authentication, webhooks, and third-party APIs — and make sure the next integration is cheaper to build than the last.
▪Stay current with partner platform roadmaps and the shifting privacy and measurement landscape, and bring a point of view on what it means for our customers.
Bring AI into the product
▪Identify where AI meaningfully improves the integration experience — intelligent field mapping, automated setup and diagnostics, enriched data pushed into partner systems, self-healing syncs — and build the case for what's worth investing in.
▪Shape how CallRail's integration data is consumed by AI agents and assistants, as customers increasingly expect their systems to be queryable and actionable by AI rather than only by humans.
▪Know the difference between an AI feature that holds up in production and one that demos well, and be willing to say so.
Prioritize and measure
▪Monitor success metrics, product health, and user feedback, and use them to continuously refine your domain.
▪Make the call on sequencing net-new work against fixes and migrations, and be able to explain that call to anyone who asks.
▪Keep the unglamorous half of integration work — bugs, migrations, reliability — visible and scheduled rather than invisible and endless.
Cross-functional
▪Partner with other product teams whose features depend on your integrations — most often Voice Assist, where the quality of a CRM or scheduling integration directly determines what our AI agents can actually do for a customer. Treat your domain as a platform other teams build on, and sequence your roadmap accordingly.
▪Work closely with Product Design on the integration experience — setup and authentication flows, field mapping, error and reconnection states — where most of the design difficulty is in making genuinely complex configuration feel simple.
▪Write clear, actionable epics, user stories, and acceptance criteria with real technical context and edge cases identified up front.
▪Partner with Marketing, Sales, and Customer Experience on launches, enablement, and adoption of new integrations.
▪Close the loop with Support — turn ticket patterns into prioritized work, and give them answers and workarounds in the meantime.
▪Represent the integrations domain in planning cycles, executive updates, and cross-functional initiatives.
What You'll Need
▪5+ years of product management experience, with 2+ years focused on integrations, partner ecosystems, or platform-oriented work.
▪Demonstrated AI fluency in your day-to-day practice. You use AI tools to accelerate research synthesis, competitive analysis, spec drafting, data exploration, and prototyping — and you can speak specifically about what you've changed in how you work, not just which tools you've tried.
▪A track record of shipping B2B SaaS integrations end to end—CRMs, ad platforms, marketing automation, analytics, or communication tools. Martech experience is preferred.
▪Strong technical fluency. You read API documentation comfortably, reason about data models and auth flows, and scope edge cases with engineers without needing a translator. Deep API design experience isn't required, but you need to know this territory well enough to make good calls about rate limits, sync behavior, and failure modes.
▪Proven ability to manage complex product surfaces across partner APIs, webhooks, OAuth, and data syncing.
▪Experience building product surfaces that other product teams depend on — negotiating roadmaps with peer PMs, making commitments you can keep, and saying no in a way that keeps the relationship intact.
▪Ability to prioritize clearly across business goals, customer needs, and technical feasibility, and to explain your reasoning to both engineers and executives.
▪Comfort working directly with Support, Sales, and Marketing — turning their signal into prioritized work and keeping them informed without being asked twice.
▪Experience in Agile teams working closely with engineers and designers. We flex to optimize how the team works best together.
▪Excellent written and verbal communication skills. Integration decisions live or die by how well they're documented.
▪Familiarity with tools we use: Jira, Confluence, Miro, Looker, Fullstory, Figma.
Nice to Have
▪Hands-on experience with ad platform measurement — offline conversion imports, value-based bidding, consent and privacy changes, and how signal loss affects attribution.
▪Hands-on experience with CRM data models and lifecycle — lead and contact objects, custom fields, activity logging, and the realities of syncing into a customer's existing workflow.
▪Experience shipping an AI-powered feature to production and owning its quality, cost, and evaluation over time.
▪Experience with MCP, agent frameworks, or designing APIs intended for AI consumption.
▪Experience in marketing tech, communications tools, or call tracking ecosystems.
▪Background working with public APIs and/or developer experience tools.
Working With AI at CallRail
AI is core to how our product team operates, and we expect it to be core to how you operate. We use Claude across discovery, spec writing, data analysis, prototyping, and internal tooling, and we're actively building AI capabilities into the product itself. In this role you will:
▪Use AI daily as a working tool — clustering support tickets to find the real bug patterns, drafting and pressure-testing specs, exploring integration data, and building throwaway scripts and prototypes to answer questions faster than a meeting could.
▪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.
If you do not meet all the requirements listed, we still encourage you to apply! No job description is perfect, and we may also have another opportunity that aligns with your skills and experience.
Additional Perks
▪Healthcare (one option covered at 100% for employees), Dental & Vision Coverage
▪Competitive HSA with company matching
▪Paid parental leave
▪Flexible vacation policy
▪401K options with company dollar-for-dollar match
▪Employee stock options available from day one
▪$2,000 annual educational allowance
▪Catered lunch every Tuesday * an in-office perk
▪MARTA transportation or office parking expenses covered
▪Employee charitable donation company match, up to $500 annually
▪Regular company outings and events
▪Hybrid work options with $500 office stipend to set up your home office
▪Designated bike storage
Learn more: https://www.callrail.com/about/
You Are Welcome Here
CallRail understands that valuing diverse creative practices and forms of knowledge are crucial to and enrich the company's core mission. We encourage applications from everyone, including members of all equity-seeking communities, such as (but certainly not limited to) women, racialized and Indigenous persons, persons with disabilities, and persons of all sexual orientations and gender identities and expressions. In your application, please feel free to note which pronouns you use (For example - she/her/hers, he/him/his, they/them/theirs, etc).
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.
▪** This position is based out of our Atlanta office. Through December 2026, employees are expected to work in the office on Tuesdays and Thursdays.
Beginning in January 2027, CallRail will transition to a 3 day hybrid work model. Employees will work in the office on Mondays, Tuesdays, and Thursdays.