Staff Software Engineer, Data Integrations
Los Angeles, California, United StatesAll locationsLos Angeles, California, United StatesMountain View, CA, USANew York City, New York, United StatesSan Francisco, California, United States Hybrid
$210,000–$275,000 a yearJobFig found this opening at its original source and checks that it remains available.
About the role
The Data Integrations team owns the systems that move clinical and financial data between Commure and hundreds of external healthcare endpoints. The domain is EMRs, but the engineering problem is distributed systems at scale: durable orchestration on Temporal, strong delivery semantics against unreliable third parties, and a data and networking substrate that has to keep up as the business grows. We're looking for a Staff Software Engineer to set technical direction for this platform and help us scale as we more towards Enterprise Customers.
What you'll bring
- Bachelor’s or Master’s degree in Computer Science, Engineering, or a related field, or equivalent extensive experience
- 10+ years of professional software engineering experience, with a substantial chunk at Staff-equivalent scope: architectural decisions on multi-quarter projects, made under real constraints, that you'd still defend today.
- Deep experience building and operating distributed systems at scale, high-throughput pipelines, data-intensive services.
- You can talk about the non-obvious failure modes, not just the happy path.
- Strong data-layer and concurrency judgment.
- You've made a relational database (Postgres or similar) do more than it wanted to, and you know when to reach for a DB lock, when Redis is the right tool, and when the right move is a design that doesn't need either.
- Real depth in the boring-but-critical layers.
- Networking and egress (NAT, static IPs, connection lifecycle, DNS, TLS), the database, the container runtime.
- You've been the person the org turns to when something below the application layer is misbehaving.
- The ability to translate business goals into technical direction, and technical tradeoffs into language non-engineers can act on.
- A history of leveling up the engineers around you.
- Healthcare integrations experience — HL7 v2, FHIR, and EHRs like Epic, Cerner, or Athenahealth.