Consulting Marketing Lead - Technology, Insights, Analytics, AI

We need to output HTML fragment with sections: About the role? Actually the posting includes intro about ZS repeated. We need to extract substantive content: role description, responsibilities (What You’ll Do), requirements (What You’ll Bring), benefits/perks (Perks & Benefits), maybe Pay/Schedule not present, so omit those sections. Also include maybe "Growth" section? There's "How you’ll grow:" which could be a section like Growth & Development. But rule: include a section only when posting has real specific content. "How you’ll grow:" includes bullet-like sentences but not list. Could treat as a paragraph under a heading "Growth & Development". However we need to decide headings: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings? Probably stick to those. We have responsibilities (What You’ll Do) ->

Responsibilities

. Requirements/Qualifications/Skills: "What You’ll Bring:" includes experience, skills. Could combine into

Requirements

or

Qualifications

. Use Requirements. Benefits: "Perks & Benefits:" ->

Benefits

. Also maybe "How you’ll grow:" could be under Benefits or separate section like "Growth". But not in list; we could incorporate into Benefits paragraph. However rule: Prefer few substantive sections over many thin ones. Could combine growth into Benefits or maybe a separate "Development" but not in given list. Safer to include as part of Benefits paragraph. We need to preserve all substantive information, not invent. Remove boilerplate like EEO, equal opportunity, scam warning, application instructions, cookie/navigation/legal. Also remove duplicated lines (the intro repeated). Also remove "Work Authorization: This position is not eligible for visa sponsorship..." that's maybe considered boilerplate? It's substantive about eligibility; but it's a requirement. Could include under Requirements? It's a condition. Might keep as a short paragraph under Requirements. Also "Considering applying? ..." is EEO/diversity statement; remove. "ZS is an equal opportunity employer..." remove. "Work Authorization: ..." maybe keep as it's a requirement. But it's also somewhat boilerplate. The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. Work authorization is not EEO; it's a requirement. Keep. Also "To complete your application: ..." is application instruction; remove. Also "Find Out More At: www.zs.com" maybe remove as navigation. We need to output only HTML fragment. Let's extract content: Intro about ZS (first paragraph) repeated; we can keep one concise paragraph summarizing ZS mission? But we must preserve ALL substantive information; we cannot summarize away detail. However we can keep the paragraph as is (though duplicated). We should remove duplicated lines. So keep one copy of the intro. The intro: "ZS is a place where passion changes lives. As a management consulting and technology firm focused on improving life and how we live it, we transform ideas into impact by bringing together data, science, technology and human ingenuity to deliver better outcomes for all. Here you’ll work side-by-side with a powerful collective of thinkers and experts shaping life-changing solutions for patients, caregivers and consumers, worldwide. ZSers drive impact by bringing a client-first mentality to each and every engagement. We partner collaboratively with our clients to develop custom solutions and technology products that create value and deliver company results across critical areas of their business. Bring your curiosity for learning, bold ideas, courage and passion to drive life-changing impact to ZS." That's substantive. Then role title line: "Growth Marketing Lead - Technology, Insights, Analytics, AI" appears but we should not repeat job title as heading. It's just text; we could keep it as a paragraph? Probably not needed; but we can keep as a line maybe as

. However instruction: 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. So we can include the job title in a

maybe. Then after that: "ZS is seeking a Consulting Marketing Lead - Technology, Insights, Analytics, AI to lead significant components of consulting marketing and portfolio strategy work across ZS’s technology, insights, analytics and AI capabilities." This is similar to role description; we can keep as part of About the role. Better to treat the intro as About the role? Actually we have no explicit "About the role" heading but we can create one? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role heading for the descriptive paragraph about the role and company. Thus structure:

About the role

... (company description + role description)

Then

Responsibilities

