Omada is a virtual care solution with personalized chronic disease management programs designed to adapt to every member. Check your eligibility today! Backed by NEA, Norwest and a16z.
About the role
Omada Health is a digital care provider that empowers people to achieve their health goals through sustainable behavioral change. We’re looking for a senior software engineer to join our Solutions Engineering Team. Our primary function is to understand customer challenges, design tailored technical solutions using Omada's products and systems, and demonstrate the value and feasibility of those solutions.
What they're looking for
- 5–8 years writing readable, tested, and efficient production code
- We primarily use Ruby on Rails and are especially interested in candidates with strong Rails experience, but we're also open to exceptional backend engineers in other languages who are excited to ramp quickly on Rails
- Experience with a relational database (PostgreSQL)
- Experience building and consuming APIs and integrations across service boundaries
- Fluency with AI-assisted development — you use AI coding assistants in your day-to-day work and have a thoughtful, quality-conscious point of view on where they help and where they don't
- Experience building API-driven automation workflows (e.g., with Tines, n8n, or similar)
More about this role
Omada Health is on a mission to bend the curve of chronic disease.
Omada Health is a digital care provider that empowers people to achieve their health goals through sustainable behavioral change.
We’re looking for a senior software engineer to join our Solutions Engineering Team. Our primary function is to understand customer challenges, design tailored technical solutions using Omada's products and systems, and demonstrate the value and feasibility of those solutions.
- Shape complex, cross-system integrations. Be involved early on high-complexity, cross-system work (e.g., partner/alliance integration APIs) that requires understanding how systems should fit together and the operational implications of the design.
- Spot the pattern behind recurring toil and define the reusable templates, standards, and automation the rest of the team builds on. Know when to loop in the engineers who own a given system, and reconcile competing constraints.
- Get to the real root cause. Go beyond the immediate fix to determine whether the true cause is architectural, a monitoring gap, or a process failure and drive the fix (and the follow-up action items) so it doesn’t recur.
- Mentor the team —...
Browse similar: Startup jobs · Remote jobs