Implementation Director

We need to output HTML fragment with sections: About the role? Actually the posting includes "Why Clarium?" (company description), "The Opportunity", "In This Role You Will", "What You'll Bring", "What You Get At Clarium". Also maybe "Benefits", "Pay", "Schedule". We need to use

for section headings. Do not repeat job title as heading (the page already shows it). No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes an "Equal Opportunity Statement" at end – that's boilerplate, remove. We need to preserve all substantive information. So we need sections: About the role? Could be "About the role" maybe from "The Opportunity". Could also have "Responsibilities" from "In This Role You Will". "Requirements" from "What You'll Bring". "Benefits" from "What You Get At Clarium". "Pay" from salary range. "Schedule" maybe not present (no schedule details). So we should not create Schedule section if not present. Benefits: we have list of benefits: Fully remote, NYC co-working space, distributed team, unlimited PTO, top-tier health/vision/dental, 401K, equity, etc. Pay: target base salary range $140K - 170K, plus equity. Also mention that base salary may vary, total package includes equity, etc. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must not emit sections with filler like "commensurate with experience". We have concrete info. We need to decide headings: Use

  for each section heading. Possible sections: About the role (or maybe "About Clarium"? The posting starts with "Why Clarium?" which is company description. Could be "About the role" or "About the company". The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We have: - About the role: maybe the "Why Clarium?" and "The Opportunity" combined? Actually "Why Clarium?" is company overview. Could be "About the role" but that seems odd. However we can use "About the role" to describe the role overview (The Opportunity). Could also have "About Clarium" but not in list. Probably better to use "About the role" for the role overview (The Opportunity). Then "Responsibilities" for the bullet list under "In This Role You Will". Then "Requirements" or "Qualifications" for "What You'll Bring". Then "Benefits" for benefits list. Then "Pay" for salary range. Possibly also "Skills" but we can incorporate into Requirements. We must not create sections without real content. So we will have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Check if we need "Qualifications" separate? Could combine with Requirements. We'll just use Requirements. Now extract content. About the role: Should include description of role: "The Implementation Director owns end-to-end delivery for a portfolio of Clarium's enterprise health system accounts, from signed contract through go-live and into steady-state handoff to the Customer Success team. You will personally run implementations, owning your own account portfolio directly, split by account rather than by segment or product line. Your scope spans initial implementation success, the criteria needed to grow the account, and new product rollouts and expansions, working cross-functionally with Product, Engineering, Sales, and Customer Experience to keep commitments realistic and delivery on track, without formal authority over any of those teams." Also maybe include "Why Clarium?" description? That is company overview, not role. But we could include in About the role? Might be better to have a separate "About Clarium" but not allowed headings. However we could incorporate company description into About the role as context. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview into About the role section. Thus About the role paragraph: combine why Clarium and the opportunity. Now Responsibilities: list bullet points from "In This Role You Will". Each bullet is a responsibility. List: - Own the full implementation lifecycle for a portfolio of enterprise health system accounts; kickoff, technical integration coordination, workflow configuration, training, go-live, user adoption, and success evaluation - Build and maintain the implementation project plan, timeline, and risk register for each active account, proactively identifying and mitigating delivery risk - Coordinate cross-functionally with Product, Engineering, Sales, and Customer Experience to keep commitments realistic and delivery on track; without formal authority over any of those teams - Manage executive, user, and clinical stakeholder relationships during the implementation window (CIO, supply chain VP, CFO, project sponsors), including status reporting and escalation management - Make scope and timeline tradeoff decisions when a project hits real constraints — deciding what is removed, what remains, and what gets escalated, and owning the reasoning behind each decision - Own the action plan and internal communication needed to complete any scopes of work that differ meaningfully from Clarium's core products - Ensure a clean handoff into steady-state, so the CSM inheriting the account gets a well-operating customer Now Requirements: from "What You'll Bring". List: - 4-8+ years in implementation, professional services, or technical onboarding, with meaningful time in healthcare, health system, or complex enterprise SaaS environments - Direct, hands-on ownership of enterprise-scale rollouts with multiple stakeholders and real technical complexity - Working fluency with health system IT and clinical operations — EHR/EMR integration exposure (Epic, Oracle Health/Cerner), HL7/FHIR, file exchanges, and how hospital IT and clinical governance actually operate - A track record of building structure where none existed — implementation plans, risk frameworks, status reporting — with the ability to build aspects of Clarium's playbook and make them repeatable We could also include "Skills" but not needed. Now Benefits: from "What You Get At Clarium". List: - Target Base Salary Range: $140K - 170K (but that's Pay, not Benefits) - The base salary may vary depending upon scope and responsibilities and candidate's job-related knowledge, skills, and experience. - The total package will include equity, in addition to a full range of medical and/or other benefits, depending on the position offered. - Pay and benefits are subject to change at any time, consistent with the terms of any applicable compensation or benefit plans. - Incentive Stock Options proportionate to your salary - Fully remote, with a NYC co-working space available; distributed team across multiple time zones with opportunities for in-person time - Unlimited PTO - Top-tier health, vision, and dental benefits - 401K - The opportunity to build on a strong foundational team with deep data and engineering roots at a stage where your work genuinely shapes the product - A fast-paced, high-growth environment where we move quickly to solve critical healthcare challenges - The chance to empower frontline healthcare workers by automating the administrative friction in their day-to-day - Collaborative work alongside a high-caliber team of clinicians, engineers, and revenue leaders We need to separate Pay and Benefits sections. Pay: base salary range and equity, maybe mention that base may vary, total package includes equity. Benefits: the rest (remote, PTO, health, 401K, etc). Also mention "Incentive Stock Options proportionate to your salary" could be part of Pay or Benefits; but it's equity, so Pay. Thus Pay section: include base salary range, equity (ISO), note that base may vary, total package includes equity. Benefits section: list remote, NYC co-working, distributed team, unlimited PTO, top-tier health/vision/dental, 401K, opportunity to build, fast-paced, chance to empower, collaborative work. We should not include boilerplate like "Pay and benefits are subject to change..." maybe that's okay as it's substantive? It's a generic statement but it's part of the posting. It's not filler like "commensurate with experience". It's a statement about variability. Could keep but maybe it's boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The statement about pay and benefits subject to change is not exactly legal boilerplate but could be considered generic. However it's part of the compensation description; I'd keep it as it's substantive about compensation. But we need to avoid filler like "not specified". This is fine. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

  About the role

  ...combined text...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  ...salary range and equity...

  Make sure not to repeat job title. No extra sections. Now craft the About the role paragraph. Combine why Clarium and the opportunity: "Why Clarium? The healthcare industry overspends on its supply chain by over $25B each year, the result of fragmented data, inefficient workflows, and wasted supplies. Clarium is fixing that. Our AI-powered platform, Astra OS, gives hospitals end-to-end visibility into their supply chain operations, automating workflows and surfacing actionable insights so supply chain teams can focus on what matters most: patient care. We're trusted by some of the world's leading health systems, including Yale New Haven Health, Stanford, Geisinger, and Kaiser Permanente. Founded in 2020, Clarium has raised $43M in total funding. Our Series A was led by Northzone, with participation from General Catalyst, AlleyCorp, Kaiser Permanente Ventures, Texas Medical Center Ventures, and 1984 Ventures. The Opportunity: The Implementation Director owns end-to-end delivery for a portfolio of Clarium's enterprise health system accounts, from signed contract through go-live and into steady-state handoff to the Customer Success team. You will personally run implementations, owning your own account portfolio directly, split by account rather than by segment or product line. Your scope spans initial implementation success, the criteria needed to grow the account, and new product rollouts and expansions, working cross-functionally with Product, Engineering, Sales, and Customer Experience to keep commitments realistic and delivery on track, without formal authority over any of those teams." We can combine into one paragraph or two paragraphs. Use

  for prose; we can have multiple

  inside section? Probably okay. We'll put one

  with the combined text. Now Responsibilities list as above. Now Requirements list. Now Benefits list. Now Pay paragraph. Let's craft Benefits list items: - Fully remote, with a NYC co-working space available; distributed team across multiple time zones with opportunities for in-person time - Unlimited PTO - Top-tier health, vision, and dental benefits - 401K - The opportunity to build on a strong foundational team with deep data and engineering roots at a stage where your work genuinely shapes the product - A fast-paced, high-growth environment where we move quickly to solve critical healthcare challenges - The chance to empower frontline healthcare workers by automating the administrative friction in their day-to-day - Collaborative work alongside a high-caliber team of clinicians, engineers, and revenue leaders Pay paragraph: - Target Base Salary Range: $140K - 170K. The base salary may vary depending upon the ultimate scope and responsibilities of the position and on the candidate's