• ... each duty from "What You’ll Do:" list. We need to extract each bullet. The "What You’ll Do:" section has paragraphs with multiple sentences; we need to turn each duty into list items. The instruction: Use
  • for any list of duties/requirements/benefits. So we need to parse the duties into items. Let's list duties from that section: - Develop a deep understanding of ZS’s technology, insights, analytics and AI capabilities, including market opportunities, priority offerings, competitive dynamics, customer needs and stakeholder priorities. - Lead market opportunity assessments and growth analyses to identify new business opportunities. - Translate business priorities, market insights and client needs into portfolio strategy recommendations, growth strategies, positioning and market narratives. - Contribute to annual marketing plans, quarterly business reviews, launch planning and portfolio evolution for supported solution areas, practices and ventures. - Identify new opportunity areas or marketing claims that deliver competitive advantage. - Develop business and stakeholder strategies and messaging that are well-aligned to company brand, priorities and key messages. - Develop positioning, messaging frameworks, value propositions and executive-ready narratives that support clear market differentiation. - Partner with business leaders and SMEs to translate market trends, competitive intelligence, client needs, ZS expertise and business priorities into market-backed points of view and strategic artifacts. - Collaborate on strategic narrative and thought leadership planning to identify differentiated points of view. - Lead creative processes and brainstorming to identify novel solutions. - Partner with business leaders, consulting teams and Marcomms colleagues to develop market-backed strategic artifacts, thought leadership inputs and intellectual capital. - Translate strategic narratives, market insights and positioning into sales enablement materials, proof-point packages and outreach tools that client-facing teams can use in business development conversations. - Support development of frameworks, trend summaries, practice approach collateral, executive-ready materials and other strategic artifacts that can be amplified through campaigns and client engagement. - Help business leaders connect portfolio decisions, market priorities and messaging to enterprise objectives and client needs. - Partner with Demand Generation and other marketing functions to ensure go-to-market plans are grounded in clear strategy, positioning and audience insight. - Integrate multiple data sources, including customer insight, competitive intelligence, portfolio analysis and marketing performance data, to solve ambiguous strategic problems. - Analyze marketing campaign data to deliver insights and recommendations. - Use insights to inform messaging, portfolio direction, strategic recommendations and future planning. - Support structured documentation of strategies, strategic artifacts, assets and outcomes so learnings can inform future planning and decision making. - Independently drive stakeholder discussions and alignment with business leaders, consulting teams and cross-functional marketing partners. - Serve as a strategic thought partner to supported business areas, helping leaders assess where to play, how to win and how to align marketing and portfolio decisions to enterprise priorities. - Own complex, multi-phase projects, managing deliverables to timelines and budgets. - Effectively prioritize and actively manage cross-functional team delivery and alignment. - Develop clear, executive-ready recommendations, presentations and decision materials. - Mentor and invest in others for team success. That's many items; we should keep them all as list items. Now Requirements: "What You’ll Bring:" section includes bullet-like sentences but not explicit list. We need to turn each into list items. List: - 5–8 years of experience in marketing strategy, portfolio strategy, commercial strategy, consulting or related advisory roles. - Strong experience developing recommendations, business cases, value propositions, positioning, messaging or executive-ready materials. - Strong analytical skills and comfort integrating multiple data sources into a cohesive story. - Ability to translate complex technology, insights, analytics and AI topics into clear decisions, actions and strategic narratives. - Effective stakeholder management and ability to influence cross-functional partners. - Ability to lead moderately complex workstreams independently and manage ambiguity. - Strong communication skills with the ability to translate complex insights into clear, persuasive recommendations. - Experience connecting customer insight, competitive intelligence, market analysis, portfolio priorities and business objectives to strategic direction. - Ability to develop market-backed narratives, value propositions, sales enablement materials and thought leadership inputs. - Fluency in English. - Client-first mentality, collaborative spirit and problem-solving approach. Also maybe "How you’ll grow:" we could incorporate as a separate list under Benefits or as its own section "Growth". Since not in prescribed headings, maybe we add a

    Growth & Development

    but instruction says use those examples but not limited? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could still use other headings but better to stick to those. Could put growth under Benefits as part of benefits paragraph. But we also have "Perks & Benefits:" paragraph. We'll extract that as Benefits section. Benefits paragraph: "At ZS, your growth matters. We offer a comprehensive total rewards package that supports your health and well‑being, financial future, time away, and professional development. With robust skills‑building programs, multiple career progression paths, internal mobility, and a deeply collaborative culture, you’ll have the opportunity to do meaningful work, expand your capabilities, and thrive as part of a global community. For details on total rewards in United States, visit ZS US office locations | Where we work | ZS. Hybrid working model: We are committed to giving our employees a flexible and connected way of working. A flexible and connected ZS allows us to combine work from home and on-site presence at clients/ZS offices for the majority of our week. The magic of ZS culture and innovation thrives in both planned and spontaneous face-to-face connections. Travel: Travel is a requirement at ZS for client facing ZSers; business needs of your project and client are the priority. While some projects may be local, all client-facing ZSers should be prepared to travel as needed. Travel provides opportunities to strengthen client relationships, gain diverse experiences, and enhance professional growth by working in different environments and cultures." We need to preserve all substantive information; we can keep as paragraph(s) under Benefits heading. Should we split into list? Not required; we can keep as

    . Also note there is a link "visit ZS US office locations | Where we work | ZS." That's maybe navigation; but it's part of benefits description; we can keep as text. Now also there is "Considering applying? ..." which we remove as EEO/diversity statement. Also "Work Authorization: This position is not eligible for visa sponsorship. Candidates must have authorization to work in the United States that does not now or in the future require employer sponsorship." This is a requirement; we can include under Requirements as a list item. Also "To complete your application: ..." remove. Now we need to ensure we don't include any boilerplate like "NO AGENCY CALLS, PLEASE." remove. Now construct HTML. We'll start with

    About the role

    ... combined intro + role seeking paragraph.

    Let's craft About the role paragraph: combine the initial ZS description and the role seeking sentence. Paragraph