Customer Delivery Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, maybe Benefits, etc. Must not repeat job title. Must not include metadata like Job ID. Must include only sections with real content. We need to parse the posting. First, there is "Our Mission ..." paragraph. That's likely about company mission, not a section heading. Could be part of "About the role"? Actually there is "About The Role" heading later. The initial mission paragraph could be considered "About the company" but not required. We can include as a

before sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Thus we need to decide which sections to include: About the role (maybe from "About The Role" paragraph). Responsibilities (the bullet list under "The Role (What You'll Be Doing)"). Requirements (the "Requirements - Core Skills (Must Have)" and "Preferred/Bonus Skills (Nice To Have)" plus maybe "What Makes You A Great Fit"? That could be Qualifications or Skills. Benefits (the "Perks And Benefits" paragraph). Possibly Pay and Schedule: not given specific numbers, only "Competitive salary based on location and experience." That's vague but still mentions salary. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary based on location and experience." That's a statement about pay, albeit not specific. Should we include Pay section? It says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive salary based on location and experience" is somewhat vague but not exactly placeholder like "commensurate with experience". It's a statement that salary is competitive based on location/experience. Might be considered substantive enough? The instruction says prefer a few substantive sections over many thin ones. Could combine Pay into Benefits? But they said Benefits separate. Could include Benefits section with the perks paragraph, and maybe include Pay as a short p inside Benefits? But they said use

  • for any list of duties/requirements/benefits, and

    for prose. Benefits could be a list. The perks paragraph includes multiple items: Competitive salary..., Comprehensive health coverage..., Fully remote role..., Based in Southern California... That's more like prose. Could make a

    • for each perk. Schedule: not mentioned. So omit Schedule. Qualifications: Could be covered by Requirements and What Makes You A Great Fit. Could have a Qualifications section combining those? But we already have Requirements. Could have Skills section for core skills? But we have Requirements - Core Skills (Must Have) and Preferred/Bonus Skills. Could treat Requirements as a section with sublists. We need to avoid duplication. Let's extract content. Mission paragraph: "Our Mission Salt AI is building the intelligence layer for the enterprise, starting with life sciences. In a world where AI is fragmented across models, tools, and data silos, Salt unifies them through a compliance-first orchestration platform that lets regulated organizations deploy AI securely, at scale, and with confidence. We're creating the backend systems that power real-world AI workflows across drug discovery, clinical development, and commercial operations. Our platform turns complex, regulated environments into intelligent, adaptive systems where autonomous AI agents operate in harmony with existing infrastructure." That's substantive. Could be placed as a

      before sections, maybe as an introductory paragraph. Not a heading. Then "About The Role" heading: paragraph: "As a Customer Delivery Lead, you own our most strategic enterprise deployments end to end — from initial scoping through production go-live and customer self-sufficiency. Reporting to the Chief Customer Officer, you'll work with leading pharma, biotech, investment banking, and energy enterprises deploying Salt into demanding SaaS, VPC, and on-prem environments. This is a senior, judgment-heavy role. You define what we're building, negotiate what we're not, direct the Forward Deployed Engineers and Customer Solutions Engineers assigned to your accounts, and hold the line when a customer pushes to expand scope mid-engagement. You'll keep engagement detail current in our existing AI-first project management flow (Slack → Notion → Linear), where engineers groom their own tickets — so your time goes to scoping and direction, not ticket administration." That's substantive. Could be under

      About the role

      and then

      ... (maybe multiple paragraphs). We'll keep as one

      . Then "The Role (What You'll Be Doing)" heading: then a list of responsibilities (each sentence ends with a period). We'll convert to

      • items. List: - Scope engagements down to one or two named workflows with fixed timelines, and drive customer stakeholders to converge on them quickly. - Define the engagement exit before work begins: what customer self-sufficiency looks like, written down and agreed. - Own SOW terms and the deal scope boundary — including the authority to decline out-of-scope asks from senior customer stakeholders. - Run post-engagement debriefs and drive field learning back into product and platform priorities. - Provide and leadership, prioritization, and technical direction to the Forward Deployed Engineers and Customer Solutions Engineers assigned to your accounts. (Note: grammar weird: "Provide and leadership" maybe typo; keep as is.) - Lead executive communication with customer sponsors throughout the engagement lifecycle. - Stay engaged after go-live on the technical outcome — adoption depth and scoping the next workflow. - Sales owns the account relationship and review cadence. - Partner with Sales on expansion: they lead the pursuit, you control what can be committed on scope, timeline, and capacity. - Own the SOW Approval Gate on new and expansion business — no contract or SOW goes to a customer without your sign-off on scope, timeline, and capacity. - Build reusable delivery patterns — templates, integration components, and reference architectures that make each subsequent engagement faster. - Work with the account's Executive Advisor to bring domain expertise into scoping and validate outputs where correctness depends on it. We'll output each as
      • . Then "Requirements - Core Skills (Must Have)" heading: list of must-have items: - 5+ years owning complex enterprise technical deployments end to end — as a forward deployed engineer, technical program manager, solutions architect, or delivery lead at a technical consultancy or enterprise software company. - Technical fluency: enough depth in cloud architecture, APIs, data pipelines, and integration patterns to scope work credibly and direct engineers without needing translation. Engineering or technical background required. - Scope discipline: demonstrated ability to hold a line against pressure from senior stakeholders, and the judgment to know when holding is right. - Written communication and document hygiene: scopes, exit criteria, and decisions live in writing, not in your head. - Executive presence: credible in the room with VP- and C-level customer sponsors at large enterprises. - Comfort with ambiguity: our customers often don't know their highest-value use case when we arrive, and finding it is part of the job. Then "Preferred/Bonus Skills (Nice To Have)" list: - Experience with on-premise, VPC, or air-gapped deployments in regulated industries — pharma, life sciences, financial services, or government. - Familiarity with GxP, HIPAA, SOC 2, or similar compliance and validation frameworks. - Background at a company running a forward deployed engineering model. - Hands-on experience with AI/ML workflows, model deployment, or agent orchestration. - Track record turning one-off engagements into repeatable delivery motions. Then "What Makes You A Great Fit" paragraph: list of bullet-like statements but not formatted as list. Could be turned into
        • as well? It's a series of statements each starting with "You". Could treat as
          • . But the instruction: Use
            • for any list of duties/requirements/benefits. This is a list of traits, could be considered requirements/qualifications. Might be better as a
              • under a section like "Qualifications" or "Skills". But we already have Requirements section. Could add another section "Qualifications" for these fit statements. However we might combine them into Requirements as "Nice-to-have" but they are more about fit. Safer to create a section "Qualifications" with those statements as
                • . But we must not create filler sections. This section has real content. Alternatively, we could treat "What Makes You A Great Fit" as a

                  paragraph containing multiple sentences. But it's a list; better as list. Then "Perks And Benefits" paragraph: list of benefits: - Competitive salary based on location and experience. - Comprehensive health coverage, including medical, dental, mental health. - Fully remote role, collaborating primarily within U.S. time zones. - Based in Southern California, Salt AI is pioneering the future of life sciences with advanced AI. Founded in 2024 by Aber Whitcomb and Jim Benedetto—veterans of MySpace, Jam City, Gravity, and Core Scientific—our leadership team brings over 15 years of collaboration. We’re not just building products, but transforming what’s possible in research and discovery. We value diverse perspectives and are committed to an inclusive team. If you’re excited about shaping the future of AI in life sciences, we'd love to connect with you. That last part is more marketing fluff; but still part of benefits? Might be considered boilerplate? It's not EEO etc. It's company overview. Could be included as a

                  after benefits list. We need to avoid duplication: The mission paragraph earlier already covered similar company overview. The benefits paragraph repeats some of that. Might be okay to keep both but avoid duplication? The instruction: Remove duplicated lines. The benefits paragraph includes company founding details that are similar to mission but not identical. Might be okay. We need to decide sections: About the role, Responsibilities, Requirements (maybe split into Core Skills and Preferred Skills), Qualifications (What Makes You A Great Fit), Benefits (Perks And Benefits). Possibly also include a short introductory paragraph for mission. We must not include Pay or Schedule sections unless specific. Benefits includes salary mention, okay. We must not include sections with filler like "commensurate with experience". We have "Competitive salary based on location and experience." That's not filler. Now produce HTML fragment. Structure:

                  Our Mission Salt AI is building the intelligence layer for the enterprise, starting with life sciences. In a world where AI is fragmented across models, tools, and data silos, Salt unifies them through a compliance-first orchestration platform that lets regulated organizations deploy AI securely, at scale, and with confidence. We're creating the backend systems that power real-world AI workflows across drug discovery, clinical development, and commercial operations. Our platform turns complex, regulated environments into intelligent, adaptive systems where autonomous AI agents operate in harmony with existing infrastructure.

                  About the role

                  As a Customer Delivery Lead, you own our most strategic enterprise deployments end to end — from initial scoping through production go-live and customer self-sufficiency. Reporting to the Chief Customer Officer, you'll work with leading pharma, biotech, investment banking, and energy enterprises deploying Salt into demanding SaaS, VPC, and on-prem environments. This is a senior, judgment-heavy role. You define what we're building,