Commure, Mountain View, CA +1
Our team works directly alongside clinicians, not through layers of process, which means the gap between what you build and its impact on patient care is immediate. We move fast, deploy daily, and take full ownership from early thinking to production. If you're energized by hard problems, high stakes, and a team that holds itself to a high bar, you'll find your people here.
The future of healthcare is being built right now. Come deliver this transformation.
The Revenue Cycle Management team is hiring for a Senior Engineering Manager to join the team. We build software that helps medical practices get paid accurately. This role leads the engineering team that owns the money-in path: everything from when an insurer says how much they'll pay, to when that payment is on the books, verified against the bank, and the patient knows what they still owe.
You will manage a team of ~6 engineers across the full payments surface, reading insurer payment files, matching them to the right claims, recording money on visits, reconciling with bank deposits, calculating patient balances and collections, and partnering with the team that builds the financial reports clinics rely on.
A near-term priority is to hire 2 engineers to strengthen the team. You are the people leader and delivery owner: hiring, coaching, planning, and shipping outcomes, while staying close enough to the systems to set technical direction and unblock hard problems.
Together with teams that submit claims, handle denials, and build financial reporting, this group covers the path from "insurance paid us" to "the books are right, the patient knows what they owe, and leadership can trust the numbers."
Reading insurer payment files Insurers send payment detail files (and paper explanations of benefits) through many networks and formats. The team ingests those files, turns them into structured payment records, and keeps each claim's status up to date as money comes in. This is the start of the pipeline — everything downstream depends on it being correct.
Matching payments to the right claims Each payment line has to be linked back to the claim we originally submitted. Payers often send incomplete or inconsistent identifiers, so we use scoring across many signals (patient info, policy numbers, providers, amounts) and test changes on historical data before they affect real money.
Recording payments on the books Once matched, payments are recorded on the correct visit using per-clinic rules — what to write off, what to shift to the patient, how contractual rates apply. Corrections use safe reverse-and-repost flows so history stays auditable. The books have to balance; "close enough" is not good enough.
Matching payments to the bank For many customers, we verify that insurer checks actually landed in the clinic's bank account — using live bank connections, standard bank files, and scanned deposit slips. Until the deposit is verified, automatic recording of payments can be held. This includes the messy long tail of check numbers and payer names that don't match cleanly.
Patient balances and collections After insurance pays, we calculate what the patient still owes and feed statements, the patient payment experience, credits, refunds, and collections. Balance logic has to keep up whenever posting or clinic rules change.
Financial reports clinics trust The payment and ledger work this team owns feeds the reports and dashboards clinics use to run the business. You will partner closely with our financial reporting team so that billing, recorded payments, patient balances, and reports stay in agreement — catching drift early rather than after a customer notices it.
Scale: Large volumes of visits and payment lines, background jobs and scheduled pipelines, rule engines with hundreds of clinic-specific conditions, and zero tolerance for balances that don't add up.
Backend: Python (FastAPI) Database: PostgreSQL Caching: Redis Async processing: Background jobs, task queues, and schedulers for batch payment processing Cloud: Major public cloud provider Monitoring: Prometheus + Grafana Frontend: React (and some Vue), plus reporting product surfaces Collaboration: Notion, Linear
Please be aware that all official communication from us will come exclusively from email addresses ending in @commure.com http://commure.com. Any emails from other domains are not affiliated with our organization.
Employees will act in accordance with the organization’s information security policies, to include but not limited to protecting assets from unauthorized access, disclosure, modification, destruction or interference nor execute particular security processes or activities. Employees will report to the information security office any confirmed or potential events or other risks to the organization. Employees will be required to attest to these requirements upon hire and on an annual basis.
At Commure, we're building the AI Operating System for healthcare, the foundation that defines how care is delivered, documented, and financed. Our platform spans the full care journey: Ambient AI and Dictation eliminating documentation burden at the point of care, intelligent Agents automating patient and revenue workflows, and autonomous RCM processing billions in claims, all on a single AI-native platform integrated with 60+ EHRs.
Healthcare carries a $1 trillion administrative burden and we're at the center of transforming it. Today, 500,000+ clinicians across 500+ healthcare organizations nationwide trust Commure to handle $25B+ in annual claims and support over 200 million patient interactions. Our latest $70M raise at a $7B valuation reflects the confidence the market has placed in this mission. We've also been named to the Fortune Future 50 list and the 2026 AI Breakthrough Awards for “Overall NLP Company of the Year.”
AthelasSan Francisco, California +3
Pay not posted
Posted Jun 17, 2026
AthelasSan Francisco, California +3
Pay not posted
Posted Jun 17, 2026
AthelasSan Francisco, California +3
Pay not posted
Posted Jun 17, 2026
AthelasSan Francisco, California +2
Pay not posted
Posted Jun 17, 2026
AthelasSan Francisco, California +2
Pay not posted
Posted Jun 17, 2026
AthelasSan Francisco, California +3
Pay not posted
Posted Jun 17, 2026
Source: the Commure Ashby job board. We last checked this job 8 h ago. We first saw it 6 days ago. A job on a job board does not always mean that the team interviews people now. We found this job board in a public list. We did not yet compare it with the careers page of the company.
No one has reported an interview at Commure yet. Did you interview there? Add the questions.
Funding records can have errors and can be missing. The company page has the links.
This base pay is above the median for senior software engineering jobs in the Bay Area.
We compare the middle of each posted range. This is base pay as posted. The group does not include this job.