Partner & Integration Operations Lead | Revyse

Get Covered

12d•$80,000 - $100,000

About The Position

Our vendor credentialing product does not work alone. It depends on a set of external systems - business screening, tax information, insurance verification, payments, document processing - and the quality of those connections determines whether a vendor gets verified in two days or in three weeks. This role drives those connections. The commercial relationship, the technical requirements, the data quality, the escalation path, and the handshake between what a partner's API can actually do and what our product promises. It is a narrow role on purpose. You'll own one high-leverage surface completely.

Requirements

3+ years in partner operations, integration management, technical program management, business systems, or solutions and implementation - somewhere you sat between a product team and third-party API providers.
You read API documentation without needing a translator. You can write a clear integration requirement and validate the result.
Experience owning a partner or vendor relationship commercially - SLAs, escalations, contract terms, renewal conversations.
Working familiarity with payment systems (Stripe or comparable) and document processing (OCR or AI extraction).
Strong analytical work. You diagnose with data and you quantify what you find. SQL is a plus.
You escalate early and clearly. When something is broken you say so, with evidence, and you bring a proposed fix.

Nice To Haves

exposure to commercial insurance and certificates of insurance, background screening, or other compliance-heavy operations.

Responsibilities

Own the day-to-day relationship with every third-party service the credentialing product depends on - business screening, tax information, insurance verification, payments, and document processing.
Hold partners to their SLAs. Track turnaround time, data quality, error rates, and cost per transaction. Escalate with evidence, not anecdote.
Read and understand the agreements. Know what we are entitled to, what we are paying for, and where we are not getting what we bought.
Run evaluations when we are considering replacing a partner or adding one.
Translate compliance requirements into integration requirements - what data we need, in what shape, at what point in the workflow, and what should happen when it fails.
Write the specs. Work directly with Product and Engineering to get them built, then validate the result against what the partner actually returns.
Test integrations yourself. Know the API surface well enough to reproduce a problem before you route it to anyone.
Own the change pipeline. When a partner ships a change, you know before it breaks a workflow.
Own the payment operations behind the platform - fees, collection, retries, failure handling, and reconciliation.
Monitor and improve payment success rates. Diagnose failures at the integration level, not just the ticket level.
Own the design of the operational workflows behind enrollment, verification, renewals, and rechecks - the systems, not the staffing. A separate support team runs day-to-day execution; you build what they run on.
Document the process knowledge that currently lives in people's heads.
Use throughput, turnaround, and exception data to find where workflows actually break - then fix the cause, not the symptom.