Mountain View, CAremote

Salary
$210,000–$275,000
Posted
Jul 19, 2026
Location
Mountain View, CA
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A Staff Software Engineer role focused on designing and operating the core financial ledger infrastructure within a healthcare revenue cycle management platform. The work centers on building an immutable, event-driven accounting system that tracks insurance payments, patient balances, adjustments, and refunds — keeping posting engines, bank reconciliation, and financial reports in consistent agreement at scale. Best suited to senior backend engineers with hands-on experience in financial systems such as billing, payments, or ledger design, and deep comfort with large relational databases.

Staff level · 8+ years · Remote · Full-time

Must have (5)
PythonPostgreSQLfinancial systemsdistributed tracingobservability
Nice to have (6)
healthcare RCM835/ERA remittancebank reconciliationevent sourcing or Cdc ArchitecturesBAI2Kafka

“or” means any one of them counts — you don't need all of them.

Posted 2 times — it's one opening, so apply once.

We read this from the posting text with AI. Skim the description below before ruling yourself out.

How this req sits in the market our data

Roughly 10,700 people nationally plausibly meet what this posting asks for (software developers). range 3,150–16,000

Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.

What won't set you apart
Python51%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $138,970 (middle half $107,524–$175,762).

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.

Why we read it this way (8)

No compensation range is stated in the posting.

Python is listed as 'preferred' within the required qualifications block ('Strong backend engineering (Python preferred)') — it is the named language in a hard-requirements section, so it is treated as a required skill, but the parenthetical qualifier is noted here for transparency.

Financial systems experience (payments, billing, reconciliation, ledgers, double-entry accounting, idempotency) is a hard gate stated in the required qualifications section; no single named tool is called out, so it is captured as a domain requirement.

Distributed tracing, monitoring, alerting, SLOs, dashboards, and logging are all called out as hard requirements under 'What You Have'; these are grouped under 'observability' and 'distributed tracing' as the most concrete named practices.

Healthcare RCM, 835/ERA, bank reconciliation, event sourcing/CDC, BAI2, and high-throughput batch pipelines all appear under the 'Bonus points' section and are marked preferred accordingly.

Kafka is not explicitly named; it is inferred as a representative tool for the 'unified event stream' and 'event-sourced/CDC architectures' mentioned in the bonus section — listed as preferred.

The role explicitly titles itself 'Staff Software Engineer' and the requirements (8+ years, architecture ownership, cross-team influence, mentoring Staff engineers) are consistent with Staff-level scope.

Caller marked this a fully-remote role — scored against the national candidate pool.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