Applied AI Lead (Account Management)
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: "Who We Are" maybe considered company description; we could include as a
before sections? The instruction: output only HTML fragment, we can include a
for company overview? It's not a heading; we can include as a paragraph before sections. It's substantive. Should we include? It says preserve ALL substantive information; do not invent or summarize away detail. So we should include the "Who We Are" paragraph(s). It's not a heading; we can put it as a
. Then headings for sections.
Let's extract content.
Who We Are paragraph(s):
"Heidi is building an AI Care Partner that works alongside clinicians to make that possible. We’re a team of doctors, engineers, designers, researchers, and creatives building tools that help clinicians stay focused on what matters most: their patients. In just 18 months, Heidi has given back more than 18 million hours to healthcare professionals — supporting 73 million patient visits in 116 countries. Today, more than two million patient visits each week are powered by Heidi worldwide. Backed by nearly $100 million in funding, we’re growing in the US, UK, Canada, and Europe, partnering with leading health systems including the NHS, Beth Israel Lahey Health, and Monash Health."
That's the "Who We Are". We'll put as
.
About The Role: after "About The Role" heading, there is paragraph: "We’re looking for an Applied AI Lead to deliver results across Heidi’s most complex customer deployments and growth opportunities. As a senior individual contributor on Heidi’s US Applied AI team, you’ll own strategic customer relationships within a specialty-focused pod and help improve how the broader team deploys, drives adoption, and expands the use of AI. This is a quota-carrying, consultative deployment and account management role. You’ll lead ambiguous customer engagements from discovery through implementation, expansion, and renewal, partnering with Clinical Engineers to develop solutions that create measurable clinical and operational value. You’ll bring deep product expertise, strong commercial judgment, and a track record of solving difficult problems independently. Your impact will extend beyond your own portfolio through better processes, actionable customer insights, and mentorship of less experienced colleagues."
We'll put that as
under
About the role
.
Responsibilities: from "What you'll do" bullet list. Let's extract each bullet:
- Own complex, strategic accounts. Build trusted relationships with executives, clinicians, and operational leaders, aligning stakeholders around clear transformation plans and measurable outcomes.
- Pursue the highest-value growth opportunities. Independently identify and advance opportunities for adoption, expansion, and renewal, challenging low-impact work and focusing effort where it can deliver the strongest return.
- Lead discovery and solution scoping. Run live product demonstrations and initial discovery independently, explain capabilities and limitations, and bring Clinical Engineers into deeper technical design and implementation.
- Solve ambiguous deployment challenges. Identify root causes, develop practical options, recommend a path forward, and bring a proposed next step to each issue you raise.
- Deliver complex initiatives end to end. Coordinate dependencies across customers and internal teams, track progress, surface risks early, and adjust plans to protect delivery and customer value.
- Apply deep product understanding. Use Heidi’s products routinely and understand the roadmap, underlying architecture, and clinical logic well enough to identify gaps and opportunities others may miss.
- Shape decisions through customer insight. Bring a detailed understanding of customer workflows, pain points, and buying processes into Product and Clinical Engineering discussions. Proactively develop use cases that increase meaningful usage.
- Improve how the team works. Turn successful approaches into repeatable discovery, deployment, adoption, and account growth practices that improve consistency across the department.
- Mentor and connect colleagues. Support less experienced team members, strengthen relationships between teams, and communicate complex issues clearly enough for others to act.
- Maintain commercial discipline. Own accurate forecasts and account plans for your portfolio, using adoption, utilization, and credit consumption data to anticipate risks and opportunities.
We'll put each as - .
Requirements: from "What we're looking for" bullet list:
- 5+ years of experience in consultative deployment, account management, management consulting, or a related customer-facing technology role, with sustained success in complex engagements.
- A track record of independently resolving ambiguous customer and commercial problems and delivering measurable adoption, retention, or expansion outcomes.
- Deep product fluency, including the ability to lead demonstrations and discovery and connect technical capabilities to clinical and operational needs.
- Experience building executive-level business cases and transformation plans that lead to investment and adoption.
- Strong analytical judgment: you can identify root causes, assess return on investment, and challenge work that will not materially improve outcomes.
- Experience coordinating multi-step initiatives across teams, managing dependencies, and identifying delivery risks before they become missed commitments.
- Evidence of improving processes and translating individual expertise into practices others can use.
- The ability to mentor colleagues and influence across teams without formal management authority.
- Confidence in surfacing disagreement, recommending a clear direction, and committing to the agreed decision.
We'll put as
- .
Qualifications: maybe we could treat "Strongly appreciated, but not required" as qualifications? Actually those are "Strongly appreciated, but not required". Could be considered "Preferred qualifications". We'll make a section "Qualifications" for required? But we already have Requirements. Could make Qualifications for the "Strongly appreciated" items. Let's do that.
Qualifications bullet list:
- Deep familiarity with clinical workflows and healthcare buying processes.
- Experience deploying AI products in healthcare or other complex operational environments.
- Experience growing accounts across both seat-based and usage-based commercial models.
We'll put as
- .
Skills: maybe we could extract from responsibilities? But we already have skills implied. Could make a Skills section for things like "Strong analytical judgment", "Deep product fluency", etc. But to avoid duplication, maybe we skip Skills section unless we have explicit skills list. The posting does not have a separate skills list. So we may omit Skills.
Benefits: from "Why You Will Flourish With Us" list:
- Generous Healthcare, Dental, and Vision benefit options 90%+ paid for by Heidi
- 401k with 3% match
- $100/month Healthy Heidis budget
- $700/year learning & development budget
- Recharge Days after major pushes
- The rare chance to create a global impact as you immerse yourself in one of the leading healthtech startups
We'll put as
- .
Pay: from "Compensation Range: $140K - $165K". We'll put as
maybe.
Schedule: none.
We must not include headings with empty content. So we will include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also a generic "Overview" for Who We Are? Not required but we can include as a
before sections.
We must not repeat job title as heading. Not using.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment.
Let's craft.
We'll start with a
for Who We Are.
Then
About the role
...
Then Responsibilities
...
Then Requirements
...
Then Qualifications
...
Then Benefits
...
Then Pay
Compensation Range: $140K - $165K
Make sure to preserve all details exactly as in text. Check for any missing details: In Who We Are we have "Heidi is building an AI Care Partner that works alongside clinicians to make that possible." etc. Ensure we keep punctuation.
In About the role paragraph we need to keep all sentences.
Check responsibilities bullets: ensure we keep each bullet exactly as in posting. Let's copy them.
Bullet 1: "Own complex, strategic accounts. Build trusted relationships with executives, clinicians, and operational leaders, aligning stakeholders around clear transformation plans and measurable outcomes."
Bullet 2: "Pursue the highest-value growth opportunities. Independently identify and advance opportunities for adoption, expansion, and renewal, challenging low-impact work and focusing effort where it can deliver the strongest return."
Bullet 3: "Lead discovery and solution scoping. Run live product demonstrations and initial discovery independently, explain capabilities and limitations, and bring Clinical Engineers into deeper technical design and implementation."
Bullet 4: "Solve ambiguous deployment challenges. Identify root causes, develop practical options, recommend a path forward, and bring a proposed next step to each issue you raise."
Bullet 5: "Deliver complex initiatives end to end. Coordinate dependencies across customers and internal teams, track progress, surface risks early, and adjust plans to protect delivery and customer value."
Bullet 6: "Apply deep product understanding. Use Heidi’s products routinely and understand the roadmap, underlying architecture, and clinical logic well enough to identify gaps and opportunities others may miss."
Bullet 7: "Shape decisions through customer insight. Bring a detailed understanding of customer workflows, pain points, and buying processes into Product and Clinical Engineering discussions. Proactively develop use cases that increase meaningful usage."
Bullet 8: "Improve how the team works. Turn successful approaches into repeatable discovery, deployment, adoption, and account growth practices that improve consistency across the department."
Bullet 9: "Mentor and connect colleagues. Support less experienced team members, strengthen relationships between teams, and communicate complex issues clearly enough for others to act."
Bullet 10: "Maintain commercial discipline. Own accurate forecasts and account plans for your portfolio, using adoption, utilization, and credit consumption data to anticipate risks and opportunities."
Check for any missing nuance: The original had "You’ll lead ambiguous customer engagements from discovery through implementation, expansion, and renewal, partnering with Clinical Engineers to develop solutions that create measurable clinical and operational value." That's in About the role paragraph, not responsibilities. Good.
Now Requirements bullets:
- "5+ years of experience in consultative deployment, account management, management consulting, or a related customer-facing technology role, with sustained success in complex engagements."
- "A track record of independently resolving ambiguous customer and commercial problems and delivering measurable adoption, retention, or expansion outcomes."
- "Deep product fluency, including the ability to lead demonstrations and discovery and connect technical capabilities to clinical and operational needs."
- "Experience building executive-level business cases and transformation plans that lead to investment and adoption."
- "Strong analytical judgment: you can identify root causes, assess return on investment, and challenge work that will not materially improve outcomes."
- "Experience coordinating multi-step initiatives across teams, managing dependencies, and identifying delivery risks before they become missed commitments."
- "Evidence of improving processes and translating individual expertise into practices others can use."
- "The ability to mentor colleagues and influence across teams without formal management authority."
- "Confidence in surfacing disagreement, recommending a
for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: "Who We Are" maybe considered company description; we could include as a
before sections? The instruction: output only HTML fragment, we can include a
for company overview? It's not a heading; we can include as a paragraph before sections. It's substantive. Should we include? It says preserve ALL substantive information; do not invent or summarize away detail. So we should include the "Who We Are" paragraph(s). It's not a heading; we can put it as a
. Then headings for sections. Let's extract content. Who We Are paragraph(s): "Heidi is building an AI Care Partner that works alongside clinicians to make that possible. We’re a team of doctors, engineers, designers, researchers, and creatives building tools that help clinicians stay focused on what matters most: their patients. In just 18 months, Heidi has given back more than 18 million hours to healthcare professionals — supporting 73 million patient visits in 116 countries. Today, more than two million patient visits each week are powered by Heidi worldwide. Backed by nearly $100 million in funding, we’re growing in the US, UK, Canada, and Europe, partnering with leading health systems including the NHS, Beth Israel Lahey Health, and Monash Health." That's the "Who We Are". We'll put as
. About The Role: after "About The Role" heading, there is paragraph: "We’re looking for an Applied AI Lead to deliver results across Heidi’s most complex customer deployments and growth opportunities. As a senior individual contributor on Heidi’s US Applied AI team, you’ll own strategic customer relationships within a specialty-focused pod and help improve how the broader team deploys, drives adoption, and expands the use of AI. This is a quota-carrying, consultative deployment and account management role. You’ll lead ambiguous customer engagements from discovery through implementation, expansion, and renewal, partnering with Clinical Engineers to develop solutions that create measurable clinical and operational value. You’ll bring deep product expertise, strong commercial judgment, and a track record of solving difficult problems independently. Your impact will extend beyond your own portfolio through better processes, actionable customer insights, and mentorship of less experienced colleagues." We'll put that as
under
About the role
. Responsibilities: from "What you'll do" bullet list. Let's extract each bullet: - Own complex, strategic accounts. Build trusted relationships with executives, clinicians, and operational leaders, aligning stakeholders around clear transformation plans and measurable outcomes. - Pursue the highest-value growth opportunities. Independently identify and advance opportunities for adoption, expansion, and renewal, challenging low-impact work and focusing effort where it can deliver the strongest return. - Lead discovery and solution scoping. Run live product demonstrations and initial discovery independently, explain capabilities and limitations, and bring Clinical Engineers into deeper technical design and implementation. - Solve ambiguous deployment challenges. Identify root causes, develop practical options, recommend a path forward, and bring a proposed next step to each issue you raise. - Deliver complex initiatives end to end. Coordinate dependencies across customers and internal teams, track progress, surface risks early, and adjust plans to protect delivery and customer value. - Apply deep product understanding. Use Heidi’s products routinely and understand the roadmap, underlying architecture, and clinical logic well enough to identify gaps and opportunities others may miss. - Shape decisions through customer insight. Bring a detailed understanding of customer workflows, pain points, and buying processes into Product and Clinical Engineering discussions. Proactively develop use cases that increase meaningful usage. - Improve how the team works. Turn successful approaches into repeatable discovery, deployment, adoption, and account growth practices that improve consistency across the department. - Mentor and connect colleagues. Support less experienced team members, strengthen relationships between teams, and communicate complex issues clearly enough for others to act. - Maintain commercial discipline. Own accurate forecasts and account plans for your portfolio, using adoption, utilization, and credit consumption data to anticipate risks and opportunities. We'll put each asmaybe. Schedule: none. We must not include headings with empty content. So we will include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also a generic "Overview" for Who We Are? Not required but we can include as a
before sections. We must not repeat job title as heading. Not using. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's craft. We'll start with a
for Who We Are. Then
About the role
...
ThenResponsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
Pay
Compensation Range: $140K - $165K
Make sure to preserve all details exactly as in text. Check for any missing details: In Who We Are we have "Heidi is building an AI Care Partner that works alongside clinicians to make that possible." etc. Ensure we keep punctuation. In About the role paragraph we need to keep all sentences. Check responsibilities bullets: ensure we keep each bullet exactly as in posting. Let's copy them. Bullet 1: "Own complex, strategic accounts. Build trusted relationships with executives, clinicians, and operational leaders, aligning stakeholders around clear transformation plans and measurable outcomes." Bullet 2: "Pursue the highest-value growth opportunities. Independently identify and advance opportunities for adoption, expansion, and renewal, challenging low-impact work and focusing effort where it can deliver the strongest return." Bullet 3: "Lead discovery and solution scoping. Run live product demonstrations and initial discovery independently, explain capabilities and limitations, and bring Clinical Engineers into deeper technical design and implementation." Bullet 4: "Solve ambiguous deployment challenges. Identify root causes, develop practical options, recommend a path forward, and bring a proposed next step to each issue you raise." Bullet 5: "Deliver complex initiatives end to end. Coordinate dependencies across customers and internal teams, track progress, surface risks early, and adjust plans to protect delivery and customer value." Bullet 6: "Apply deep product understanding. Use Heidi’s products routinely and understand the roadmap, underlying architecture, and clinical logic well enough to identify gaps and opportunities others may miss." Bullet 7: "Shape decisions through customer insight. Bring a detailed understanding of customer workflows, pain points, and buying processes into Product and Clinical Engineering discussions. Proactively develop use cases that increase meaningful usage." Bullet 8: "Improve how the team works. Turn successful approaches into repeatable discovery, deployment, adoption, and account growth practices that improve consistency across the department." Bullet 9: "Mentor and connect colleagues. Support less experienced team members, strengthen relationships between teams, and communicate complex issues clearly enough for others to act." Bullet 10: "Maintain commercial discipline. Own accurate forecasts and account plans for your portfolio, using adoption, utilization, and credit consumption data to anticipate risks and opportunities." Check for any missing nuance: The original had "You’ll lead ambiguous customer engagements from discovery through implementation, expansion, and renewal, partnering with Clinical Engineers to develop solutions that create measurable clinical and operational value." That's in About the role paragraph, not responsibilities. Good. Now Requirements bullets: - "5+ years of experience in consultative deployment, account management, management consulting, or a related customer-facing technology role, with sustained success in complex engagements." - "A track record of independently resolving ambiguous customer and commercial problems and delivering measurable adoption, retention, or expansion outcomes." - "Deep product fluency, including the ability to lead demonstrations and discovery and connect technical capabilities to clinical and operational needs." - "Experience building executive-level business cases and transformation plans that lead to investment and adoption." - "Strong analytical judgment: you can identify root causes, assess return on investment, and challenge work that will not materially improve outcomes." - "Experience coordinating multi-step initiatives across teams, managing dependencies, and identifying delivery risks before they become missed commitments." - "Evidence of improving processes and translating individual expertise into practices others can use." - "The ability to mentor colleagues and influence across teams without formal management authority." - "Confidence in surfacing disagreement, recommending a