Strategic Overview
Software Engineer Infrastructure at Sodalis, Inc. is defined by the responsibilities and candidate requirements in the employer's listing.
The published role emphasizes work such as Decide how our architecture runs in a pharmacy's environment, starting with the AI pharmacy tech product: full stack on-site, a hybrid split with our cloud, or something in between.
The role is listed for Palo Alto with a remote working arrangement, giving candidates the practical context needed to assess fit before applying.
Key information at a glance
About This Role
Specialty pharmacy is where the most complex and expensive drugs reach the most in-need patients, and it still runs on faxes, phone tag, and manual data entry.
Patients wait weeks for therapies that can't wait.
Sodalis is building AI agents that run those operations end to end: reading and validating prescriptions, handling phone calls, and moving prescriptions through eligibility and fulfillment.
Key Responsibilities & Objectives
- Decide how our architecture runs in a pharmacy's environment, starting with the AI pharmacy tech product: full stack on-site, a hybrid split with our cloud, or something in between.
- Adapt our current infrastructure and build the packaging and deployment path that installs and updates Sodalis at each pharmacy.
- Own those deployments over time: upgrades, rollbacks, and observability into health and failures without being on site.
- Go in with our customer and pharmacy IT teams to learn what their environments actually allow, and design for the range.
- Partner with the founders and early engineering team on architecture.
Required Qualifications & Candidate Blueprint
- 5+ years in infrastructure or platform engineering.
- You've taken an AWS-native stack and made it run on Kubernetes or similar in environments you don't operate, including stateful services.
- You've shipped and maintained software running in environments you don't control: on-prem, customer-hosted, edge, or embedded.
- You've kept a fleet of remote installs updated, observable, and recoverable without being able to log into them.
- You've set the first pattern for something in a startup and are comfortable with ambiguity.
- You'll spend time with pharmacy IT teams and need to understand their constraints firsthand. No healthcare background required.
Salary & Benefits
Published compensation: $185,000 – $215,000
Salary Benchmark
This role’s published compensation is compared with active employer-disclosed ranges for the same role, in the same currency and pay period.
Benchmark uses active employer job postings in our database, excludes this listing, and matches the currency and pay period. It is not a third-party salary estimate; currencies are not converted.
Full Job Description
The following is the complete job description supplied by the source. We sanitize unsafe markup and remove external links, but do not shorten or rewrite the employer's source content.
Software Engineer, Infrastructure
Hybrid in Palo Alto (Mon / Wed / Thurs) · $185Kâ$215K base + meaningful early-stage equity + full benefits
About Sodalis
Specialty pharmacy is where the most complex and expensive drugs reach the most in-need patients, and it still runs on faxes, phone tag, and manual data entry. Patients wait weeks for therapies that can't wait.
Sodalis is building AI agents that run those operations end to end: reading and validating prescriptions, handling phone calls, and moving prescriptions through eligibility and fulfillment. The ambition goes beyond that. We want to be the rails every specialty prescription runs on, and the first system to perform clinical review at the standard of a pharmacist.
We're already in production, processing tens of thousands of prescriptions a week. Backed by Gradient Ventures (Google's AI fund), and founded by veterans of Apple's Applied ML, Included Health, and Avella Specialty Pharmacy (scaled to $1.5B+ before its acquisition by OptumRx).
The Opportunity
Everything we run today is cloud-based, and so are the pharmacy management systems we integrate with. But most of the specialty pharmacy market runs on-prem. To reach it, our system has to run on the pharmacy's systems instead of ours. Whether that's the full stack on-site or a hybrid split with our cloud is one of the first decisions you'd make. That's the problem you'd own.
We've never shipped an on-prem deployment, so there's no pattern to follow. You'll decide how our architecture gets packaged and deployed into environments we don't control, what has to change in our current infrastructure to make that possible, and how we maintain and see into those deployments once they're live.
We don't yet know what these environments look like in detail. Some pharmacies may have restricted outbound access, legacy hardware, or IT teams that can't give us a login; others may be more open. Part of the job is going in with our customer, finding out what's actually there, and designing something that works across the range.
You'll start with our AI pharmacy tech product, rolling out with a committed customer, so you build against a real deployment instead of a hypothetical one. You'd work directly with the founders and the early engineering team on the architecture.
What you'll do
Decide how our architecture runs in a pharmacy's environment, starting with the AI pharmacy tech product: full stack on-site, a hybrid split with our cloud, or something in between.
Adapt our current infrastructure and build the packaging and deployment path that installs and updates Sodalis at each pharmacy.
Own those deployments over time: upgrades, rollbacks, and observability into health and failures without being on site.
Go in with our customer and pharmacy IT teams to learn what their environments actually allow, and design for the range.
Partner with the founders and early engineering team on architecture.
What we're looking for
5+ years in infrastructure or platform engineering.
You've taken an AWS-native stack and made it run on Kubernetes or similar in environments you don't operate, including stateful services.
You've shipped and maintained software running in environments you don't control: on-prem, customer-hosted, edge, or embedded.
You've kept a fleet of remote installs updated, observable, and recoverable without being able to log into them.
You've set the first pattern for something in a startup and are comfortable with ambiguity.
You'll spend time with pharmacy IT teams and need to understand their constraints firsthand. No healthcare background required.
How we work
We're a handful of people going all in on a problem we think is worth it, holding a high bar and shipping work that reaches real patients. It's intense, and it isn't for everyone. We want people who want to build something that matters, alongside others who care as much as they do. If that's you, we should talk.
Please mention the word **COMMITMENT** and tag RMmEwNjo5OGMwOjM2MDA6OjEwMw== when applying to show you read the job post completely (#RMmEwNjo5OGMwOjM2MDA6OjEwMw==). This is a beta feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.
Editor’s Market Perspective (Our Custom Analysis)
Why This Position Matters
This opening may suit candidates who can demonstrate experience relevant to the employer's published requirements. Its strongest career signal is the scope of the work itself — particularly Decide how our architecture runs in a pharmacy's environment, starting with the AI pharmacy tech product: full stack on-site, a hybrid split with our cloud, or something in between. — rather than a generic title alone.
Resume & Application Strategy
For the application, connect specific examples from your experience to the responsibilities and qualifications in the employer's description. Quantify outcomes from comparable work, and place the most relevant evidence near the top of the resume. When the employer explicitly names tools, platforms, leadership scope, or domain experience, use those source terms accurately and in context.
We organize source-provided information into this independent job-seeker overview. Compensation is shown only when the source provides it; the official listing remains the authority for current requirements and application instructions.