Director/Sr. Director Engineering- Growth + Consumer
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment.
Let's extract content.
About Midi Health description: "Midi Health is transforming healthcare for women in midlife, delivering expert, personalized care through a virtual-first platform built around the needs of women in perimenopause and menopause. We’re growing quickly, and technology is at the center of how we reach more patients, create an exceptional care experience, and scale access to high-quality care nationwide. We’re looking for leaders who are excited to build at that intersection of healthcare, technology, and consumer experience."
That's about the company, not role. But we could put under About the role? Might be okay. The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview there.
The Role description: "We’re looking for a Director of Engineering, Growth & Consumer to lead the engineering teams behind Midi’s patient experience — from the moment someone first discovers Midi through registration, onboarding, booking, and ongoing engagement with their care. This is a true player-coach role. You’ll lead and develop a high-performing engineering team while staying close to the technology: shaping architecture, reviewing code, using AI coding tools, and helping your team solve hard problems. You’ll also be a senior engineering partner to Product, Marketing, Design, Data Science, and Clinical leaders. We expect our engineering leaders to think beyond their immediate teams, contribute to company-wide technical decisions, and help shape how we build as Midi scales."
That's also role overview.
We can combine both into About the role paragraph(s). Use
for prose.
Responsibilities: "What You’ll Own:" list:
- Lead the engineering roadmap and execution for Midi’s consumer and growth experiences, including registration, onboarding, appointment booking, patient engagement, prescription and supplement commerce, and growth loops.
- Build and lead high-performing engineering teams with a culture of ownership, accountability, speed, and high technical standards.
- Stay hands-on with the technology through architecture decisions, code reviews, prototyping, and AI-assisted development.
- Partner closely with Product, Marketing, Design, and Data Science to translate business and patient needs into scalable technical solutions.
- Drive engineering quality, velocity, reliability, and operational health across your area.
- Hire, mentor, and develop engineers and engineering leaders as the organization grows.
- Collaborate with engineering leaders across Midi to make thoughtful decisions for the broader technology organization — not just your individual area.
- Help define how Midi uses AI and modern development tools to fundamentally improve how software is built.
We need to put each as
- inside
.
Requirements: "What We’re Looking For:" list:
- Deep software engineering foundation. You’ve spent meaningful time as a senior individual contributor building sophisticated applications and consumer-facing experiences.
- Proven engineering leadership. You have 5+ years of engineering management experience and have led organizations of 10+ engineers.
- Player-coach mindset. You’re comfortable operating at the leadership level while remaining technically credible and close enough to the work to help your team make better decisions.
- Strong product and consumer instincts. You understand that great engineering isn’t just about technical elegance — it’s about building experiences that drive meaningful outcomes for users and the business.
- Executive-level communication and judgment. You can confidently partner with senior leaders, navigate ambiguity, influence direction, and communicate technical tradeoffs clearly.
- Exceptional cross-functional instincts. You naturally build trust with Product, Design, Marketing, Data Science, and other non-engineering partners.
- AI-native approach to engineering. You’ve recently built or shipped something meaningful using AI coding agents and have a practical understanding of how AI is changing what engineering teams can accomplish.
- First-principles thinking. You ask the right questions, communicate clearly, and align early rather than building in isolation.
- Strong ownership mindset. You close loops, take accountability for outcomes, and step into problems rather than waiting for someone else to solve them.
We need to keep each as - .
Qualifications: Nice to Have list:
- Experience leading Growth Engineering, Consumer Engineering, Martech, or digital commerce teams.
- Experience building high-scale consumer products where conversion, engagement, retention, or experimentation are core to the business.
- Experience with Python, Django, React, and AWS.
- Experience working in healthcare, fintech, or another regulated environment.
- Experience building experimentation platforms, personalization systems, or AI-powered consumer experiences.
We could put these under Qualifications heading.
Skills: Could we separate technical skills? Might be redundant. But we could still have Skills heading listing specific technologies: Python, Django, React, AWS, AI coding tools, etc. However the Nice to Have already includes those. To avoid duplication, maybe we put Skills as a subsection of Qualifications? But instruction: Prefer a few substantive sections over many thin ones. Could combine Nice to Have into Qualifications and not have separate Skills. However we need to include Skills heading only if there is real specific content. We could extract skills from the requirements: "Deep software engineering foundation", "Proven engineering leadership", etc. Those are more competencies than skills. Might be better to have Skills heading listing specific technologies: Python, Django, React, AWS, AI coding tools. But those are already in Nice to Have. To avoid duplication, we could still include them under Skills, but that would repeat content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we could keep Qualifications as Nice to Have and not have Skills. But the instruction says we must use headings from list when appropriate. If we don't have specific content for Skills, we should omit it. So we can omit Skills.
Benefits: The posting says: "In addition to base salary, employees are eligible for a wide range of benefits and equity in the company". Also "Why Midi" includes opportunity to shape etc. But we can capture benefits as that sentence. Also equity mentioned. We'll put that as
under Benefits.
Pay: Salary range: $250,000-325,000 per year, based on factors such as experience and skills. Also mention equity. We'll put that.
Schedule: Hybrid, 2 days/week in San Francisco OR Palo Alto office. Also location: San Francisco Bay Area. We'll put that.
We must not include boilerplate like visa sponsorship, EEO, legal, etc.
Now construct HTML.
We'll start with
About the role
then ... combine company overview and role overview maybe two paragraphs.
Then
Responsibilities
with items.
Then Requirements
with items.
Then Qualifications
with Nice to Have items.
Then Benefits
... (wide range of benefits and equity).
Then
Pay
... salary range and equity.
Then
Schedule
... hybrid schedule.
Make sure no extra whitespace issues.
Let's craft the prose.
About the role paragraph(s):
First paragraph: Company overview.
Second paragraph: Role overview.
We'll put them as separate
elements.
Now Responsibilities list items exactly as given.
Requirements list items.
Qualifications list items.
Benefits paragraph: "In addition to base salary, employees are eligible for a wide range of benefits and equity in the company."
Pay paragraph: "The estimated salary range for this role is $250,000-325,000 per year, based on factors such as experience and skills. In addition to base salary, employees are eligible for equity in the company."
But note we already mentioned equity in benefits; could mention again but okay.
Schedule paragraph: "Hybrid work model: 2 days per week in either the San Francisco or Palo Alto office, located in the San Francisco Bay Area."
Now ensure we didn't include any boilerplate like "At Midi Health, we are committed to pay transparency and equity." That's part of pay? Actually that is a statement about pay transparency. Could be considered part of Pay section? It's about pay philosophy. Might be considered substantive. But we already have Pay section with salary range. The statement about commitment to pay transparency and equity could be included in Pay section as extra sentence. However the instruction: do not emit filler/placeholder text. This is not filler. It's a statement about policy. Could include.
But we also have "At this time, Midi is unable to provide visa sponsorship. All Candidates must be authorized to work in the United States without current or future sponsorship needs." That's legal/visa info, should be removed.
Also "Please note that all official communication from Midi Health will come from an @joinmidi.com email address. We will never ask for payment of any kind during the application or hiring process. If you receive any suspicious communication claiming to
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment. Let's extract content. About Midi Health description: "Midi Health is transforming healthcare for women in midlife, delivering expert, personalized care through a virtual-first platform built around the needs of women in perimenopause and menopause. We’re growing quickly, and technology is at the center of how we reach more patients, create an exceptional care experience, and scale access to high-quality care nationwide. We’re looking for leaders who are excited to build at that intersection of healthcare, technology, and consumer experience." That's about the company, not role. But we could put under About the role? Might be okay. The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview there. The Role description: "We’re looking for a Director of Engineering, Growth & Consumer to lead the engineering teams behind Midi’s patient experience — from the moment someone first discovers Midi through registration, onboarding, booking, and ongoing engagement with their care. This is a true player-coach role. You’ll lead and develop a high-performing engineering team while staying close to the technology: shaping architecture, reviewing code, using AI coding tools, and helping your team solve hard problems. You’ll also be a senior engineering partner to Product, Marketing, Design, Data Science, and Clinical leaders. We expect our engineering leaders to think beyond their immediate teams, contribute to company-wide technical decisions, and help shape how we build as Midi scales." That's also role overview. We can combine both into About the role paragraph(s). Use
for prose. Responsibilities: "What You’ll Own:" list: - Lead the engineering roadmap and execution for Midi’s consumer and growth experiences, including registration, onboarding, appointment booking, patient engagement, prescription and supplement commerce, and growth loops. - Build and lead high-performing engineering teams with a culture of ownership, accountability, speed, and high technical standards. - Stay hands-on with the technology through architecture decisions, code reviews, prototyping, and AI-assisted development. - Partner closely with Product, Marketing, Design, and Data Science to translate business and patient needs into scalable technical solutions. - Drive engineering quality, velocity, reliability, and operational health across your area. - Hire, mentor, and develop engineers and engineering leaders as the organization grows. - Collaborate with engineering leaders across Midi to make thoughtful decisions for the broader technology organization — not just your individual area. - Help define how Midi uses AI and modern development tools to fundamentally improve how software is built. We need to put each as
- .
Requirements: "What We’re Looking For:" list:
- Deep software engineering foundation. You’ve spent meaningful time as a senior individual contributor building sophisticated applications and consumer-facing experiences.
- Proven engineering leadership. You have 5+ years of engineering management experience and have led organizations of 10+ engineers.
- Player-coach mindset. You’re comfortable operating at the leadership level while remaining technically credible and close enough to the work to help your team make better decisions.
- Strong product and consumer instincts. You understand that great engineering isn’t just about technical elegance — it’s about building experiences that drive meaningful outcomes for users and the business.
- Executive-level communication and judgment. You can confidently partner with senior leaders, navigate ambiguity, influence direction, and communicate technical tradeoffs clearly.
- Exceptional cross-functional instincts. You naturally build trust with Product, Design, Marketing, Data Science, and other non-engineering partners.
- AI-native approach to engineering. You’ve recently built or shipped something meaningful using AI coding agents and have a practical understanding of how AI is changing what engineering teams can accomplish.
- First-principles thinking. You ask the right questions, communicate clearly, and align early rather than building in isolation.
- Strong ownership mindset. You close loops, take accountability for outcomes, and step into problems rather than waiting for someone else to solve them.
We need to keep each as
- .
Qualifications: Nice to Have list:
- Experience leading Growth Engineering, Consumer Engineering, Martech, or digital commerce teams.
- Experience building high-scale consumer products where conversion, engagement, retention, or experimentation are core to the business.
- Experience with Python, Django, React, and AWS.
- Experience working in healthcare, fintech, or another regulated environment.
- Experience building experimentation platforms, personalization systems, or AI-powered consumer experiences.
We could put these under Qualifications heading.
Skills: Could we separate technical skills? Might be redundant. But we could still have Skills heading listing specific technologies: Python, Django, React, AWS, AI coding tools, etc. However the Nice to Have already includes those. To avoid duplication, maybe we put Skills as a subsection of Qualifications? But instruction: Prefer a few substantive sections over many thin ones. Could combine Nice to Have into Qualifications and not have separate Skills. However we need to include Skills heading only if there is real specific content. We could extract skills from the requirements: "Deep software engineering foundation", "Proven engineering leadership", etc. Those are more competencies than skills. Might be better to have Skills heading listing specific technologies: Python, Django, React, AWS, AI coding tools. But those are already in Nice to Have. To avoid duplication, we could still include them under Skills, but that would repeat content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we could keep Qualifications as Nice to Have and not have Skills. But the instruction says we must use headings from list when appropriate. If we don't have specific content for Skills, we should omit it. So we can omit Skills.
Benefits: The posting says: "In addition to base salary, employees are eligible for a wide range of benefits and equity in the company". Also "Why Midi" includes opportunity to shape etc. But we can capture benefits as that sentence. Also equity mentioned. We'll put that as
under Benefits. Pay: Salary range: $250,000-325,000 per year, based on factors such as experience and skills. Also mention equity. We'll put that. Schedule: Hybrid, 2 days/week in San Francisco OR Palo Alto office. Also location: San Francisco Bay Area. We'll put that. We must not include boilerplate like visa sponsorship, EEO, legal, etc. Now construct HTML. We'll start with
About the role
then... combine company overview and role overview maybe two paragraphs. Then
Responsibilities
- with items.
Then
Requirements
- with items.
Then
Qualifications
- with Nice to Have items.
Then
Benefits
... (wide range of benefits and equity). Then
Pay
... salary range and equity. Then
Schedule
... hybrid schedule. Make sure no extra whitespace issues. Let's craft the prose. About the role paragraph(s): First paragraph: Company overview. Second paragraph: Role overview. We'll put them as separate
elements. Now Responsibilities list items exactly as given. Requirements list items. Qualifications list items. Benefits paragraph: "In addition to base salary, employees are eligible for a wide range of benefits and equity in the company." Pay paragraph: "The estimated salary range for this role is $250,000-325,000 per year, based on factors such as experience and skills. In addition to base salary, employees are eligible for equity in the company." But note we already mentioned equity in benefits; could mention again but okay. Schedule paragraph: "Hybrid work model: 2 days per week in either the San Francisco or Palo Alto office, located in the San Francisco Bay Area." Now ensure we didn't include any boilerplate like "At Midi Health, we are committed to pay transparency and equity." That's part of pay? Actually that is a statement about pay transparency. Could be considered part of Pay section? It's about pay philosophy. Might be considered substantive. But we already have Pay section with salary range. The statement about commitment to pay transparency and equity could be included in Pay section as extra sentence. However the instruction: do not emit filler/placeholder text. This is not filler. It's a statement about policy. Could include. But we also have "At this time, Midi is unable to provide visa sponsorship. All Candidates must be authorized to work in the United States without current or future sponsorship needs." That's legal/visa info, should be removed. Also "Please note that all official communication from Midi Health will come from an @joinmidi.com email address. We will never ask for payment of any kind during the application or hiring process. If you receive any suspicious communication claiming to