> Markdown version of [/jobs/ext/4014612-staff-software-engineer-platform-architecture](https://www.wearedevelopers.com/jobs/ext/4014612-staff-software-engineer-platform-architecture). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Software Engineer - Platform Architecture - **Company:** b.well Connected Health - **Location:** United States - **Salary:** $175,000.0 - $220,000.0 - **Contract:** Permanent contract - **Skills:** Query Performance, Java (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Application Integration Architecture, Computing Platforms, Cloud Engineering, Data Architecture, Data Integration, Software Debugging, Document Management Systems, Distributed Systems, Python (Programming Language), Modular Design, MongoDB, Node.Js, Operational Data Store, OpenID, Query Optimization, Software Engineering, Software Technical Review, TypeScript, Management of Software Versions, Fast Healthcare Interoperability Resources, Large Language Models, Apache Spark, Spring-boot, IT Architecture, Caching, Electronic Medical Records, Backend, Event Driven Architecture, Build Management, Kubernetes, Apache Kafka, Graphql, Operational Systems, Data Management, Vertica, Claude, Api Design, Wearables, Databricks - **Published:** October 29, 2026 - **Apply:** https://www.careerbuilder.com/job-details/staff-software-engineer-platform-architecture--c586e36b-860b-4495-8d26-2c126ad7d07f ## About the Role Software Engineering, Customer Experience, Ecosystems, Medical Record System, Data Management, Healthcare, Wearables, Software Engineering, Technical/Engineering Design, Application Programming Interface (API), * Deep expertise in large-scale distributed systems and scalable design. You''ve built and operated systems that handle high volume and real failure modes, and you''re fluent in partitioning, back-pressure, idempotency, eventual consistency, and the trade-offs between consistency and availability. * Strong event-driven architecture experience, hands-on with Kafka: topic and partition design, schema evolution and governance, consumer groups, idempotency, and the operational side of running it in production. * Strong API design across REST and GraphQL. We run a federated GraphQL gateway, so schema composition, versioning, and contract evolution matter here as much as clean endpoint design. * Exposure to AI as a component of a system is a plus - LLMs or agents and the practical concerns around them (retrieval, evaluation, guardrails, cost and latency). Deep AI architecture ownership sits with a dedicated Applied AI Engineering hire, so it isn''t a primary requirement here. We do expect you to use AI tools like Claude fluently in your own work. * A well-rounded, hands-on engineer who goes deep in at least one strongly-typed language and moves comfortably across a polyglot stack. You have strong software-design instincts and care about clean interfaces, sensible abstractions, and keeping services loosely coupled. Our backend spans Python (data and AI), TypeScript/Node.js (which runs our FHIR server), and Java/Spring Boot (FHIR processing and backend services), with Kafka, our federated GraphQL gateway, Databricks, ClickHouse, MongoDB, and AWS around it. * Sound data and storage instincts: data modeling, caching, query optimization, and how batch and streaming workloads (for example on Spark or Databricks) fit together with operational systems. * Cloud-native and security fundamentals: Kubernetes and AWS, identity and auth (OIDC, token exchange), and multi-tenant isolation in a regulated environment that handles protected health data. * You can walk someone through a system you''ve designed and operated end to end: how it works, where it breaks, and the trade-offs you made. * Healthcare or FHIR experience is a strong plus and something you''ll go deep in here. If you haven''t worked in the domain yet, that''s fine; it''s learnable, and we''ll help you get there. ## Description The Architecture team defines how that platform is designed and built. We set the patterns, contracts, and standards the rest of engineering builds on, run technical design reviews, and take on the hardest, most cross-cutting systems ourselves. We''re hiring a Staff Software Engineer to own work like event-driven data integration on Kafka, large-scale distributed processing, and the API and federated GraphQL layer behind our SDKs - and to partner on making AI a dependable part of the platform. This is a hands-on role. You design these systems, you build them, and you help operate them in production. You work horizontally across teams rather than inside a single product squad, so the patterns and services you create show up everywhere. The hard problems here are about scale, correctness, distributed-systems behavior, and the real-world messiness of healthcare data. What you''ll do: * Design and build event-driven distributed systems on Kafka: orchestrator and worker services, schema and contract governance (AsyncAPI, CloudEvents), idempotent consumers, sagas and event choreography, and config-driven pipelines that onboard new data sources without code changes. * Own API architecture at scale across REST and a federated GraphQL gateway (WunderGraph Cosmo) that powers our SDKs, including schema composition, versioning, contract evolution, and FHIR conformance. * Partner on AI architecture and enablement: help make LLMs and agents dependable parts of the system (retrieval, evaluation, guardrails, and clear boundaries around protected health data), working alongside the dedicated Applied AI Engineering lead who owns that area. * Shape FHIR and health-data architecture: terminology services, resource modeling, clinical quality measurement (DQM and CQL), high-volume document storage, and query performance across MongoDB and ClickHouse. * Help run the technical design review process and document the decisions and standards, so significant designs are reviewed against consistent criteria and the platform stays coherent as it grows. * Stay close to the code and to production: write real software, build proofs of concept that prove out a pattern before teams adopt it, and use observability and operational data to confirm decisions hold up and to debug incidents when they don''t. * Mentor senior engineers and tech leads on distributed-systems thinking, system design, and the trade-offs behind good architecture., * The platform''s event-driven and API/GraphQL foundations are solid, well-governed, and adopted across teams. * The platform''s AI integration points are dependable and safe to build on, in partnership with the Applied AI Engineering lead. * FHIR and health-data architecture (terminology, quality measurement, storage) performs well and scales to millions of patients. * Technical design reviews run efficiently, with clear decisions and standards that teams rely on. * Engineering moves faster because teams build on proven, reusable platform patterns instead of reinventing them.