Platform Engineer

• Build the tool surface an agent acts through, the retrieval and context layer that grounds it in the right clinical and operational data, the serving path product teams call to reach a model, and the evaluation that catches a regression before a customer does.
• Take over shared components that every team depends on, providing interfaces worth depending on, and clarify the seams between the legacy platform and the newer services.
• Enhance the messaging backbone; take the event bus the rest of the way, adding contract testing for service verification.

Senior Software Engineer, Platform

Developer Relations

• The delivery pipeline. Consolidate CI/CD onto a single system every delivery team builds and deploys through. Cut build and deploy times. Own the AWS and CloudFormation infrastructure underneath it. Make dependency scanning, secrets detection, and static analysis default steps on every build. Give teams feature flags so deploy and release come apart.
• The developer platform. This starts on the engineer's machine: environment setup, build speed, the tools they use before code ever reaches the pipeline. Replace shared environments with ephemeral ones, and solve multi-tenant test data seeding so they're usable. Our event bus is partially adopted, which makes contract testing part of this: services have to be testable in isolation without standing up the whole topology. Establish golden paths: opinionated, documented ways to build, test, and deploy a service. Drive toward self-service, and over time an internal developer portal. Run the platform as a product, with a visible roadmap, a feedback channel teams actually use, and reliability standards for the platform itself.
• The test automation framework. Turn a framework QA builds on delivery teams' behalf into one delivery engineers use directly. Two SDETs work with you on it. Building it is the straightforward part. Landing it with delivery leads whose teams are measured on shipping is the job.
• Production ownership. Delivery engineers carry the pager for their own code today, but most incident response still lands on the infrastructure team, because engineers can't see or reach what they shipped. This is a HIPAA environment, so broad production access isn't on the table. Engineers need full visibility into how their systems behave without access to the data inside them. Build the logging, tracing, metrics, and alerting stack that delivers that, and give teams audited break-glass paths for the cases that need more.
• The agentic development loop. Our engineers already use AI-assisted development, and it's made everything downstream of them slower. Code generation is cheap. Verification is not. That gap is what we're hiring you to close. You'll own what makes coding agents effective in our codebase: deterministic local builds, fast test feedback, repo context, sandboxed execution, review gates for agent-authored code, and internal platform capabilities exposed to agents through MCP.

ECP

Senior Software Engineer, Platform

Engineering Manager, Developer Experience