Engineering Manager, Infrastructure

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: Job overview (maybe About the role), About you (maybe Qualifications/Requirements), What you'll be doing (Responsibilities), What you need for this role (Requirements/Qualifications), Technologies we use (maybe Skills), Benefits (Benefits), Pay (salary ranges), Schedule? Not mentioned. So we should include sections: About the role (maybe from Job overview), Responsibilities (What you'll be doing), Requirements (What you need for this role), Skills (Technologies we use), Benefits, Pay. Possibly also Qualifications but we can combine Requirements and Qualifications. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. So we need to strip out the values statements, equal opportunity, etc. Also remove "About Omada Health" etc? That's maybe not needed but could be considered boilerplate? It's substantive about company but maybe not needed? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Omada Health" is not exactly those but could be considered company description; not explicitly prohibited. However they said preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive. Should we keep? It might be considered part of job posting but not required sections. Could be placed in a

before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we must wrap everything in sections; we can have paragraphs before sections. Probably better to include a brief intro paragraph about mission etc. But we must not repeat job title. The job overview starts with "Omada Health is on a mission to bend the curve of chronic disease." That's mission statement. Could be a

. Then sections. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, requirements list, benefits list, skills list maybe. We must not create sections with filler like "commensurate with experience". Pay section: we have salary ranges, so we can include Pay section with those ranges. Must not include placeholder. Schedule: not mentioned, so omit. We need to preserve all substantive information: include details like managing 5 people, hiring, mentoring, owning squad delivery, cycle time, ship code, grow engineers, operational health, escalate, hire AI-augmented, etc. Also details about managing vendor budget, audit controls, etc. Also details about "You will manage millions of dollars in annual vendor budget and spending, through key contracts including Amazon Web Services, Datadog, Gitlab, and Anthropic." Also "You will be responsible for annual internal and external audit controls, and must help your teams develop automation and evidence management processes to streamline audit responses." Also "You partner closely with stakeholders across Engineering, Product, Design, IT, InfoSec, Legal, Compliance, Procurement, and beyond." Also "As a Engineering Manager, you ship code alongside your AI-powered engineers." Also "You are responsible for those squads: what they work on, in what order, and how your people and teams grow." Also "You will quickly find opportunities to expand your teams, and must have a strong perspective on how to hire amazing people." Also "You will hire the new generation of AI-augmented Omadans." Also "You will manage millions of dollars in annual vendor budget and spending, through key contracts including Amazon Web Services, Datadog, Gitlab, and Anthropic." Also "You will be responsible for annual internal and external audit controls, and must help your teams develop automation and evidence management processes to streamline audit responses." Also "You will manage millions of dollars in annual vendor budget and spending, through key contracts including Amazon Web Services, Datadog, Gitlab, and Anthropic." Also "You will be responsible for annual internal and external audit controls, and must help your teams develop automation and evidence management processes to streamline audit responses." Also "You will manage millions of dollars in annual vendor budget and spending, through key contracts including Amazon Web Services, Datadog, Gitlab, and Anthropic." Ok. Now we need to format. We'll start with a

  for mission statement and job overview summary. Then

  About the role

  maybe containing a short paragraph summarizing role? But we already have overview. Could put overview there. Better:

  About the role

  ... (job overview)

  Then

  Responsibilities

  • ... each duty
  Then

  Requirements

  • ... each requirement
  Then

  Skills

  • ... technologies
  Then

  Benefits

  • ... benefits
  Then

  Pay

  ... salary ranges

  We must not repeat job title. Ensure no duplicate lines. We need to extract responsibilities list from "What you'll be doing:" bullet-like sentences. Let's list them: - Managing, Hiring, and Mentoring. You will lead 5 people. You will quickly find opportunities to expand your teams, and must have a strong perspective on how to hire amazing people. Meanwhile, you must ensure that the people who work on your teams today continue growing and challenging themselves. - Own the squad's delivery. Sprint shaping, prioritization, backlog grooming, and estimation are yours. Make the calls, write them down, and be accountable for them. - Own cycle time at constant or better quality. Your squad's contribution to it is yours to move and yours to explain. - Ship code. Production work every sprint, off the critical path, using the same agent workflows your squad uses. This is what keeps the standing to review their work and the credibility to defend the model. - Grow your engineers. Omadans care about each other: we believe everyone can grow, and you will provide your reports with the best leadership they have ever experienced. - Own the operational health of your squad. On-call rotations, MTTR and post-incident analysis are shared work you lead. - Escalate early, often, and precisely. You bring tradeoffs, you use your engineering and product taste to come up with recommendations. - You will hire the new generation of AI-augmented Omadans. We believe in co-intelligence: we will continue hiring amazing humans, and help them build a career with us. Also earlier: "You partner closely with stakeholders across Engineering, Product, Design, IT, InfoSec, Legal, Compliance, Procurement, and beyond. Your relationships with the people in those departments will be very important. You will manage millions of dollars in annual vendor budget and spending, through key contracts including Amazon Web Services, Datadog, Gitlab, and Anthropic. You will be responsible for annual internal and external audit controls, and must help your teams develop automation and evidence management processes to streamline audit responses." These could be responsibilities as well. We'll include them. Now requirements list from "What you need for this role:": - 8+ years in software engineering, including at least 2 years managing engineers, or equivalent experience leading delivery for a team you were accountable for. - A track record shipping mission-critical software to production, and living with it afterwards: we all make mistakes, what separates you from others is that you own these, and use this as an opportunity to build something even greater. - The ability to build a roadmap, plan for capacity, evaluate trade-offs, and know how to negotiate with your stakeholders. - 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 (Multi-account AWS, self-managed continuous integration, k8s, backend (Ruby, Python, ...), GitOps release management, internal tools and services) with enough range to follow the conversation in the others and review architecture decisions critically. - 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. - A Security-mentality in everything you design and build - Excellent written communication. Much of this job is writing things down clearly once so they do not have to be discussed four times. Also maybe "You are comfortable being accountable for what your squad ships. You still write code, and you want to." That's more about you but could be in About you but we can include in Requirements or Qualifications. But we have a separate "About you" section earlier. Could treat as Qualifications. But we can combine. We'll create Requirements section with those bullet points. Skills: "Technologies we use:" list: - Architecture & Infrastructure: AWS (EKS, IAM, RDS, SQS, etc), Docker, GitLab, Argo/Kargo, Vault, Datadog, PagerDuty. - Application Engineering: Ruby on Rails, Python (Flask, FastAPI), React, native iOS (Swift, SwiftUI), native Android (Kotlin), PostgreSQL, GraphQL, Claude We can list each as separate
