Skip to content
Pricing
Cohere HealthVerified from Cohere Health's careers page · Greenhouse

Integration Support Analyst

  • USA - Remote
  • 3+ Years
  • Posted Nov 20, 2026

Visa sponsorship: the posting does not say.

Cohere Health had H-1B petitions approved for 22 workers in fiscal year 2026 (USCIS). That is history, not a promise for this role. See the record

At a glance

Integration Support Analyst at Cohere Health, based in USA - Remote. Experience level: 3+ Years. Posted on 20 November 2026, read from Cohere Health's own careers page (Greenhouse), which RealAnalystJobs re-checks daily and removes the role when it closes. Cohere Health has approved H-1B petitions on USCIS record (employer-wide, not a promise for this role).

Similar roles on RealAnalystJobs, as of 21 November 2026

About this role

Opportunity Overview: We are seeking an Integration Support Analyst to join Integration Operations (INTOPS), the Level 3 support function within Integration Services for Cohere Health's payer and provider integrations. In this individual contributor role, you will own complex production integration issues from first escalation through root cause, recovery, and verified close. L1 and L2 resolve known, documented issues; INTOPS takes what remains. You will trace failing transactions across the integration flow, identify exactly where behavior stopped matching the agreed design and determine which team owns the fix, handing Product, Development, Data, Engineering or the client a narrowed, evidence-backed problem statement. This role is production support and incident resolution, not implementation delivery or code development. It is an opportunity to apply deep healthcare interoperability expertise to high-impact production problems, strengthen client confidence, and shape how a growing support function operates, including the triage guides, error-classification rules, and ownership paths that keep known issues from reaching L3. What you’ll do: Own L3 triage for production integration issues: confirm impact, isolate a failing example, find the last successful and first failed step in the flow, and compare actual behavior against the integration contract, mapping, or design. Verify delivery end to end, because a success response on our side does not prove the downstream system received or accepted the transaction. ● Determine ownership rather than simply routing tickets: separate where an error surfaced from where the defect originated, triage per authorization rather than per ticket when one incident has more than one owner, and rule out expected or configured behavior before declaring a defect. ● Write engineering-ready escalations that state the client, environment, identifiers, exact error, expected versus actual behavior, failure point, affected volume, ownership rationale, whether a re-trigger is safe, and a proposed fix or specific open question. Attach proof to every handoff, such as log identifiers, queries, and payloads, and open paired support and engineering tickets with a named owning team for confirmed defects. ● Troubleshoot FHIR R4 APIs (including Da Vinci CRD), X12 278, flat-file and SFTP exchanges, event-driven outbound pipelines, and OAuth, token, certificate, and SSO connectivity failures. ● Lead recovery and reconciliation: decide when a retry or re-trigger is appropriate and when it will not help (a re-trigger resolves timing failures, not bad data or bad state), identify every affected transaction, replay them safely after a fix ships, and confirm the downstream system accepted them. ● Own each ticket through verified resolution: keep the support ticket as the client-facing record until the fix is confirmed in production rather than when engineering merges, and make sure alerts are not closed while failures continue. ● Coordinate incident response for client-impacting issues, including stakeholder updates and SLA-aligned tracking. ● Monitor integration health using logs, dashboards, alerts, and observability records, and turn recurring failure patterns into systemic fixes, monitors, and known-error rules. ● Reduce manual work by maintaining error-classification rules and contributing to automated retry, reporting, validation, and alerting tooling, so recurring errors are handled by rule instead of one ticket at a time. ● Enable L1 and L2 by writing and maintaining short "101" triage guides, runbooks, known-issue references, and escalation checklists, and coach support analysts so repeatable issues are resolved earlier in the support path. ● Communicate technical findings clearly to clients, Client Success, and internal partners, and support error reporting and fallout analysis. ● Protect PHI in all support work: redact member identifiers and other PHI from tickets, chat, and AI-assistant prompts. ● Drive measurable improvements in time to resolution, recurring error rates, escalation quality, and SLA adherence. What you’ll need: • 3+ years of experience in payor and provider integration support, implementation, or technical operations, preferably in healthcare. • Strong working knowledge of HL7 FHIR R4 and X12 EDI, with 278 strongly preferred. • Experience troubleshooting REST APIs, OAuth 2.0 and TLS connectivity, SFTP and file-based integrations, and event-driven or message-based systems. • Proficiency querying and analyzing integration data with SQL, using Athena or similar tools. • Hands-on experience with logging and monitoring tools such as Datadog, AWS Athena and CloudWatch Logs Insights, or Kibana. • Evidence-based approach to root cause analysis, including tracing a transaction across multiple systems and teams and confirming what the downstream system actually received. • Sound judgment on ownership and recovery, including recognizing when an issue is not an integration defect, when the behavior is expected or configured, and when a retry will not fix it. • Excellent written communication, including concise escalations that engineers can act on without a follow-up meeting. • Ability to own critical, client-impacting issues independently and explain findings to technical and non-technical audiences. • Experience working in a ticketing or service-desk tool such as Jira Service Management. • Rigor in handling PHI and production data. • Bachelor's degree in Computer Science, Engineering, Information Systems, or equivalent professional experience. Bonus: • Experience with payer or provider integrations, prior authorization or utilization management workflows, or CMS interoperability requirements such as CMS-0057-F. • Familiarity with Da Vinci implementation guides (CRD, DTR, PAS, CDex). • AWS experience, including S3, Lambda, ECS, DynamoDB, and Transfer Family. • Experience building support automation or error-management tooling, using Python

Description from Cohere Health's public careers feed, reproduced so you can read the role here. Apply on the company's own site; RealAnalystJobs never submits anything for you.

Cohere Health

10 open analyst roles on RealAnalystJobs

More roles at Cohere Health
Get new analyst roles every day on Telegram. India, the US, Europe and remote, one tap to follow, no sign-up.

Hiring analysts? List your role free.