Quadrivia AI

Solutions Engineer

• Design and build resilient, bidirectional integrations with major EHRs
• Implement and maintain HL7v2 interfaces and FHIR R4 / US Core integrations
• Build and operate integration pipelines on InterSystems IRIS
• Handle C-CDA documents, X12 transactions, and the connectivity layer
• Navigate EHR vendor programs end-to-end
• Own reliability of the integration estate
• Guarantee accuracy, patient-matching integrity, and de-identification/PHI handling across every data flow
• Support customer and partner due-diligence and security reviews
• Coordinate multiple parallel, demand-driven integration teams
• Plan capacity and sequence go-lives
• Set integration standards and mentor engineers
• Collaborate closely with Backend, AI, Clinical, and Implementation teams
• Write clean, test-driven, maintainable code

Senior EHR Integration Engineer

Sales

• Prospect into healthcare organizations using your existing network and relationships, or by researching and conducting cold outreach
• Book qualified introductory meetings between target accounts and the Quadrivia sales team
• Claim and work accounts from our curated approved target account lists
• Complete short positioning certifications before initiating outreach
• Track outreach activity and be able to view deal progression through the Quadrivia contractor platform
• Represent Quadrivia professionally and credibly within your network

Sales Professional, US Healthcare

QA Automation Engineer

• Hunt down high-leverage processes. Talk to people across the company, find the manual, repetitive, error-prone work, and rank it by what's genuinely worth automating.
• Pull a workflow out of someone's head and specify it. Most of the job is turning a vague "this is just how we do it" into something precise enough to automate.
• Build the automation. Python and API glue, MCP servers and clients, Claude Skills, agent workflows, and small services where they're needed.
• Instrument what you ship so it doesn't rot silently. Logs, alerts when something breaks, and a way to know whether the automation is still doing its job.
• Drive adoption. Get non-technical teams to trust and use what you've built, train them, and stay close after launch so it sticks.
• Know when to escalate. When an automation needs to become real platform, hand it to the backend team instead of bolting on. Knowing where that line sits is part of the job.

Senior EHR Integration Engineer

Sales Professional, US Healthcare

AI Automation Engineer