# Staff Software Engineer, Data Integrations at Commure

- Company: Commure
- What the company does: Commure builds the financial infrastructure for modern health systems, with an AI-native revenue cycle platform that automates end-to-end RCM and turns manual administrative work into scalable software—enabling durable growth and better care outcomes. Backed by General Catalyst, Sequoia and Lux.
- Company website: https://www.commure.com/
- Type: Startups
- Level: Senior
- Location: Mountain View, CA
- Work setup: Remote
- Pay: $210K to $275K base salary per year (USD)
- Posted: 2026-07-20
- Apply by: 2026-10-08
- Apply: https://jobs.ashbyhq.com/commure/62be068a-2618-4e87-b279-93703f62dc7d
- Page: https://www.1752.vc/careers/jobs/commure-staff-software-engineer-data-integrations/

## 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.

## What they're looking for

- 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
- Production experience with GCP and container orchestration (Kubernetes, Knative, or similar serverless-on-k8s), and fluency in a modern backend language (Python strongly preferred, Go or similar is a plus)

Tags: Engineering