Strategic AI adoption lead (East)

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements (What You Need), Benefits (Benefits & Perks), Pay (Compensation Range). Also maybe Schedule? Not present. Travel Requirements note is maybe part of responsibilities? It's a note; but we can include as a short paragraph maybe under Responsibilities? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Travel Requirements is a note; we could include as a paragraph under Responsibilities or maybe a separate small note. But we should not create sections without real content. Travel note is specific content: "Travel Requirements: 25% domestic and international travel may be required." That's substantive. Could be a

under Responsibilities or maybe a separate section "Travel". But we only have prescribed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Travel not in list; we could embed in Responsibilities as a paragraph. We must not repeat job title as heading. The page already shows it, so we don't add heading for title. We need to use

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. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the EEO statement at end, also the "Under the San Francisco Fair Chance Ordinance..." and "By submitting your application..." and "Compensation Range:" maybe we keep as Pay section. We need to include About the role heading? The posting has "🚀 About WRITER" then "📐 About The Role". So we need About the role section with content from that paragraph. The "About WRITER" is company description; maybe we could include that as part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have About the role heading with content describing the role (the paragraph after "About The Role"). We also might include a brief company overview? Not required; but we could include as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive but not part of role. However headings list does not include "About the company". Could we put it under About the role? Might be mixing. But we could include a short paragraph before the role description as part of About the role? The instruction says use headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. It doesn't say we cannot have other headings, but better to stick to those. The company description could be placed as a

  before any heading? The page already shows job title; we could add a

  with company overview then

  About the role>. That seems okay. We must not repeat job title as heading. So we will not add a heading for the title. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Company description (About WRITER): "🚀 About WRITER WRITER is where the world's leading enterprises orchestrate AI-powered work. Our vision is to expand human capacity through superintelligence. And we're proving it's possible – through powerful, trustworthy AI that unites IT and business teams together to unlock enterprise-wide transformation. With WRITER's end-to-end platform, hundreds of companies like Mars, Marriott, Uber, and Vanguard are building and deploying AI agents that are grounded in their company's data and fueled by WRITER's enterprise-grade LLMs. Valued at $1.9B and backed by industry-leading investors including Premji Invest, Radical Ventures, and ICONIQ Growth, WRITER is rapidly cementing its position as the leader in enterprise generative AI. Founded in 2020 with office hubs in San Francisco, New York City, Seattle, Austin, Chicago, and London, our team thinks big and moves fast, and we're looking for smart, hardworking builders and scalers to join us on our journey to create a better future of work with AI." We'll keep that as a

  . Then About The Role paragraph: "📐 About The Role WRITER is looking for a customer success professional who will own deployment and activation success across a customer portfolio. You'll embed deeply into your customers' organizations, understand their business objectives, and build the programs, communities, and frameworks that turn AI investment into measurable outcomes. You'll partner closely with a Transformation lead to identify the right WRITER capabilities for each use case, then design and execute the strategies that drive meaningful adoption: building champion networks, running customized workshops, and advising customers on how to scale their AI programs over time. The ideal candidate brings a builder's mindset to customer success: you're not waiting for customers to engage, you're creating the conditions for it. This is a hybrid role based in our New York City hub." We'll put that under

  About the role

  as

  . Next, What You'll Do (Responsibilities). We need to convert bullet points into

  • . The text includes multiple paragraphs each starting with bold headings. We'll extract each duty. Let's list: Own activation and platform success - Deeply understand each customer's specific use cases, business objectives, and success metrics - Build and co-develop custom AI solutions with customers, translating their specific use cases into workflows that drive measurable business impact - Design and execute activation strategies that drive measurable platform adoption and business outcomes - Implement champion programs, office hours, usage dashboards, customized trainings, and workshops Build champion communities - Create advocate networks and champion communities within customer organizations - Establish power user communities that drive peer-to-peer learning - Train internal customer trainers to scale enablement - Design innovative customer experiences that deepen engagement Lead educational workshops & live events - Facilitate dynamic live and virtual training sessions tailored to diverse audiences - Partner with curriculum team while owning customization and delivery for your customers - Create memorable learning experiences that inspire action and drive adoption Continuously improve & collaborate - Refine materials based on customer feedback and adoption data - Work cross-functionally to understand evolving customer needs - Identify gaps and champion new training opportunities - Build deep relationships with customer stakeholders and executive sponsors Also Travel Requirements note: "Travel Requirements: 25% domestic and international travel may be required." We'll add as a

    after the list. Now What You Need (Requirements). We'll treat as Requirements heading. The content includes sections: Customer success & activation expertise, AI & technical proficiency, Facilitation & education skills, Collaboration & growth. Each with bullet points. Let's extract bullet points: Customer success & activation expertise - At least 9 years of proven track record owning activation success and driving measurable adoption outcomes - Deep experience understanding customer use cases: you discover, map, and leverage specific workflows and business objectives - Experience implementing activation strategies: champion programs, office hours, dashboards, and workshops - Success building advocate networks and power user communities - Ability to connect platform usage to business outcomes and articulate ROI AI & technical proficiency - Ability to scope, design, and deliver custom solutions and demos tailored to customer use cases, working hands-on alongside business stakeholders - Comfortable understanding technical concepts and communicating them effectively to varied audiences - Ability to demonstrate use cases and articulate business value Facilitation & education skills - Expertise delivering virtual and live instructor-led workshops - Skilled at tailoring content and delivery to diverse audiences based on their use cases - Ability to partner effectively with curriculum teams while owning customization and delivery Collaboration & growth - Excellence building relationships with stakeholders at all levels - Strong program management skills and natural advisor mindset - Thrive in fast-paced environments; comfortable with experimentation - Self-aware, feedback-driven, and committed to continuous growth We'll put these under

    Requirements

    with
    • for each bullet. Could also group by subheadings but not required; we can just list all bullets. Benefits & Perks (US Full-time Employees) section: list items. Extract: - Generous PTO, plus company holidays - Medical, dental, and vision coverage for you and your family - Paid parental leave for all parents (16 weeks) - Fertility and family planning support - Early-detection cancer testing through Galleri - Flexible spending account and dependent FSA options - Health savings account for eligible plans with company contribution - Annual work-life stipends for: - Wellness stipend for gym, massage/chiropractor, personal training, etc. - Learning and development stipend - Company-wide off-sites and team off-sites - Competitive compensation, company stock options and 401k We need to format as
      • . The nested list for Annual work-life stipends could be a
        inside
        • . We'll do that. Pay section: Compensation Range: $186K - $219K. We'll put under

          Pay

          as

          . Schedule: not present, so omit. We must not include EEO boilerplate etc. Remove lines: "WRITER is an equal-opportunity employer..." and the Fair Chance Ordinance line and the application acknowledgment line. Now construct HTML. We'll start with a

          for company description. Then

          About the role

          ...

          Then

          Responsibilities

          with
          • for each bullet. We'll need to flatten the bullet list; we can keep the headings as part of
          • text? Could incorporate headings as plain text inside
          • . Eg:
          • Own activation and platform success - Deeply understand each customer's specific use cases, business objectives, and success metrics
          but we should not add extra formatting not in original? The instruction didn't forbid using inside
          • . It said use
            • for any list of duties/requirements/benefits, and

              for prose. It didn't say we cannot add other tags inside. Safer to keep plain text; we can include the heading as part of the sentence. Eg: "Own activation and platform success: Deeply understand each customer's specific use cases, business objectives, and success metrics". We'll just combine. Thus each

            • will contain the full sentence. Let's list responsibilities bullets: - Own activation and platform success: Deeply understand each customer's specific use cases, business objectives, and success metrics; Build and co-develop custom AI solutions with customers, translating their specific use cases into workflows that drive measurable business impact; Design and execute activation strategies that drive measurable platform adoption and business outcomes; Implement champion programs, office hours, usage dashboards, customized trainings, and workshops. But the original had separate bullet points under that heading. We could keep each as separate
            • but include the heading as part of each? Might be repetitive. Better to keep each bullet as separate
            • with the action phrase. Eg:
            • Own activation and platform success
            then sub-bullets? But we cannot have nested
            unless we want. The instruction: use
            • for any list of duties/requirements/benefits. It didn't forbid nested lists. We could have main categories as