Omada Health Senior Engineering Manager at Omada Health owning delivery and growth of multiple squads focused on member-facing products. Stay technical by shipping production work and reviewing architecture.
Responsibilities
Own delivery across your squads. Sprint shaping, prioritization, backlog grooming, and estimation. Make the calls, write them down, and be accountable for them. When two squads want the same thing at the same time, you are the one who decides.
Own cycle time. Yours to improve, not at the expense of quality, and yours to explain when it changes, including why one of your squads is slower than the other.
Stay technical. On squads you manage directly, you ship production work every sprint, off the critical path, in the same agent workflows your builders use. On squads that run through a manager, you stay close enough to review architecture, catch a weak design, and be useful in an incident. Either way, you can teach someone to navigate the system, not just navigate it yourself.
Partner with your Product Strategist. They own what the squad builds; you hold the line between their scope and yours so the squad never has two people answering the same question differently.
Grow a manager. If an EM reports to you, their growth is your work product. Their squad's health is the evidence.
Plan the team you need next year, not just this quarter. Headcount, skill mix, and the onboarding path that gets a new builder productive in an agent-heavy codebase in weeks rather than months.
Set the AI standard past your own boundary. Write down what good looks like, teach it, and measure whether it stuck. Other squads should be able to use what you built without you in the room.
Take on the problem that is nobody's. You will find things that slow down engineering broadly. Some of them you should pick up, organize, and close out with your peers.
Qualification
Your first team is your peer group8+ years in software engineeringExperience developing another leaderCurrently shippingUnderstanding of CI/CDExcellent written communication
Required
You are comfortable being accountable for what your squads ship. You still write code, and you want to. This role ships production work off the critical path, in the same codebase and the same agent workflows as your squads, so you feel the friction your people feel first-hand.
Your first team is your peer group, not your reports. When something is slowing down the engineering org and it is nobody's job, you have a track record of picking it up, getting the right people in the room, and finishing it.
8+ years in software engineering, including 4+ years managing engineers directly.
Experience developing another leader: a manager who reported to you, or an engineer you grew into a tech lead or EM role with real accountability attached. Tell us where they are now.
A track record shipping mission-critical software to production, and living with it afterwards. We all make mistakes; what sets you apart is that you own yours and turn them into something better.
Experience owning prioritization and estimation for a team, including saying no, not now, and explaining why.
Experience giving direct developmental feedback, and at least one case where you managed someone through underperformance with real support attached.
Currently shipping, or recently shipping, production code in at least one layer of our stack (backend (Ruby, Python, ...), web frontends (React), iOS, or Android,) with enough range to follow the conversation in the others and review architecture decisions critically.
Comfort with an expert-generalist team model, where a backend-heavy builder ships in the mobile app and a mobile-heavy one ships in the backend. You understand how transformative this model is, and you should be able to name the risks and opportunities it brings.
Hands-on experience directing AI agents through real world production changes, and a considered view on where they help and where they produce work someone else has to redo.
Understanding of CI/CD, logging, monitoring, and telemetry, at the level where you can tell whether your squad's operational story checks out or falls short.
Excellent written communication. Much of this job is writing things down clearly once so they do not have to be argued four times.