Senior Software Engineer, Solutions Engineering

Omada Health

2d•$156,000 - $224,250•Remote

About The Position

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.

Requirements

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)
A track record of identifying inefficiencies and shipping solutions that deliver measurable value. Comfort connecting the dots between a business/operational problem and the code that solves it
Solid debugging and optimization skills
Strong grasp of SDLC processes and frameworks
Excellent communication and collaboration skills (verbal and written) — you can work directly with non-engineering stakeholders and translate between business needs and technical reality
Experience in a solutions engineering, implementation, or customer-facing technical capacity
Experience mentoring engineers or leading projects

Nice To Haves

Experience with a modern front-end framework (React, Vue)
Healthcare or other regulated / data-sensitive domain experience

Responsibilities

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 — including non-engineers. Be the go-to person for coding guidance and growth for the team’s members who don’t have a formal software engineering background but write code and build automations as part of their role.
Drive delivery decisions with stakeholders. Partner directly with commercial, product, and engineering stakeholders to scope solutions that fit real timeframes and constraints, and make the call on technical trade-offs for delivery.
Navigate ambiguity. Take on problems that show up without a clear spec — ask the right clarifying questions, scope the actual work, and create a technical plan the team can execute against.
Surface risk early and document deeply. Identify risks, edge cases, security concerns, and downstream impacts as part of discovery, and make sure deep-dive knowledge lives in runbooks.
Participate in our on-call rotation; triage and address issues that come up supporting members, ensuring timely resolutions and assisting internal teams in their investigations.