AI Success Architect

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the description. The posting includes: - Description: "What We’re Looking For: ..." then "What You'll Do:" then "What You'll Bring:" then "What We Offer:" then "Our Story" then EEO etc. We need to map to sections: About the role (maybe the introductory paragraph), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (What You'll Bring), Benefits (What We Offer), Pay (salary range), Schedule (maybe hybrid work style). Also maybe "About the role" could be the initial description. We must not repeat job title as heading. No Job ID. We must not include boilerplate like EEO, legal, etc. We must not include sections with filler like "commensurate with experience". We have actual content. We need to output only HTML fragment, no /, no markdown fences. 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, not invent or summarize away detail. We need to remove duplicated lines. Let's extract content. First, "What We’re Looking For:" paragraph: "We're looking for an AI Success Architect to join our Solutions Consulting team and own a new, post-sales discipline at Meltwater: helping our most sophisticated customers get real, measurable value out of our MCP solutions once they're live. This is not a support role and it's not a sales role. It's the connective tissue between what a customer has purchased and what they actually build with it. Customer Success owns everything inside the Meltwater product (searches, dashboards, boolean logic). The AI Success Architect owns everything on the other side of the connector: how a customer uses an LLM platform to turn Meltwater data into reports, briefs, and decisions, and how they responsibly combine that data with other sources they're bringing into the same environment. You'll be hands-on with customers from implementation through the life of the account, and you'll be a genuine authority on where AI and agentic tooling are headed, because our customers will expect you to be ahead of them." That's the About the role. Next "What You'll Do:" bullet list (actually sentences). Let's list each duty: - Partner with customers from implementation onward to design how they'll use MCP and LLM platforms to work with Meltwater data, setting the technical and workflow foundation early so adoption sticks - Help customers build skills, agents, and repeatable workflows that turn raw Meltwater data into reports, briefs, and other deliverables their teams actually use - Develop and share best practices for combining Meltwater data with other datasets customers bring into their LLM environment, including guidance on structuring, prompting, and data hygiene - Act as the primary point of contact for the "outside the product" experience, working alongside CS, Account Managers, and Implementation so nothing falls in the gap between platform and product - Stay current on the fastest-moving part of the AI landscape (models, agent frameworks, MCP tooling) and translate what's new into practical guidance customers can use right away - Identify friction points or recurring questions across accounts and turn them into scalable enablement materials, playbooks, or internal feedback for the product team - Build trusted, senior-level relationships with sophisticated customer stakeholders who expect a true expert, not a generic support contact - Represent the voice of the customer internally, feeding real-world usage patterns and gaps back to Product and Solutions Consulting leadership These are duties. Next "What You'll Bring:" list of qualifications/requirements/skills: - 5+ years of experience in solutions consulting, product specialist, or similar customer-facing technical roles - Hands-on fluency with LLM platforms and agentic tooling, including how to build and structure custom skills or agents, not just how to prompt one - Working understanding of MCP (Model Context Protocol) or comparable connector architectures, and how data flows from a platform into an LLM environment - Comfort translating a technical capability into a clear business workflow, and comfort translating a business need into the technical setup that solves for it - Experience supporting large, complex, or enterprise-scale accounts, including the patience and structure needed for phased implementations - A genuine curiosity about where AI is headed, evidenced by how you already use these tools, not just familiarity with the space - Strong cross-functional instincts and the ability to work smoothly alongside CS, Account Management, and Implementation without needing rigid handoffs - Excellent communication skills, credible with both technical stakeholders and senior business decision-makers - Prior experience with Meltwater's product suite or similar media intelligence/social listening platforms is a plus, but not required We can treat these as Requirements/Qualifications/Skills. The instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have content for About the role, Responsibilities, Requirements (maybe combine Qualifications and Skills?), but we could split: Requirements (experience), Qualifications (education? none), Skills (technical). However we have no explicit education qualifications. Could combine Requirements and Qualifications into one section? But we must only emit sections when posting has real specific content. We could have Requirements (experience), Skills (technical and soft skills). Qualifications maybe not needed. But we have "Prior experience with Meltwater's product suite ... is a plus, but not required" - that's a qualification. We could create sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Omit Qualifications if no distinct content. But we need to follow instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples; we can include only those we have content for. Thus we will output:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • 5+ years of experience in solutions consulting, product specialist, or similar customer-facing technical roles
  • Experience supporting large, complex, or enterprise-scale accounts, including the patience and structure needed for phased implementations

  Skills

  • Hands-on fluency with LLM platforms and agentic tooling, including how to build and structure custom skills or agents, not just how to prompt one
  • Working understanding of MCP (Model Context Protocol) or comparable connector architectures, and how data flows from a platform into an LLM environment
  • Comfort translating a technical capability into a clear business workflow, and comfort translating a business need into the technical setup that solves for it
  • A genuine curiosity about where AI is headed, evidenced by how you already use these tools, not just familiarity with the space
  • Strong cross-functional instincts and the ability to work smoothly alongside CS, Account Management, and Implementation without needing rigid handoffs
  • Excellent communication skills, credible with both technical stakeholders and senior business decision-makers
  • Prior experience with Meltwater's product suite or similar media intelligence/social listening platforms is a plus, but not required

  Benefits

  • Enjoy flexible paid time off that allows you to have an enhanced work-life balance.
  • Excellent medical, dental, and vision options
  • 401(k) matching, life insurance, commuter benefits, and parental leave plans
  • Complimentary CalmApp subscription for you and your loved ones, because mental wellness matters.
  • Energetic work environment with a hybrid work style, providing the balance you need.
  • Thrive within our inclusive community and seize ongoing professional development opportunities to elevate your career.
  But note: "Energetic work environment with a hybrid work style, providing the balance you need." could be considered Schedule? Actually schedule is hybrid work style. We could extract schedule: hybrid work style. But we also have Benefits includes that line. Might be better to separate Schedule section: hybrid work style. However the instruction says include Schedule only if posting actually states them. It does state hybrid work style. So we could put Schedule section with that line. But we also have Benefits includes many items; we could keep Benefits without the hybrid line, and Schedule separate. Let's parse Benefits from "What We Offer:": - Enjoy flexible paid time off that allows you to have an enhanced work-life balance. - Excellent medical, dental, and vision options - 401(k) matching, life insurance, commuter benefits, and parental leave plans - Complimentary CalmApp subscription for you and your loved ones, because mental wellness matters. - Energetic work environment with a hybrid work style, providing the balance you need. - Thrive within our inclusive community and seize ongoing professional development opportunities to elevate your career. - At Meltwater, we believe great impact deserves great reward. Our compensation approach is data-driven, market-informed, and built to scale with your growth. We benchmark roles against external market data and use structured leveling frameworks to ensure fairness, consistency, and internal equity across teams and geographies. These frameworks are based on objective, gender-neutral criteria in line with applicable pay transparency regulations. For this role, the base salary range is $91,000 - $130,000. Compensation may also include a performance-based bonus opportunity. Actual offers are determined based on job-related skills, experience, demonstrated capabilities, and work location. We typically hire within the range in a way that supports long-term growth, recognizing that compensation evolves as scope, performance, and impact expand over time. We regularly review our compensation practices and conduct pay equity analyses to help ensure our decisions remain fair, objective, and market-aligned. Employees and candidates may request additional information on how compensation is determined, in line with local legal requirements. Our Talent Acquisition Team is happy to walk you through the full compensation picture specific to your location and level during the interview process. Thus Benefits includes many items; Pay includes salary range and bonus. Schedule: hybrid work style. Thus we should separate: Benefits: flexible PTO, medical/dental/vision, 401k matching etc, CalmApp subscription, inclusive community, professional development. Pay: base salary range $91,000 - $130,000, performance-based bonus opportunity. Schedule: hybrid work style (energetic work environment with a hybrid work style, providing the balance you need). Could also mention flexible PTO but that's benefit. Thus we need to extract. Let's list Benefits items: - Enjoy flexible paid time off that allows you to have an enhanced work-life balance. - Excellent medical, dental, and vision options - 401(k) matching, life insurance, commuter benefits, and parental leave plans - Complimentary CalmApp subscription for you and your loved ones, because mental wellness matters. - Thrive within our inclusive community and seize ongoing professional development opportunities to elevate your career. (Note: "Energetic work environment with a hybrid work style, providing the balance you need." goes to Schedule.) Pay items: - For this role, the base salary range is $91,000 - $130,000. - Compensation may also include a performance-based bonus opportunity. - Additional details about compensation determination etc. But we should preserve substantive info; we can include the base salary range and bonus opportunity. The rest about determination could be considered boilerplate? It's still substantive but maybe we can include as part of Pay section. However instruction: "Prefer a few substantive sections over many thin ones." We could include Pay section with salary range and bonus. The rest about determination could be considered boilerplate but it's still info about compensation.