Senior Software Engineer, Integrations

We’re Scan.com, the digital health scale-up making diagnostics accessible, fast, and transparent. Our technology speeds up diagnoses for timely treatments, improving healthcare outcomes for hundreds of patients each day.

We're doing diagnostics differently, with solutions tailored to both patients and providers, all backed by our technology and world-class customer operations team. Our B2C marketplace simplifies booking a scan, making it as straightforward for patients as booking a hotel. Our B2B platforms provide live scheduling at the point of care and harness AI to ease workflows for physicians, attorneys, and providers.

We're looking for a Senior Software Engineer, Integrations at an exciting time. We've successfully launched multiple platforms and products, raised over $100M in VC funding, reached profitability, and have a growth trajectory of over 100% YoY.

WHAT YOU WILL BE GETTING INVOLVED IN

Scan.com's integration layer is mission-critical infrastructure. We interface with hundreds of imaging centers and health systems operating disparate, often decades-old systems — RIS platforms built on legacy protocols, HL7 v2 feeds with idiosyncratic vendor dialects, and hardware gateways running in constrained clinical environments. On the demand side, we connect to modern EHR APIs, third-party referral networks, and portal integrations that must work reliably at scale.

As a Senior Software Engineer, Integrations, you will architect and build the systems that make these connections robust, observable, and extensible. This problem area requires genuine passion for legacy system integration patterns, message transformation pipelines, and the operational discipline to maintain high-reliability infrastructure against the entropy of the real world.

As a scale-up business, you can expect your role to develop over time. Here are some of the types of things you could be getting involved in:

• Design and implement HL7 v2 transformation pipelines — parsing, normalizing, enriching, and routing ADT, ORM, ORU, SIU, and MDM message types across heterogeneous RIS and EHR systems with non-standard vendor extensions.

• Build and maintain integration connectors for modern and legacy imaging center RIS systems.

• Architect fault-tolerant message queuing and delivery infrastructure for inbound and outbound HL7 and API traffic.

• Develop interfaces for demand-side EHR integrations, including mapping from internal data models to FHIR-compliant (and other standards) representations.

• Build and maintain REST API integrations with third-party referral sources, attorney platforms, and demand aggregators, including OAuth flows, rate limiting, retry logic, and schema versioning.

• Own the observability layer for the integration infrastructure: structured logging, alerting on message processing latency/failures, and dashboards that surface issues before they reach the operations teams.

• Contribute to the design of integration onboarding tooling that reduces time-to-live for new imaging center and referral source connections

• Provide technical mentorship to mid-level engineers and participate in architecture reviews across the broader Engineering org

THE TOP 5 THINGS WE WANT YOU TO ACHIEVE IN YOUR FIRST YEAR

• Deep domain ownership. Within 90 days, you have a complete mental model of our integration workflows — every active connector, its transport mechanism, its failure modes, and its monitoring coverage.

• Resilience uplift. You have identified and remediated the most critical reliability gaps in our HL7 pipeline. There is a measurable reduction in integration-related operational escalations.

• Scalable transformation architecture. You have designed or materially evolved our data workflows such that onboarding a new demand-side or supply-side vendor is a simple choice from a menu of robust technical options.

• Observability in production. Every integration has structured alerting and a clear SLA. The operations team can self-serve on integration health without engineering involvement for routine issues.

• Shipped meaningful capability. At least two significant integration improvements. This can be new connectors, new vendors, automations that improve quality, or infrastructure improvements. These improvements are live in production and have measurably improved connection optionality, operational efficiency, and/or error rate.

WHAT YOU MIGHT BRING TO THE TABLE

You don't need to tick all the boxes to apply for this role. Whether it's your first role or your fifth, we believe everyone can add value, learn, and grow. However, these might be some of the ways you are currently adding value:

• Proven ability to integrate with legacy systems that were not designed for modern interoperability. For example, aging RIS platforms in radiology, core banking systems in fintech, or equivalent legacy infrastructure in another vertical. The underlying pattern of bridging old and new matters more than the specific domain.

• Strong command of message transformation architecture: you can design pipelines that are observable, replayable, and extensible without requiring a full rewrite every time a new vendor is onboarded

• Experience with integration middleware or engine patterns. This can be a commercial engine (Rhapsody, Mirth Connect, Iguana) or a custom-built equivalent. Strong opinions on when each approach is appropriate are expected.

• Proficiency in at least one backend language used in high-reliability integration contexts (Python, Ruby, Java, C# are all relevant; language is less important than architectural rigor).

• Familiarity with RESTful API integration patterns, including schema versioning, backward compatibility, and API contract management

• Strong operational instincts: you instrument what you build, you think about failure modes before they happen, and you treat on-call escalations as a signal about systemic gaps

• Deep expertise in HL7 v2 message processing is preferred. This means you understand the base standard and have worked through enough vendor non-conformance to know where the dragons are. Experience with MLLP transport, message acknowledgment patterns FHIR R4, and common parsing edge cases is strongly preferred

• Experience in healthcare is a plus, but not required. We care far more about your integration engineering depth and legacy system fluency than your industry background

HOW WE WILL INTERVIEW YOU

We keep our interview process short and sweet, and we're a nimble team that can progress at pace. Here are the stages you can expect, but we might switch up the order depending on team availability:

• Introductory call with our Senior Talent Partner — approximately 30 minutes by phone.

• Video call with the hiring manager — approximately 45 minutes, structured deep-dive into the role and technical domain.

• Assessment stage — may be a take-home exercise, in-person session, or additional video calls. We're mindful of your time.

• Meet the founders and/or other team members.

• Offer!

BENEFITS

We go beyond the basics with our benefits package. Here's what you can expect from us:

• Competitive salary range, plus performance bonus and equity

• 401k

• Healthcare, Vision, and Dental

• All equipment needed to do your role effectively

• Flexible and remote/hybrid working options

• Personal development budgets

• 18 days PTO plus public holidays

• 10 paid sick days

• Inclusive policies designed by our team, for our team

Diversity at SCAN.COM

Scan.com is committed to eliminating discrimination and encouraging diversity within our team.

We strive to provide equality and fairness for all job applicants and employees, and never discriminate on the basis of gender, marital status, age, race, ethnicity, religion, or physical differences.

We are opposed to all forms of unlawful treatment and discrimination.

Our ambition is for our team and its Board to be representative of the diversity in society, and for every employee to feel respected and able to bring their best selves to work.