Product Manager, Integrations & API (Senior/Staff/Principal)

PRODUCT MANAGER, INTEGRATIONS & API (SENIOR/STAFF/PRINCIPAL) Location: Hybrid (Nashville, TN) or Remote (US), Remote (Canada) Reports to: Head of Product & Engineering THE ROLE This role owns how VITL connects to the outside world: the EHR/EMR and practice-management systems clinics use, the pharmacy network that fulfills orders, and the public API that partners and customers build on. Expect a full-spectrum day: a technical call with an EHR partner's developer in the morning, a deal-structuring conversation with Business Development in the afternoon, and a call with a pharmacy's operations lead that evening to unblock a go-live. You sit at the center of the rectangle (BD, sales, engineering, ops) and you are accountable for making the math work across all four sides. An engineering team handles the deep implementation; your job is to create the specificity and strategy that lets that work land. WHAT YOU’LL OWN - EHR/EMR integrations. Own the integrations that connect VITL to the EHR/EMR and practice-management systems clinics use. You will get to know how practitioners and their teams actually work, then build integrations they can lean on. - Pharmacy integrations. Own the integrations that connect VITL to our pharmacy network. You will work shoulder to shoulder with pharmacy operations teams, turning the messy realities of fulfillment into something dependable that patients feel without ever seeing it. - Public API and developer experience. Own everything partner developers touch: the API, SDKs, docs, sandbox, webhooks, auth flows, and data models. The bar is that a partner developer can self-serve from first call to first successful test transaction without an engineer holding their hand. - Integration roadmap, intake, and strategy. Own the full intake funnel, develop a prioritization framework, and the roadmap that falls out of it. Weigh demand against commercial value and engineering cost to decide what we build and in what sequence. Hold the line against randomization to protect existing high-priority commitments. - Commercial partnership with BD and sales. For every partnership that touches integrations or the API, you are the technical-economic voice in the room: what is buildable, by when, at what cost, and under what constraints. You will partner directly with sales, business development, and engineering on every commercial conversation where an integration is the fulcrum. - Scoping and delivery. Run technical discovery calls with counterparts at partners. Produce discovery summaries that hold up, and carry them through to shipping. Negotiate realistic timelines and commitments, and drive phased rollouts with staged customer comms. - Partner relationships and escalations. Define pilots, run validations, and build the go / no-go checklist. After launch, you quarterback each integration through quality, migrations, incidents, and escalations. Track adoption, identify stuck partners, and feed gaps back into the roadmap. WHAT SUCCESS LOOKS LIKE - Intake and prioritization run themselves within 90 days. Every integration request and partner ask lands in one funnel with a documented prioritization framework. BD, sales, and engineering align on what we are building and what we are not. - The team trusts your scoping. Because of your technical scoping, post-signature surprises are rare because you asked the hard questions up front. - Integrations ship and stick. Each launched integration hits its go-live date, clears its quality bar, and shows real adoption inside 60 days. Stuck partners get unstuck quickly. - The integration engine compounds. By month 12 you have built the intake, scoping, rollout, and post-launch playbooks that let the next partner onboard faster than the last. WHAT YOU BRING - Integrations and API depth. 5+ years shipping integrations, developer-facing APIs, or large-scale partner connections. You have run the full lifecycle from discovery to production and you know where the landmines are. Bonus points…