Integration Engineer, Clinical Data Path

About This Role

Own the complete clinical data path for FDA-cleared diagnostic AI: how studies arrive from hospital systems, how our model processes them, and how results return reliably. You'll solve the structural problems that make clinical AI fail silently in production—incomplete studies, unclosed associations, memory leaks surfacing as 502s, and firewall rules applied to wrong egress IPs.

a2z Radiology AI builds clinical AI that reads alongside radiologists. Our abdomen-pelvis CT triage device is FDA-cleared and the first commercial system to simultaneously triage seven urgent conditions on abdomen-pelvis CT in the U.S. We're backed by Khosla Ventures.

What You'll Own

• On-premise ingest: A pynetdicom C-STORE service that assembles studies, handles senders that never signal completion cleanly, applies backpressure, passes compressed transfer syntaxes through untouched, and spools to disk to prevent data loss on link drops.
• Cloud ingest: A DICOMweb STOW-RS receiver with streaming, bounded-memory multipart parsing, per-part study-UID checks, and exactly one canonicalization and inference firing per request.
• Tenancy and privacy at the boundary: Determine which customer owns a study with no silent defaults, apply DICOM PS3.15 confidentiality rules, run fail-closed checks before egress, and maintain a re-identification store encrypted under customer-held keys we never access.
• Outbound lanes: JSON callbacks, dictation-system autotext, and HL7 v2 ORU^R01 over MLLP shaped to each customer's interface engine.
• Visibility and observability: Per-study tracing, three-component health checks per integration, drift detection between deployed and expected state, and continuous integration for gateway repositories.
• Security documentation: Precise, honest answers on transport, retention, and incident handling for security reviews, with clear accounting of system capabilities and limits.

The Work

Hard problems here are rarely sloppy code—they are structural. You'll chase unbounded reads that balloon memory past request-body size and trigger OOM kills surfacing as bare 502s from load balancers. You'll debug network rules returning mid-stream 403s that look exactly like TLS failures. This role currently has one owner and needs dedicated focus to harden the path and bring gateway repositories under proper continuous integration.