> Markdown version of [/jobs/ext/4647604-senior-backend-engineer](https://www.wearedevelopers.com/jobs/ext/4647604-senior-backend-engineer). 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). --- # Senior Backend Engineer - **Company:** Sodalis AI - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Management of Software Versions, Backend, Build Tools, Api Design - **Published:** November 9, 2026 - **Apply:** https://www.juju.com/job/28_25303_55bcf00b68cf69edb9f43ac1cad36270 ## About the Role * 5+ years building backend systems in production. * Strong system design: you can take an open prompt, design a coherent system, and explain the trade-offs clearly. * Solid data modeling and API design: you build systems that generalize, not one-offs. * You've built something config-driven that other people operated: a rules engine, a multi-tenant platform, a feature-flag or rollout system, a workflow DSL. You know where those designs go wrong. * You've shipped 0*1 in startups and are comfortable with ambiguity. * You'll spend time with the solutions team and with pharmacies to understand how their workflows actually differ. No healthcare background required. ## Description * Model the shared primitives (prescriptions, directions, insurance outcomes) and build the backend that turns each pharmacy's differences into configuration, so one system serves many pharmacies. * Decide where the line between configuration and code sits: what a solutions team can safely configure, and what stays in the engine. * Build the backend services and APIs behind the internal tools a solutions team uses to implement a new customer without an engineer. * Define and version the contract between our engines and whoever configures them, so upgrades ship safely and selectively. * Ship changes to a system that's live, where every prescription is a patient and a bad migration isn't an outage, it's a delayed therapy. Zero-downtime rollouts and safe versioning are table stakes here. * Partner with the founders and early engineering team on architecture and roadmap.