Staff Engineer - Insights

Staff Engineer - Insights Full time position open to fully remote work About b.well Connected Health Healthcare is broken by fragmentation. Patients juggle dozens of disconnected portals, carry clipboards full of forms, and struggle to make sense of their own health data. b.well Connected Health exists to fix that. We are a healthcare technology company on a mission to transform healthcare into a simple, on-demand experience, one where consumers are truly at the center. Our platform unifies fragmented health data from hundreds of sources (clinical, claims, device, wearables, etc.) into a single AI-ready longitudinal health record, powering connected digital health experiences for health plans, providers, employers, and the world's leading technology companies. Our partnerships with OpenAI, Samsung, Google, and Perplexity, and our commitment to the CMS-Aligned Network, reflect our position at the forefront of healthcare interoperability. Products like bailey™, our white-label AI health assistant, and the b.well Health AI SDK are redefining what's possible when great data meets great design. If you believe that patients should access their health records as easily as they board a plane, and that design can genuinely change healthcare, this is your role. About the Role b.well's Clinical Data Platform ingests, evaluates, and acts on clinical data at scale — pulling FHIR resources from national and regional data sources, evaluating them against quality measures (HEDIS/NCQA) using a CQL execution engine, and turning the results into tasks, notifications, and care recommendations that reach real patients through our Health Programs applications. We're looking for a Staff Software Engineer to operate at the seams of this system: the shared libraries a dozen-plus services depend on, the production incidents that cross service boundaries, and the architectural calls that determine whether the next six months of feature work is easy or painful. This is a senior individual-contributor role — deeper and broader in scope than a Senior Engineer, focused on multiplying the effectiveness of the teams around you rather than accumulating direct reports. What You'll Work On A distributed system of 15+ Java microservices (Spring Boot 3.5, Java 21, Gradle with dependency locking) spanning FHIR resource management, CQL-based quality measure evaluation, task orchestration, and patient notifications — communicating primarily via Kafka with CloudEvents envelopes. A shared internal FHIR client library, built on HAPI FHIR R4, consumed by nearly every Java service in the org. Changes here ship carefully — versioned releases, staged consumer rollout, and verification — because a mistake doesn't stay contained to one team. A multi-stage clinical data quality pipeline that assembles a member's clinical history and evaluates it against CQL-based quality measures (e.g., breast cancer screening, colorectal screening) on a rolling 12-month window, at population scale. Mixed persistence and messaging: MongoDB (CQL result caching, notification preferences), PostgreSQL with Flyway (measure orchestration state), Kafka (including MSK IAM-authenticated CDC streams), Redis/Caffeine caching, and S3-backed bundling. Production-grade distributed systems problems: consumer group rebalance storms, cursor pagination bugs that silently drop records at scale, ID-form mismatches between systems that only surface for a subset of members, OOM loops under specific data shapes. You'll be the person other engineers loop in when a bug doesn't have an obvious owner. Federated GraphQL and REST APIs (Netflix DGS) fronting the FHIR-based data model, plus event-driven integrations with Iterable for patient messaging. Deployment and observability on AWS/EKS — Helm-based Kubernetes deployments, OpenTelemetry export to Groundcover, and CI/CD via shared GitHub Actions workflows with automated security patching (root.io/Aikido) and Karate-based end-to-end test gates. What You'll Do Root-cause the incidents nobody else can close. Trace symptoms across Kafka consumers, FHIR persistence, and downstream services to the actual root cause — not the nearest workaround — using hypothesis-driven investigation, then land the fix with tests that prove it. Own cross-cutting technical initiatives end-to-end. Things like a persistence migration for a core platform service, a CVE remediation sweep across a dozen+ repositories, or a schema alignment that requires coordinated, ordered PRs across multiple services — you scope it, sequence it, and see it through. Set technical direction for a slice of the platform, in collaboration with — not isolation from — the engineers building on top of it. Write the design docs and ADRs; get them reviewed; make the call when reasonable people disagree. Raise the bar on code review and engineering standards across multiple repositories, not just your own team's. Contribute to shared conventions (hexagonal architecture guidelines, coding standards) that other services adopt. Be a force multiplier for other engineers. Unblock people stuck on distributed systems problems, review architecture before it's implemented rather than after, and turn one-off investigations into reusable tooling or documentation so the next engineer doesn't start from zero. Balance urgency against correctness under production pressure. Distinguish a symptom fix that needs to ship now from the root cause that needs to ship next, and be honest about which one you're doing. What We're Looking For 8+ years of professional software engineering experience, with deep expertise in Java and the Spring ecosystem (Spring Boot, Spring Kafka, Spring Data). Proven experience owning distributed systems in production — Kafka or an equivalent event streaming platform, and the operational maturity that comes with having debugged consumer lag, rebalancing, and message-ordering issues firsthand. Experience maintaining a library or service with many internal consumers, and the discipline that requires around versioning, backward compatibility, and staged rollout. Comfort reading and reasoning about healthcare data standards — FHIR (HL7 R4) or similar structured interoperability standards. CQL, HEDIS/NCQA quality measures, or clinical data experience is a strong plus, not a requirement. A track record of driving technical initiatives that span multiple services or teams, from design through delivery, without needing a program manager to hold the plan together. Experience with at least one of PostgreSQL or MongoDB in production, plus AWS (EKS/Kubernetes, S3, IAM) or equivalent cloud infrastructure. Strong written communication — you'll be writing design docs and ADRs that other engineers implement against, and PR reviews that teach as much as they gatekeep. A bias toward finding root causes over shipping the fastest patch, tempered by good judgment about when "fastest patch now, root cause next" is the right call. Compensation The target salary range for this position is $185,000 – $250,000, and is part of a competitive total rewards package including stock options, benefits, and incentive pay for eligible roles. Individual pay is determined by experience, location, internal pay equity, and other relevant business considerations. We review all compensation programs annually to ensure they remain competitive and fair. Data shows that women, people of color, and other underrepresented groups may be less likely to apply for jobs unless they believe they are a perfect match. But b.well holds diversity amongst its key values, and we have a strong commitment to building our workforce and products through that lens. You don't have to check every box in this job description to be a great fit for the role! If you're excited about this position and the prospect of working for b.well, please apply. If it turns out this role isn't for you, there may be other openings that could align with your experience and expertise! We are committed to an inclusive and diverse b.well. We are an equal opportunity employer. We do not discriminate based on race, ethnicity, color, ancestry, national origin, religion, sex, sexual orientation, gender identity, age, disability, veteran, genetic information, marital status or any other legally protected status.