Senior Backend Engineer, Application Platform

Sodalis, Inc.•Palo Alto, CA

2d•$185,000 - $215,000•Hybrid

About The Position

Sodalis is building AI agents to automate specialty pharmacy operations, including prescription review and validation, phone calls, eligibility, and fulfillment. The company aims to create a platform that can support specialty prescriptions across pharmacies and perform clinical review to pharmacist standards. Its product is already in production, processing tens of thousands of prescriptions weekly. The Senior Backend Engineer will own the application platform, including its domain model, configuration layer, and internal tooling. The role focuses on building shared backend primitives and a configuration-driven system that supports the differing workflows of multiple pharmacies without requiring custom engineering for each implementation. The engineer will define the boundary between configurable behavior and core code, build services and APIs for internal implementation tools, and establish versioned contracts that allow safe, selective upgrades to a live system. The role works directly with the founders and early engineering team on architecture and platform direction. It also involves working with the solutions team and pharmacies to understand their workflows. Healthcare experience is not required.

Requirements

At least 5 years of experience building backend systems in production.
Strong system design skills, including the ability to design a coherent system from an open-ended prompt and explain trade-offs clearly.
Solid data modeling and API design skills, with an ability to build generalizable systems rather than one-off solutions.
Experience building a configuration-driven system operated by others, such as a rules engine, multi-tenant platform, feature-flag or rollout system, or workflow DSL.
Experience shipping 0-to-1 products in startups and comfort working with ambiguity.

Responsibilities

Model shared pharmacy primitives, including prescriptions, directions, and insurance outcomes, and build backend systems that express pharmacy-specific differences through configuration.
Determine which behaviors can safely be configured by the solutions team and which must remain in the core engine.
Build backend services and APIs for internal tools that enable the solutions team to implement new customers without engineering support.
Define and version the contract between the engines and the people configuring them so upgrades can be released safely and selectively.
Ship changes to the live system using zero-downtime rollouts and safe versioning practices.
Partner with the founders and early engineering team on architecture and roadmap.
Work with the solutions team and pharmacies to understand how their workflows differ.