• maybe grouping. Benefits list: from "Benefits:" bullet list: - Competitive salary with generous annual cash bonus - Equity grants - Employee stock purchasing plan (ESPP) - Remote first work from home culture - Flexible Time Off to help you rest, recharge, and connect with loved ones - Generous parental leave - Health, dental, and vision insurance (and above market employer contributions) - 401k retirement savings plan - Lifestyle Spending Account (LSA) - Mental Health Support Solutions...and more! We'll include those. Pay: salary ranges: - Zone 1: $179,400 - $224,250 - Zone 2: $171,600 - $214,500 - Zone 3: $156,000 - $195,000 We'll put in

  . Now we need to ensure we don't include boilerplate like "It takes a village to change health care..." etc. That's values; maybe we can keep as a short paragraph under About the role? It's substantive but not required sections. Could include as a

  after About the role before Responsibilities. But we must not create extra headings unless needed. We can just include a paragraph. Also "About Omada Health: ..." is company description; could be included as a paragraph. We must not include EEO statement etc. Let's craft. HTML:

  Omada Health is on a mission to bend the curve of chronic disease.

  About the role

  We are hiring an Engineering Manager to lead two squads building Omada’s Platform and Engineering Systems. These squads own problems from prototype to production, including maintenance and on‑call rotation for what they ship. You are responsible for those squads: what they work on, in what order, and how your people and teams grow. As an Engineering Manager, you ship code alongside your AI‑powered engineers. You own the execution and will run the squad’s rituals: iteration shaping, prioritization, backlog refinement, and initiative estimation are your calls. Being in charge means you have an opinion about the tradeoffs you and the squad